Google Ads Placement Exclusions Best Practices

The best Google Ads placement exclusions practices protect the brand and remove proven waste while keeping enough eligible inventory for the campaign to reach and learn from qualified people. Separate mandatory safety rules from performance experiments, choose the narrowest scope that fits the rule, build lists from evidence, and measure the reach and outcome tradeoff after the change. An exclusion is a governance decision, not a universal shortcut for improving performance.

Google’s current placement exclusion guidance covers excluding specific webpages and videos and notes that placements can include pages, sites, mobile apps, and videos. The interface also groups content targeting and exclusions in the campaign’s content area, with options that vary by campaign type. Confirm the current controls before publishing; the decision framework below remains useful when labels or menus change.

Start with a written exclusion policy

Define what the campaign is protecting and what it is trying to achieve. Write the audience, offer, geography, conversion, value model, budget, bidding approach, and brand or regulatory risk. Then classify a proposed exclusion as one of three things:

A mandatory safety or policy rule.
A repeated performance problem supported by enough evidence.
An unfamiliar or immature placement that should be observed.

These categories need different decisions. A brand-safety rule may apply even when there is little spend. A performance block should have a sample-size threshold, a conversion-lag rule, and a review date. An unproven placement should not be blocked merely because it looks unfamiliar or has not matured.

Assign decision ownership

Give safety rules to the brand, legal, or policy owner and performance rules to the person accountable for qualified outcomes. Record the list name, purpose, scope, owner, creation date, last review, evidence, and rollback condition. Without that record, an exclusion can become a permanent block that nobody understands well enough to remove.

Distinguish placement exclusions from other controls

Do not use one term for every kind of reach control. A placement exclusion can remove a website, page, app, video, channel, or other specific inventory. A content exclusion can remove a category or suitability context. A targeting choice determines where the campaign is eligible to seek people. Negative keywords, audience settings, creative, and landing-page language solve other parts of the relevance problem.

Google’s Display content-exclusion guidance explains that multiple exclusion types can be combined and that ads will not match against the selected excluded content in the ad group. Read the setting description in the current campaign before assuming that a category block has the same scope or behavior as an individual placement exclusion.

Solve the cause, not only the symptom

If an app produces accidental interactions, inspect the placement report, creative, click pattern, and downstream quality. A placement exclusion may be appropriate, but a broad app-category block can hide a targeting or creative problem. If irrelevant sites appear because the offer is too broad, improve audience, topic, placement, creative, or landing-page alignment as well as reviewing the inventory.

Use placement reports as evidence

Review where ads were eligible or served and filter the report by website, app, video, channel, category, device, location, and campaign type when those dimensions are available. For each candidate, inspect context and record impressions, spend, interactions, conversions, qualified rate, revenue or pipeline value, and normal conversion lag.

A high click-through rate can indicate curiosity or accidental interaction; it is not proof that the placement is valuable. A high cost per conversion can be temporary when the placement has only a few clicks or a long sales cycle. Look for repeated patterns and the business outcome, not a single alarming row in a report.

Set a minimum evidence rule

For performance exclusions, define a threshold before looking for candidates: for example, repeated spend without a qualified outcome after the campaign’s normal lag, or a stable pattern of low value across a meaningful sample. The right threshold depends on traffic, margins, conversion volume, and risk; it should not be copied from another account.

For safety exclusions, follow the approved rule even when performance evidence is small. Mark the reason as mandatory so a later analyst does not remove it because the short-term CPA happened to look acceptable.

Choose the narrowest effective scope

Apply an exclusion where the rule is true, not where the control is easiest to find. An account or manager-level rule can protect every relevant campaign, but it also removes inventory from campaigns with different audiences, markets, offers, or risk tolerance. A campaign-level rule is usually better when the concern belongs to one offer or geography. An ad-group or individual placement exclusion is appropriate when the issue is specific to one intent or destination.

Before attaching a shared list, compare the campaign goals, markets, conversion models, brand rules, and inventory needs of every branch that will inherit it. Separate lists by purpose, such as “mandatory brand safety,” “regulated context,” “temporary performance test,” or “mobile-app investigation.” A single list that mixes permanent policy rules with experimental blocks is hard to review and risky to detach.

Name lists for the decision they represent

Use a name that states the scope and purpose, not only a date or internal ticket number. Record included placement types, owner, evidence, last review, expiration or renewal rule, affected campaigns, and rollback steps. Keep a change log when a list grows; adding one app or channel should not erase why the original list existed.

Do not assume that a shared list is harmless because it is centrally managed. Central ownership improves consistency only when each attachment has an intentional review and the reach tradeoff is visible to the campaign owner.

Match the exclusion to the inventory

Different inventory needs different evidence and controls:

Websites and pages need context, domain, content quality, and downstream outcome review.
Mobile apps need careful interaction analysis because taps can be accidental or poorly qualified, but a broad app block can remove useful reach.
Videos and channels need content context, audience fit, frequency, and suitability review.
Categories and content labels are broader controls and should be governed by an explicit brand or risk rule.
Individual placements are useful for a known unsuitable page, app, video, or channel when the account can identify it accurately.

Do not extrapolate from one placement to an entire category without evidence or an approved safety requirement. If the problem is a publisher’s context, use the smallest publisher or placement exclusion that covers the problem. If a category is genuinely unacceptable for the brand, document the policy reason and apply the appropriate content control rather than accumulating many individual blocks that approximate the same rule.

Check how the current campaign treats exclusions

