How to Fix Google Ads Placement Exclusions

To fix Google Ads placement exclusions, identify the symptom, inspect the effective account and campaign settings, verify the placement format and surface, then change the smallest rule responsible. A placement that still receives impressions may be attached to the wrong level or formatted for a different network; a campaign that suddenly loses reach may have overlapping lists or an overly broad content category. Do not delete every exclusion until you know which problem you are solving.

Google’s placement exclusion help covers specific webpages, domains, apps, videos, and related controls. It also explains that placement and content exclusions vary by campaign and surface. Use the current account interface and policy details for the final diagnosis; the workflow below keeps the investigation ordered.

Identify the exact symptom

Record the campaign, ad group, account or manager list, placement value, device, surface, date range, and expected behavior. Common symptoms include:

an excluded website, app, video, or channel still receives impressions;
a list works in one campaign but not another;
reach or spend drops sharply after a list change;
an entire category was blocked when only one placement was problematic; or
the report and the exclusion list appear to use different identifiers.

Separate a delivery problem from a reporting problem. A recent placement report can contain data from before the exclusion, and a conversion or impression may have a lag. A live search or app test is not enough to prove that a placement is or is not eligible.

Check status and effective scope first

Open the current Content or Exclusions view and confirm the account, campaign, ad group, list association, placement type, and content settings. Inspect a representative ad group or campaign that should inherit the rule. Shared lists, account-level exclusions, and overlapping categories can make the effective state different from the row that was just edited.

Fix the common “excluded placement still shows” case

First check whether the impression came from the same property and surface. An individual page exclusion is not automatically a domain exclusion, and a Display placement rule may not cover a Search Partner surface in the same way. Google documents that account-level placement exclusions apply to the Search Partner Network, while subdomains, subsites, and subpages do not work there in the same way as domain exclusions.

Confirm the date and time of the impression, the campaign to which the exclusion is attached, and whether another targeting or campaign branch is responsible. If the placement report shows a domain but the list contains a path, determine whether the path is the intended boundary or whether the domain should be blocked.

Check the exact placement value

Compare the list entry with the placement identifier shown by Google Ads. Look for protocol prefixes, URL paths, store package names, video or channel IDs, and copied whitespace. Do not replace a valid narrow entry with a broad domain until the business owner accepts the reach change.

For mobile apps, verify the store identifier or package name. For a website, choose domain, subdomain, directory, or page deliberately. For a video or channel, copy the identifier from the placement report rather than deriving it from a display name.

Fix a block that is too broad

If useful reach disappears after an exclusion change, compare the before and after effective settings. Look for a domain where only one directory was problematic, a shared list attached to an unrelated campaign, a category exclusion added on top of a placement list, or several lists that cover the same inventory. Restore the prior state only after preserving the evidence and identifying which rule caused the change.

Narrow a performance exclusion to the page, app, video, channel, or directory that meets the evidence rule. Move an offer-specific list from account level to campaign or ad-group scope. Keep a mandatory safety exclusion broad when that is what the approved policy requires, and route any change through its owner.

Check the campaign’s other controls

Review content suitability, app categories, device settings, targeting, audiences, schedules, budgets, bids, and campaign status. A placement exclusion cannot explain every reach change. If several controls changed in the same release, compare their effective states and roll back only the unrelated or mistaken change.

Fix an exclusion that uses the wrong format

Use Google’s current placement-format guidance to distinguish a top-level domain, first-level subdomain, directory, individual page, app identifier, video, and channel. A value that looks plausible in a text box can still be ignored or interpreted at another scope. Re-enter the approved value using the format shown by the account and then verify the saved association.

For sites, decide whether the entire domain or only a path is unacceptable. For apps, copy the iPhone store ID or Android package name from the relevant store URL or placement record. For videos and channels, use the identifier Google exposes. Do not include a long query string or tracking parameter unless the current field explicitly supports that property.

Avoid malformed bulk uploads

If a list was uploaded in bulk, compare the source file with the entries Google accepted. Check duplicate rows, blank values, unsupported properties, domain syntax, and accidental broadening from a copied prefix. Keep the accepted list and rejected-row report with the change record. Fix the source and re-upload a small correction rather than appending a second list that hides the first mistake.

Fix content-exclusion confusion

Content exclusions and placement exclusions are related but not interchangeable. A category or inventory-type setting can remove many potential placements, while an individual placement exclusion targets a known website, app, video, or channel. Read the description and campaign scope for the current control.

If the account has a safety requirement, confirm it with the policy or brand owner before narrowing a category. If the problem is one low-quality placement, replace a broad category block with the smallest evidence-based exclusion that covers the issue. Google warns that category exclusions cannot guarantee that every related page is removed, so do not describe a category as perfect coverage.

Google’s content-exclusion guidance explains that multiple exclusion types can be combined. Check for combinations that unintentionally remove more inventory than the team intended.

Fix policy or ownership problems

When a list includes sensitive, regulated, or brand-protected inventory, record the reason and decision owner. A performance analyst should not remove a mandatory safety rule because a short report looks efficient. Conversely, a temporary performance block should not be presented as a permanent policy requirement.

Give each shared list a clear name, owner, purpose, affected campaigns, last review, and rollback note. Before editing a shared list, identify every branch that can inherit it. If one campaign needs an exception, create a narrower list or placement rule rather than changing the shared rule for everyone.

Fix measurement and interpretation errors

Check the date range and whether the placement report is updated. Compare eligible impressions, spend, interactions, conversions, qualified outcomes, value, and normal conversion lag. A placement may appear after the exclusion because the report contains earlier activity, or it may appear through a different campaign or targeting path.

Keep bids, budgets, audiences, creative, landing pages, and offers in the analysis. A reach decline that follows an exclusion can also be caused by a budget change, a schedule, a policy review, or a campaign being paused.

Use a controlled repair

Write the repair, expected result, observation window, owner, and rollback condition. Change the smallest scope or value possible. After saving, inspect the effective setting and annotate the time. Wait for the normal data and conversion lag before judging a performance repair, but act immediately on a clear safety violation under the approved policy.

Verify the repair and decide what happens next

Reopen the Content or Exclusions view after the change. Confirm the account, campaign, ad group, list, placement value, surface, category, and schedule. Check a representative effective branch and preserve the old state. If the issue involved a shared list, verify at least one other campaign was not changed accidentally.

At review, choose retain, narrow, expand, pause, replace, reverse, test, or wait. Record the evidence, owner, next date, and any policy approval. Do not close the issue merely because the editor accepted the value; close it when the scope and intended business outcome are understood.

Placement-exclusion troubleshooting checklist

[ ] The symptom, campaign branch, placement, surface, date range, and expected behavior are recorded.
[ ] Account, manager, campaign, ad-group, content, and shared-list scope is checked.
[ ] The exact domain, path, page, app, video, or channel identifier is verified against the placement report.
[ ] Search Partner, Display, Video, app, and other relevant surface behavior is considered.
[ ] Overlapping lists, category settings, schedules, budgets, bids, and campaign status are reviewed.
[ ] A safety rule is separated from an evidence-based performance test.
[ ] Bulk-upload source and accepted entries are compared when applicable.
[ ] Baseline, conversion lag, qualified outcomes, value, and reach are included in the diagnosis.
[ ] The repair is narrow, documented, owned, and reversible.
[ ] The saved state and a representative effective branch are rechecked.

For the initial workflow, read how to set up Google Ads placement exclusions correctly. For ongoing review, use how to optimize Google Ads placement exclusions and Google Ads placement exclusions best practices. The adz.so product overview is an audit entry point; it does not automatically repair Google Ads exclusions.