Exact match negative keywords and close variants

Negative exact is narrower than positive exact

Positive exact matching in Google Ads can reach searches with the same meaning or intent. Negative exact does not copy that expansion. A positive keyword and a negative keyword with the same wording can therefore cover different sets of searches, even when both carry the exact match label.

Enter a Google exact negative with square brackets where the interface uses keyword syntax, or select Exact in the appropriate match type field. The rule applies to the complete search at its assigned scope. Extra words before, after or inside the wording put a query outside that exact exclusion.

For example, [free crm] blocks free crm. It does not block best free crm, free crm migration or crm free. This makes exact a useful way to remove a specific unwanted query while retaining the ability to assess related demand. It does not exclude the whole subject of free software.

Eligibility under a negative rule does not guarantee an impression. The query still needs an eligible targeting route, suitable settings and an auction outcome. The negative keyword match types guide compares that boundary with the wider coverage of phrase and Google negative broad.

What the same exact exclusion leaves eligible

Assume a paid software campaign rejects the bare query free crm because it requests an offer the business does not provide. The Google negative [free crm] creates the following boundary. Each no in the table means this particular negative does not block the query.

The table is a matching test, not a recommendation to exclude every free crm query. A product with a suitable offer may want that traffic. Even a paid product may have valuable modified queries, which is why the scope of the evidence matters before expanding an exclusion.

Do not describe exact negatives as character sensitive. Capitalization is not a useful way to separate query eligibility. The practical distinction is the full query wording without close variant expansion, rather than a promise that punctuation or letter case creates separate audiences.

Use the search terms report to protect useful modifiers

Consider a paid CRM product that includes migration assistance with its subscription. The bare search free crm can request a permanently unpaid product. The longer search free crm migration for business can request an included migration service while the buyer remains willing to pay for the software.

If that longer query has qualified conversions, a negative phrase "free crm" conflicts with it. A Google negative broad free crm also reaches it because both words appear. The exact negative [free crm] removes only the bare query under that rule, preserving eligibility for the converting modified search.

Start in the search terms report. Separate the complete unwanted query from the converting query and inspect their campaign, landing page and conversion actions. Confirm that the valuable outcome is relevant to the business rather than a weak engagement event that merely looks like a sale.

Then test the proposed exact negative against active keywords, advertised products and converting searches at the intended scope. If it conflicts with an active keyword strategy, resolve the targeting decision before publishing. A smaller exclusion is still a conflict when it blocks traffic the team deliberately buys.

After application, check both sides of the decision. The unwanted bare query should be excluded at that scope, while the valuable longer query should retain an eligible path. Report visibility can be incomplete, so combine query review with targeting diagnostics rather than treating an absent row as conclusive evidence.

Add observed unwanted variants deliberately

Google and Microsoft negative keywords do not expand to close variants. An exact exclusion for a singular query does not automatically remove its plural, misspelling or synonym. Each unwanted full query needs separate consideration, or a justified wider rule that covers the observed family.

Preserve the original search wording when grouping intent. A report can place free crm and free crms in the same analytical category, but a Google upload containing only [free crm] does not inherit the category's coverage. Normalizing the review table must not silently change the native exclusion boundary.

Avoid creating spelling permutations simply to make a list longer. Review actual observed variants and known business exclusions, then test them against valuable queries. Excessive speculative entries make ownership and troubleshooting harder while doing little to establish whether the account's important unwanted searches are covered.

If new unwanted modifiers recur, compare them with protected modifiers before expanding to phrase. A phrase can reduce repeated additions, but only when the sequence remains unsuitable across longer searches. The phrase match negative keywords guide shows the extra coverage and the corresponding risk.

Exact negatives can remove an unwanted campaign path

Traffic sculpting uses exclusions to prevent a query from serving through an undesired campaign or ad group. An exact negative is useful when the routing decision concerns a complete query rather than every search containing a phrase. It is a restriction on eligibility, not a command that forces another campaign to serve.

Suppose separate campaigns cover general running shoes and trail running shoes. The business wants trail running shoes handled by the trail campaign because its landing page and budget reflect that category. Adding [trail running shoes] to the general campaign removes that exact query from the general destination.

The exclusion does not automatically route buy trail running shoes or running shoes for trails. Those are different complete queries. Review their actual destinations before adding more negatives. Positive matching can expand while negative exact stays narrow, so a neat keyword structure does not guarantee equally neat search term routing.

Before blocking the general campaign, confirm that the trail campaign has suitable positive targeting or product eligibility, a relevant landing page, appropriate geography and a usable budget. Otherwise the query may lose a viable route without gaining another one. A negative does not create demand or targeting eligibility elsewhere.

Avoid reciprocal exclusions that remove every route for the same search. Also check shared lists and account level rules that could block the intended destination. The campaign and account level negative keywords guide explains why a local routing rule should not become a global exclusion.

A narrow match type can still have a wide reach

Exact describes which query is excluded. Scope describes where that exclusion applies. An exact negative at account level can block the same complete query across eligible campaign inventory, including a campaign where it is commercially valuable. Narrow matching does not make an account wide choice safe by itself.

Use an ad group exclusion for a local routing issue and a campaign exclusion for an offer specific boundary. Shared lists belong to groups of campaigns that share the same business rule. Account level exclusions need a rationale that remains valid across the account, rather than only in the report being reviewed.

For Shopping, assess the advertised products and supported campaign or ad group controls rather than looking only for a positive search keyword. For Performance Max, use campaign or account negative controls where the platform allows. Do not assume every campaign type supports the same list attachment workflow.

Keep Microsoft exact distinct from Google broad imports

Microsoft Advertising supports negative exact and negative phrase, but not negative broad. Negative exact there also excludes the specified complete search without expanding to close variants. Additional words or changed word forms need separate review, just as they do in the Google exact workflow.

When importing exclusions, preserve the explicit match type and destination. A Google broad negative converted to Microsoft exact becomes much narrower, even if the wording stays the same. Check query coverage rather than judging an import by whether the row count matches. The Microsoft guide provides the network context.

Amazon negative exact can include close variations

Amazon Sponsored Products supports negative exact and negative phrase keywords, but its matching rules differ from Google and Microsoft. Negative exact can exclude the specified full shopping query and close variations. Do not assume every spelling or plural stays eligible merely because that would be true under a Google exact exclusion.

Evaluate an Amazon negative against the advertised product, its relevant attributes and the shopper's request. If a stainless steel product cannot satisfy a plastic product search, a scoped negative can make sense. Check related catalog items before applying the exclusion across a campaign that advertises several materials.

Amazon harvesting workflows sometimes move a useful query from an automatic campaign into a manual campaign and add a negative exact in the source. Verify the destination's targeting, bids, budget, product availability and eligibility first. The negative removes source eligibility but does not guarantee delivery through the new campaign.

Use negative product targeting for an unwanted eligible ASIN or product placement rather than trying to solve every placement problem with a keyword. The Amazon search term report guide explains why query exclusions and product exclusions need separate review and platform appropriate bulk fields.

Measure the decision beyond the exclusion count

Keep a change record with the query, reason, match type, destination and protected alternatives. Check subsequent reports for recurring unwanted variants and for changes around the intended destination. Evaluate mature conversions and business outcomes, not just a decline in clicks after adding negatives.

Revisit exact negatives when the offer changes. A business that adds a product tier, material or service can make an old exclusion obsolete. Remove or revise the relevant entry at every applicable layer. Adding a positive target cannot override an exclusion that still applies.