How to Govern Google Ads Placement Exclusions

A placement exclusion answers a specific question: on which page, site, app, video, channel, or other supported placement should an ad not appear? It does not answer who the audience is, which search query should be blocked, or which landing page should receive traffic. Write the unsuitable-placement rule first, name the account or campaigns it is meant to protect, and retain the rendered placement evidence that triggered review. That makes the action reversible and prevents a vague concern from becoming a permanent account-wide block.

Separate four neighboring controls in the operating record. Placement exclusions address inventory locations. Content-suitability settings address types of content. Negative keywords address query matching. Brand exclusions address branded search traffic. Google groups some of these settings near one another, but they have different scope and consequences. Use one owner and review date for each entry, and never claim that a saved exclusion guarantees every related impression is blocked. The control should be evaluated against the official limitation and the placement evidence you can actually observe.

Apply an exclusion only as broadly as the rule requires. Google documents placement exclusions at account, campaign, or ad-group level, with account-level settings overriding narrower settings. Performance Max placement exclusions are managed at the account level, and manager-account placement exclusion lists can be inherited by linked child accounts. That means a list created for one recurring risk can affect far more campaigns than the person entering it may expect. Map account ownership and campaign coverage before applying a manager-level list.

Use an account-level entry when the placement is unsuitable for every relevant campaign in that account. Use a campaign or ad-group control when the issue is specific to a narrower objective and the campaign type supports that scope. For a manager list, inventory every linked child account and document who can approve additions. Avoid copying the same exclusion into several scopes without a reason. Duplicate controls obscure which record is authoritative and make rollback harder when a placement is later reclassified.

Store the exact placement value accepted by Google Ads and a normalized review key beside it. Google notes that excluding a domain without the www prefix can extend the exclusion to subdomains, subsites, and subpages, while retaining www can narrow that behavior. Country domains need separate exclusions. Search Partner behavior also differs from Display or Video behavior. Preserve the raw entered value, the normalized domain or content identifier, and the inventory type so later reviewers do not infer a wider rule than the platform applies.

For YouTube, distinguish a specific video from a channel and from the entire youtube.com domain. Google states that the entire YouTube domain cannot be excluded at the campaign level, especially for Performance Max, while specific videos or channels can be managed through account-level content-suitability controls. Validate identifiers before saving. A typo can create a control that looks complete in a spreadsheet but matches nothing in the advertising account.

A useful exclusion ledger contains the observed placement, screenshot or report reference, campaign and account scope, reason code, requested by, approved by, created time, review date, and desired rollback state. Reason codes might distinguish brand unsuitability, fraudulent inventory evidence, legal restriction, customer-safety concern, or an approved strategic boundary. Do not use performance alone as a permanent suitability judgment without a sufficient comparison window and conversion evidence. A low-volume placement can look extreme because the denominator is small.

Link every row to the source report and retain the report filters. If the placement came from Performance Max channel reporting, record that fact and the reporting period. If it came from a complaint or screenshot, retain the visible page context. Avoid copying personal data or unrelated account details into the ledger. The goal is an auditable control, not a second ungoverned data store.

Google documents manager-account placement exclusion lists as reusable controls that can be applied to linked child accounts. Treat that inheritance as a release. Review the proposed list, compare it with existing account exclusions, identify conflicts, and create a dated snapshot before applying it. Limit edit access to the people responsible for cross-account brand suitability. A shared list saves repetition only when its owner can explain why every child account should inherit every entry.

For an individual account, enter placements through the account content-suitability controls and confirm the saved values. For a manager account, create the list in the shared library, select the intended child accounts, and apply it deliberately. Do not assume new child accounts inherit an existing list automatically without verifying the current account configuration. Record the applied accounts and the verification time after the change.

Google says new placement exclusions typically take effect within twelve hours and can be checked in change history. Record the save confirmation, then verify change history and the final list after the processing window. Review new placement reporting for the same identifier, but do not treat an empty report as proof that every related impression is impossible. Reporting latency, aggregation, and identifier differences can all affect what the interface shows.

If the same placement appears after the expected window, compare the raw identifier, inventory type, account scope, and campaign type before changing more settings. Confirm whether the impression occurred before or after the exclusion time. Escalate a reproducible platform mismatch with the saved control and report evidence. Avoid broad emergency exclusions while the first control is still processing unless the risk itself requires immediate containment.

Schedule a periodic review based on risk. Confirm that the placement still exists, the reason remains valid, the scope is still correct, and the owner is active. Compare manager lists with child-account exceptions and investigate entries that no longer have evidence. A long exclusion list is not automatically safer. Stale entries can hide inventory that later becomes appropriate, while duplicate entries make ownership unclear.

Retire a control with the same discipline used to add it. Preserve the prior value, removal reason, approver, date, and expected affected accounts. Verify the deletion in change history and monitor the relevant placement report after the change. Keep the historical ledger instead of erasing the row. That lets a future operator distinguish an intentional rollback from a missing control and avoids rebuilding the same decision without context.