Google’s specific placement exclusion guidance describes acceptable forms such as a domain, directory, or individual page, and notes that the dynamic nature of the Display Network means a category exclusion cannot guarantee removal of every related page. Use the current documentation and campaign interface to verify syntax, supported surfaces, and effective scope before relying on a list for a safety promise.

The same guidance states that account-level placement exclusions also apply to the Search partner network from March 2024. Treat that as a current platform behavior to verify in the account and documentation, not as a reason to place every performance block at account level. A broad exclusion can affect more surfaces than the report that originally prompted it.

Apply changes in a controlled sequence

Before saving a change, capture the current setting and effective scope. Then:

Apply mandatory safety and policy controls approved for the campaign.
Attach or edit the narrow performance list that meets the evidence rule.
Verify the resulting account, campaign, ad-group, and content settings.
Annotate the effective date, reason, owner, affected branch, and review window.
Leave bids, budgets, creative, audiences, and landing pages unchanged when they are not part of the same controlled decision.

Open the current Content page under the campaign’s Audiences, keywords, and content controls, or use the placement settings exposed for the campaign type. Review websites, apps, videos, channels, topics, content types, and exclusion lists together. Overlapping controls can make effective reach narrower than any one list suggests.

Verify before interpreting results

After saving, inspect a representative campaign and ad group. Confirm the intended list is attached, the placement or content type is correct, and no unrelated list or category setting was inherited. Export or record the before-and-after state according to the team’s normal change process.

If delivery falls immediately, check for overlapping lists, a malformed placement, a broader category than intended, a campaign schedule change, or a shared account rule. Do not restore every exclusion automatically; identify which setting caused the reach change and preserve mandatory safety controls.

Measure both protection and reach

Set a baseline before changing a performance exclusion. Include the same geography, offer, budget, bidding approach, audience, creative, landing page, and conversion definition. After the campaign’s normal conversion lag, compare eligible impressions, spend, placement mix, interactions, conversions, qualified outcomes, revenue or pipeline value, and invalid or accidental interaction indicators where available.

Look for the tradeoff rather than a single favorable metric. A block can reduce cheap clicks while increasing qualified rate, or reduce both waste and useful demand. A safety rule can be correct even if it lowers reach. A performance rule should be narrowed or reversed when it removes valuable inventory without improving the outcome it was meant to improve.

Separate safety decisions from optimization decisions

Label every result as safety, relevance, efficiency, or learning. Do not remove a mandatory safety exclusion because a short report shows an attractive CPA, and do not expand a safety block into a whole inventory class because one placement had a poor day. The review owner should be able to explain which objective the rule serves.

Use an observation window that reflects sales and conversion delay. For a clear safety violation, act immediately under the approved policy. For a weak performance signal, record “observe” and a next review date when the data is not mature enough to justify a permanent block.

Review, narrow, or roll back the list

At each review, classify the rule as retain, narrow, expand, pause, replace, or wait. Record the evidence and the next check. A list can be narrowed when a specific app, page, or channel caused the issue but the category is still useful. It can be expanded when a documented policy rule covers the broader inventory. It can be rolled back when an experimental exclusion failed its stated test or reduced qualified value.

Preserve the previous list and attachment state before editing. If a site, app, video, channel, offer, or campaign is removed from the exclusion, record why and whether a re-test is controlled. Do not remove a mandatory safety rule because an owner changed or because it has not generated recent spend.

Revisit after structural changes

Review exclusions after a new campaign type, site migration, audience change, brand or legal policy update, budget shift, bidding change, geographic launch, or major landing-page release. A list that was sensible for an awareness campaign may be too restrictive for a high-intent lead campaign, while a list created for one market may no longer match another.

Common placement-exclusion mistakes

Avoid these patterns:

copying a universal block list into campaigns with different risk and conversion goals;
blocking an entire app, topic, category, or publisher after one low-volume placement;
treating high CTR or low CPA as proof of qualified value;
excluding inventory before the conversion lag has passed;
using a placement exclusion to compensate for broad targeting, weak creative, or broken measurement;
mixing mandatory safety rules with temporary performance experiments;
ignoring overlapping account, campaign, ad-group, and content exclusions;
failing to check the exact scope and syntax of a domain, directory, page, app, video, or channel exclusion;
changing exclusions, bids, budgets, audiences, and ads at the same time;
leaving lists without an owner, evidence, review date, or rollback rule;
assuming a category exclusion guarantees removal of every related page;
never revisiting the list after a campaign, market, or policy change.

Google Ads placement exclusions checklist

Before publishing or renewing an exclusion, confirm:

[ ] Campaign goal, audience, offer, geography, conversion, value, and risk level are documented.
[ ] The rule is classified as mandatory safety, proven performance, or unproven inventory.
[ ] The exclusion type matches the inventory and the current campaign interface supports the intended scope.
[ ] Evidence, sample size, conversion lag, or approved safety policy is recorded.
[ ] The exclusion is no broader than necessary for the rule.
[ ] Shared lists have clear name, purpose, owner, affected campaigns, review date, and rollback notes.
[ ] Account, manager, campaign, ad-group, and content settings have been checked for overlap and effective scope.
[ ] Websites, apps, videos, channels, categories, and individual placements were reviewed in context.
[ ] Before-state, effective date, and unchanged campaign variables are recorded.
[ ] Baseline, reach, spend, qualified outcomes, value, and conversion lag are ready for review.
[ ] The next retain, narrow, expand, pause, replace, or wait decision has an owner and date.

For implementation steps, read how to set up Google Ads placement exclusions correctly. For the settings reference, see best Google Ads placement exclusions settings. The adz.so product overview describes the current audit entry point; it does not claim that adz.so creates, applies, or manages Google Ads exclusions.