Google Ads Placement Exclusions Checklist

Use this Google Ads placement exclusions checklist before adding a block, after a campaign change, and during recurring account reviews. Confirm the business reason, evidence or approved safety rule, placement format, scope, overlap, and reach tradeoff before saving. Then assign an owner and review date so the exclusion remains understandable and reversible.

Google’s current placement exclusion guidance covers websites, pages, mobile apps, videos, channels, and content controls. The exact fields and campaign surfaces can change, so use the current Google Ads interface for implementation. This checklist supplies the decisions and verification record around those controls.

1. Define the campaign and decision

[ ] Campaign, type, market, language, device mix, and date are recorded.
[ ] Audience, offer, geography, budget, bidding, and primary conversion are documented.
[ ] Qualified outcome, value model, and conversion lag are known.
[ ] Brand, legal, policy, or business risk is stated.
[ ] The proposed exclusion is classified as safety, proven performance, or unproven inventory.
[ ] An owner, effective date, review date, and rollback condition are named.

Write the reason in plain language before opening the editor. “This context violates the approved brand-safety rule” is different from “this placement has a high CPA.” The first can require immediate action; the second needs data and a review rule.

Set the evidence rule

For a performance exclusion, record the minimum spend, interactions, time, qualified outcomes, or value pattern required. Include the normal conversion lag. Do not turn one low-volume row, two clicks, or an unfamiliar publisher into a permanent block without a business or safety basis.

For a safety exclusion, attach the approved policy or decision owner. Do not remove it later because short-term performance happens to look attractive.

2. Inspect reports and placement context

[ ] The placement or content report covers the relevant campaign and date range.
[ ] Website, page, app, video, channel, category, device, and location dimensions are reviewed where available.
[ ] Context, impressions, spend, interactions, conversions, qualified rate, value, and lag are recorded.
[ ] Accidental interaction, targeting mismatch, creative, landing-page, and measurement causes have been considered.
[ ] The candidate is not being blocked only because it is unfamiliar.
[ ] The report row is associated with the same campaign and surface as the proposed exclusion.

The report is evidence, not an automatic block list. Ask whether the inventory is the problem or whether another campaign component is attracting the wrong traffic. Preserve the before-state before changing the account.

3. Select the correct exclusion format

For every candidate, check:

[ ] Domain, subdomain, directory, or individual page is the intended website boundary.
[ ] App identifier or package name comes from the correct store or placement record.
[ ] Video or channel identifier is copied from Google Ads rather than a display name.
[ ] The value contains no unintended protocol, query string, whitespace, or broad prefix.
[ ] The current editor supports the selected property and campaign surface.
[ ] A category or content exclusion is used only when the broader rule is truly required.

Google documents that domain, path, and page exclusions have different scope, and that subdomains, subsites, and subpages do not work on the Search Partner Network in the same way as domain exclusions. Do not assume a Display format has identical coverage on every network.

4. Confirm scope and list ownership

[ ] Account or manager scope is used only for a rule shared by every attached campaign.
[ ] Campaign scope matches the offer, market, geography, and risk profile.
[ ] Ad-group or individual-placement scope matches the specific intent or known property.
[ ] Shared lists have a descriptive name and a stated purpose.
[ ] Each list has an owner, affected campaigns, evidence, last review, and rollback note.
[ ] Mandatory safety entries are separated from temporary performance tests.
[ ] A campaign-specific exception has its own narrower rule rather than an edit to a shared asset.

Before attaching a shared list, inspect the goals and inventory needs of every branch that will inherit it. Central management does not make a broad block safe by itself. The placement exclusion lists guidance can help with shared-library decisions, but the campaign owner still needs to review the effective attachment.

Check overlap

[ ] Existing account, campaign, ad-group, list, category, and content exclusions are exported or recorded.
[ ] Redundant domain, path, page, app, video, and category entries are identified.
[ ] Several moderate controls do not combine into an unintended global restriction.
[ ] The expected reach effect is written beside the proposed change.

5. Review content-suitability settings

[ ] Placement exclusions and content exclusions are considered separately.
[ ] Inventory types and sensitive-content settings match the approved brand policy.
[ ] Category exclusions are not being used to hide one performance problem.
[ ] The team understands that category exclusions do not guarantee removal of every related page.
[ ] Search Partner, Display, Video, app, and other relevant surfaces are included in the review.

Google’s Display content-exclusion documentation explains that multiple exclusion types can be combined. Read each setting’s current description and record whether it is a safety requirement or an optimization experiment.

6. Apply and verify the saved change

[ ] The correct account and campaign are open.
[ ] The current Content or Exclusions page is being edited.
[ ] The selected exclusion type matches the approved record.
[ ] The list or placement value is copied and reviewed before Save.
[ ] The account, campaign, ad-group, or content association is correct.
[ ] The status and effective settings are checked after Save.
[ ] A representative ad group or campaign has been inspected.
[ ] Shared branches were checked for accidental changes.
[ ] Bulk-upload accepted and rejected rows are preserved when applicable.

A successful Save message proves only that the interface accepted the input. Reopen the settings and inspect the effective branch. If the rule is shared, verify at least one other campaign that should inherit it and one campaign that should not.

7. Measure protection, reach, and quality

[ ] Before-state, effective date, list version, and simultaneous changes are recorded.
[ ] Baseline eligible impressions, spend, placement mix, interactions, conversions, qualified outcomes, and value are available.
[ ] Review timing includes the campaign’s normal conversion lag.
[ ] Budget, bids, audience, creative, landing page, offer, and geography are comparable or annotated.
[ ] Safety, relevance, efficiency, and learning outcomes are separated.
[ ] The team knows what result would justify narrowing, retaining, expanding, pausing, replacing, or reversing the rule.

A lower click count is not enough to prove success. An exclusion can remove accidental traffic and improve quality, or remove useful demand and reduce value. Review the full path and the business outcome.

Keep a rollback record

[ ] The previous list and attachment state are preserved.
[ ] The rollback owner and trigger are recorded.
[ ] Experimental blocks can be reversed without touching mandatory safety controls.
[ ] A policy or legal owner approves changes to non-negotiable rules.

8. Recurring placement-exclusion maintenance

Run these checks after a site migration, new campaign type, market launch, budget or bid change, audience update, brand-policy change, or landing-page release:

[ ] List entries still exist and represent the intended inventory.
[ ] Domains, paths, apps, videos, channels, and categories still have the recorded scope.
[ ] Shared lists are attached only to campaigns with compatible goals.
[ ] Owners and review dates are current.
[ ] Safety entries remain approved and performance entries still meet their evidence rule.
[ ] Reach, qualified outcomes, value, and lag are reviewed.
[ ] Stale, redundant, or over-broad entries have an explicit decision.

Do not let a list become a permanent archive of old reactions. Keep its purpose visible, review it on a calendar, and preserve a change history.

Compact launch ticket checklist

Copy this version into a change record:

[ ] Reason: safety / performance / observation.
[ ] Campaigns and scope:
[ ] Placement or category format:
[ ] Evidence or policy basis:
[ ] Owner and policy reviewer:
[ ] Effective date and review date:
[ ] Expected reach and quality effect:
[ ] Rollback trigger:
[ ] Saved-state verification:
[ ] Next action:

For setup steps, read how to set up Google Ads placement exclusions correctly. For optimization, use how to optimize Google Ads placement exclusions; for existing problems, see how to fix Google Ads placement exclusions. The adz.so product overview is a truthful audit entry point; it does not apply Google Ads exclusion settings automatically.