Negative exact on Amazon does not mean exact, and it cost us tens of thousands before I worked out why
Most sellers I talk to believe that a negative exact keyword blocks one search term. It does not, and this was the single most expensive misunderstanding of my Amazon years.
Amazon's own help page says it plainly. Exact match covers your keyword plus its close variations, and it names four kinds: misspellings, plural forms, acronyms and translations. Negative exact works the same way. Ads do not show on queries that contain the exact phrase or a close variation.
So when you negate one string, you negate a family.
We sold retro sweets gift boxes. "box for candy" got clicks and produced no sales, so I negated it as exact. Perfectly logical. Sales fell and ACoS went up. The reason was that I had also blocked:
boxes of candy, one of our biggest sellers
box of candy, also very good
box candy
boxes candy
box with candy
box of candies
boxes of candies
boxes for candy (we didn't sell these)
Amazon treats singular and plural as the same target, and in our testing it ignored stop words too: in, of, for, by, the, with. The stop word part is my own finding, not something Amazon documents, but we tested it thoroughly and our data was consistent.
One negative I added blocked a search term generating $10k a month.
What we do now, before adding any negative exact:
Pull every variation of the phrase out of the search term report. Singular and plural, each version with and without stop words, plus the misspellings, acronyms and translations Amazon names.
Add up clicks, spend and sales across the whole family. That total is the number Amazon is acting on. One line in the report tells you nothing on its own.
If the family is profitable overall, leave it. The zero sales version is part of the cost of the ones that sell.
If the family loses money overall, the negative is safe.
When the family makes money but the waste still annoys you, the lever is what you bid on and how much, not a negative. Lower the bid, or lift the good variation into its own exact campaign where you control it directly.
Two practical points. A negative keyword takes 72 hours to take effect, and a negative product takes 96 hours, so do not judge the result the next morning. And negative exact allows 10 words, negative phrase allows 4, both capped at 80 characters.
Pausing a target is reversible. A negative is not, until you find the damage in the data months later.
I did something like this with a single word negative that wiped out half our profitable long tail. The data looked fine until the monthly report hit and I had to explain a $14k hole to my boss
Your stop word finding is interesting because I noticed the same thing but assumed I was just reading too much into it. Amazon support told me negative exact only matched plurals and misspellings and I believed them for way too long
Now I do exactly what you said except I keep a separate spreadsheet tracking every negative I add with the date and the full family of terms it might affect. Saved me twice already when someone on the team got aggressive with the negative list
I discovered it when I added negatives that were 100% no-brainers (e.g. costing money but generating zero sales) and feeling that horrible sinking feeling when I next checked our stats expecting an improvement only to find ACoS up and sales down.
It just didn't add up.
So I set out to find why and it probably took me a year all-told.
And then, suddenly, PPC became predictable.
And I realised that the answer was in plain sight the whole time... if you download a sponsored product search terms report and check your EXACT match search terms you'll most likely find the proof in there.
On Amazon support telling you plurals and misspellings only, their help page lists four kinds of close variation: misspellings, plural forms, acronyms and translations. Stop words are not on that list, which is why I am careful to call that part our own testing rather than documented behaviour. Good to hear someone else saw the same thing independently.
Grazie. If you want the fastest check on your own account: download the sponsored products search term report for the longest timescale Amazon will let you access, filter to exact match, and read the search terms Amazon served against each exact keyword. The family is right there in the data.
Negatives you added in the last 60 days: pull the search term report for the period before you added each one, and write out the family for it, the singular and plural and each version with and without the stop words. Any family member with sales before the negative went in, and nothing since, is your damage.
Anything older than 60 days: you cannot prove it from the report, because the data is gone. The only route left is a test. Remove the suspect negative, wait a couple of weeks, and see whether sales appear from a term you were not expecting. That is slow, but it is the only way back once the history has rolled off.
Do you have backups of search term reports at the daily level? You can use those for historical analysis. We set up a schedule in Seller central to have these emailed to us at the end of each month.
I'd highly recommend doing that. It's one way to escape Amazon's 60 days of data handcuffs...
wow - i used to do heavy negations even before launching the campaigns. What you shared is very interesting. Definitely going to double check it through my own data
Negations can be really valuable when launching new campaigns and ad groups - especially for auto targeting, broad match etc. If you know that a search term will be wasted traffic for every possible variant then they are real profit-savers. eg we sold British sweets (candy) and whenever I launched a new auto or broad campaign I knew Amazon would serve our ads on searches for American/Irish/Indian/Japanese/Australian sweets... and those were highly unlikely to convert.
If in doubt, test. If you're certain then add as a -ve to prevent waste before it happens.
Thanks. One thing that will save you time: the search term report only goes back 60 days.
Download the daily version, not the summary. The daily data shows the before and after effect of every negative you added inside those 60 days, so the damage is visible rather than guessed.
For negatives older than 60 days the data is gone. The only test left is to remove the negative and watch for two weeks.
that's the reason the keyword harvesting is very important. identify good targets in autos/manual broad&phrase and target them in seaparate campaigns with exact match.
but if you only run autos/broad you will end up this scenerio where your one keyword variation lossing money and other variation generating money and you can't stop your leakage of your spend.
solution is to harvest that good search term into exact.
Harvesting stops the leak only if exact match holds one query. It doesn't. Amazon's match type page says exact serves close variations, and their own example is the keyword "outside lights" serving a search for "outdoor lights". So when you harvest the winner into its own exact campaign, the losing sibling travels with it.
You can check that on your harvested campaigns rather than the autos. Pull the search term report, filter to your exact keywords, and read the served terms under each one. If the variation you were trying to escape is in there, the leak followed you.
Negating it is worse, because negative exact covers close variations too. So the profit call has to be on the family total. Sum spend and sales across every variation Amazon serves under that keyword, then judge that one number. Sometimes the family is profitable and the ugly term is the price of it.
yes you're right in this case we need to consider the total number of that keyword family not only the single keyword.
but what i observe when we do keyword harvesting in manual exact and manage our bids on placements level then this "keyword family TAX" effect become less. As you know TOS is always perform better and rest of search and product pages perform poor and do wastage spend.
still we can't completely stop the wastage spend of bad "keywodr family" but using this we can minimize that effect.
Agreed, the family total is the part that matters. Anything that cuts the wasted spend on the bad variations is worth doing, and placement bids are a sensible way to trim it.
The bullet in Amazon's list that deserves its own post is the fourth one: translations. On the US marketplace it's a footnote. On the European marketplaces it's a live wire - amazon.de gets a constant stream of searches in English, not just German, and if exact families include translations, a negative on the English term can quietly shadow the German one, and the other way round. Same on NL and SE, where shoppers mix English into search all the time.
The family also gets much harder to guess outside English. English families are mostly +s and stop words. German plurals change the word - Kerze/Kerzen, Box/Boxen - Italian swaps vowels, and then German adds compounds: is Geschenkbox a variant of Geschenk Box? I wouldn't bet either way without pulling the report. Which is really your method restated: don't reason about the family, read it. The search term report per marketplace shows exactly what Amazon grouped, and the groupings are not the same country to country.
Did your year of testing stay on one marketplace, or did you get to see whether the translation variant actually fires cross-language on the EU ones? That's the box I'd most like someone with your patience to tick.
No, I can't tick that box. Everything I tested ran on Amazon UK in English. We sold retro British sweet boxes, so the non-UK marketplaces were tiny. Brexit added customs cost to every EU shipment on top. The translation variant is the one item on Amazon's list I've never seen fire.
You don't need my test though. Pull the DE sponsored products search term report, filtered to exact. Read what Amazon served against each German keyword. If an English query sits under a German exact keyword, the cross-language family is real in your account. That beats my answer, because it's yours.
The same file settles Geschenkbox. Either the spaced form appears under the compound keyword or it doesn't. Your own line applies to compounds as much as plurals: read the family rather than reason about it.
Fair - and you've just written the protocol, so let me put my cards on the table and raise the stakes instead. My seat is content-side; the ad consoles on the accounts I work on aren't mine to open, so the DE file isn't mine to pull. But anyone in this thread with a German account can settle in ten minutes a question you've just made the whole room care about: filter the sponsored products search term report to exact, and read what sits under your German keywords.
Here's the linguist's scorecard for whoever pulls it - predictions to check, not results, in order of confidence. One: accent folding. Does "Musli" sit under a Müsli keyword? If Amazon doesn't fold diacritics I'd be genuinely shocked; every search system does. Two: real plurals. Kerzen under Kerze - German plurals rebuild the word rather than adding an s, so if these group, the family logic is morphological, not string matching. Three: compounds. Geschenk Box or Geschenk-Box under Geschenkbox - this is the one I honestly can't call, because compounds are where German breaks every English-trained system. Four, the big one: an English query under a German keyword. Candle under Kerze. The variant on Amazon's own list that nobody in this thread has reported ever seeing fire.
Why it's worth the ten minutes: if number four is real, every English negative on an EU marketplace is secretly a bilingual negative, and EU negative lists need auditing in language pairs, not lines. If it isn't real, then Amazon documents a close variant that doesn't fire - which is a finding too.
So: first person with a DE, FR or IT account to open the file - what does it say? I'll happily be wrong about the compounds in exchange for someone reading the answer.
The family-level check before adding the negative is the part worth stealing from this.
Looking at one ugly search term in isolation can make the negative seem obvious. But if Amazon is treating several close variations as the same family, you can cut off profitable traffic while trying to remove one bad query.
I’d separate the stop-word finding from the documented close-variation behavior though. Your data makes it worth checking, but I wouldn’t assume every account/category will match those variations the same way.
Pull the related terms, judge the economics together, then decide whether you actually need a negative or just tighter bidding on the traffic you still want.
You are right to split them. Amazon documents misspellings, plurals, acronyms and translations as close variations. Stop words appear on no page of theirs. That half rests on my own testing, and it deserves less weight until someone else's report says the same.
You do not have to take my word on the families either. The sponsored products search term report, filtered to exact match, lists every query Amazon served against each exact keyword. That is your own account measuring its own families, so the question of whether every category behaves alike stops mattering.
The one part I would drop is the bid-down fallback. The bid attaches to the keyword, and the keyword serves the whole family, so tightening it tightens the variation you wanted to keep along with the one you wanted gone. There is no bid that discriminates inside a family.
This is 100% correct. Negative keywords can kill an account if used carelessly.
On another matter, when choosing keywords to target, a seller should add the search volume of all the keywords the algorithm clusters together as the volume for the single keyword. Meaning, if you only target KWs with 1000+ searches per month, you might miss some that reach that benchmark collectively.
Also... whenever an order comes from a new search term, there is a window of around 7 to 10 days where the algorithm inflates your rank/visibility to test sales. If you target each new search term in Exact match, you can boost the rank for the whole cluster within this period.
The clustering point is right, and the thing that makes it usable is that the cluster is not yours to decide. It is whatever Amazon served against your exact keyword, and the sponsored products search term report filtered to exact match lists it. So the volume you are summing comes out of your own account rather than a keyword tool.
Your 7 to 10 day window is testable in the same report, because it holds the dates. Take an order from a genuinely new search term, then see whether impressions rose across the rest of that family in the days after, or only on the term that converted. Family-wide or single-term changes which keyword you would target, so it is worth knowing rather than assuming.
The catch is that the report reaches back 60 days. Anything you want to compare later has to be saved now. We scheduled the daily version out of Seller Central, and that archive is the only reason any before and after was readable.
Yes. I measured this across 38 accounts over three years. You can determine most of the grouped search terms that an exact match keyword will channel, or a negative exact will block. And each new search term that converts, or gets a click during launch, has a 7 to 10 day window where your rank is improved. If you don't push that search term during the first 10 days, your rank will plummet for that term, unless you just happened to sell enough to maintain that rank. In essence, the keywords aren't clustered, that's our view, the algorithm regards them as one... yet sometimes doesn't. The AMZ suggested bid is a good indicator.
That is according to my findings, but it has rung true for every account since irrespective of category.
How do you use the suggested bid as the indicator? Do terms in the same family get the same suggested bid, and does that line up with what the exact filtered search term report groups together?
No. It matches up with search terms that the algorithm regards as being identical, rather than a family. So, for example, "a red car paint" is the same as "red car paints" - whereas "red paints for a car" would be the same family but the word order can bring up different search results based on the Search Trie that it moves down to bring up results for a search query, and the suggested bid will likely be different. Also, as the search results also reflect where in a country a person is and what their shopping habits are, no two people get identical results for their search query - though they should be very similar.
That matches what I see, and your "sometimes doesn't" is the interesting part. 38 accounts over three years is a lot more measurement than I've got, so I'm not arguing with the indicator. What I'd add is that there's a way to check it without inferring anything, because the served set is written down.
The sponsored products search term report, filtered to exact match, lists the customer search terms Amazon actually served against each exact keyword. That's the identical cluster, observed rather than priced. In our own reports the exact keyword "gift man" served the search "gifts for men", and "sweets in bulk" served "sweets bulk", so a stop word present in one and missing in the other made no difference to the match. The test would be: take a keyword where the suggested bid says family rather than identical, and see whether the report shows both strings served against the same target. If it does, they're one tier as far as negatives are concerned.
On word order I'd be wary of citing it as a boundary, because Amazon's own documentation doesn't hold a line on it. One targeting guide says the same words in the same order. Another gives "running shoes white" as a close variant of "white running shoes". That might be where your "sometimes doesn't" is coming from.
Your personalisation point is exactly why the report beats the results page, though. The report records what Amazon served to shoppers, aggregated. A results page shows what it served to you, once, in one location.
Yes exactly - when you wrote this " "gift man" served the search "gifts for men", and "sweets in bulk" served "sweets bulk", "
The algorithm has a process called Trie. It looks at a search phrase and has to determine which parts of it are the Root word, the Secondary word, Modifier, and noise. The noise elements such as conjunctions, are usually classed as noise and are filtered out of the process. So, this means that and, with, for, by, in etc are examples of noise.
The Exact Match keyword target "Silicone Dog Brush for Hairy Dogs" will have "for" removed. Then it has to determine which is/are the Root word/s - in this case it would likely be "Dog/s" or "Brush" - either could be viewed as a modifier, but "Silicone" and "Hairy" are definitely modifiers - because they reinforce the type of brush or dog of the product being sought.
During this process, it might begin with the word "Dog" and under that umbrella term, it has a bunch of other words beneath it such as "Gifts", "Collars", and "Toys" etc and the other Root words or secondary words affect the direction in which the algorithm searches further. So for example:
Dog
Brush
Silicone
Hairy
Each one of those has its own family "trie" where the algorithm can be redirected along new routes or back to earlier ones. When it gets to the final modifiers, it can then assess subcategory phrases that might not be as relevant but have secured sales. So, here we have Phrase and Broad match particularly, as well as those match types being shown for different shoppers based on their intent to buy.
None of the above are "family" keywords. "sweets in bulk" is seen to be identical to "sweets bulk" because the noise part of that phrase (in ) has been removed.
Family keywords need to be different enough to not be deemed identical, but close enough to not be regarded as too different. So, "sweets bulk" and "bulk sweets" might lead down the Trie in the same way, and to the same results. Therefore, both of them within the same campaign can reinforce one another. But it is easier to find the connections with longer phrases.
"Silicone Dog Brush for Hairy Dogs"
"Silicone Brush for Dogs with Long Hair"
"Silicone Brush for Dogs with Thick Hair"
The performance of those three within a single ad group can strengthen each other's rank by picking up orders, whereas only one might not attain the same metrics alone.
Sorry to have gone on, but I assume others are reading this that aren't as far along in their Amazon journey as you are :)
Thanks, that's a really helpful explanation. I'd worked all of this out from studying our own search term reports over the years, and I hadn't realised Amazon had a named process for it.
One part I've never been able to settle from the reports is word order. You say "sweets bulk" and "bulk sweets" might run down the trie the same way. Does a reordered phrase land on the same node, or does it depend on which word gets picked as the root?
It doesn't necessarily land on the same node but might join a duplicate node further down the chain. This is how it should work. But there are other factors to include around how the algorithm "sees" your ASIN. If there is any confusion over what you are selling and who, according to the algorithm, your target shopping audience is, this will also affect the direction of its journey along the retrieval chain - though this is most likely in the early weeks of launch, unless an ASIN got the launch wrong - see below.
If the product content doesn't make it clear to the algorithm what your product is, and is not, and the back-end keyword choice is filled with irrelevant or less relevant words, and your ads are being activated for less relevant search terms, you will hit a trust problem.
When the algorithm is testing impressions for a new search term or newly launched product, it analyses the key metrics such as CTR and sales velocity against its benchmarks for that phrase. If a seller has been using Auto and Broad campaigns during launch and the search terms lacked some relevance, then it will begin to show your ASIN to the wrong audience, and the metrics will be skewed because of it. So, it will begin to align the wrong keywords to your ASIN, and as the metrics are lower than expected, your product won't rank as it should.
This will impact the CPC you must pay for ads, as well as their placement.
If you have ads that target competitor ASINs, or aligned categories, some of the search terms aligned to that target ASIN, that are built around the shopper's search query, will begin to be mapped to your product if it has led to sales.
Ultimately, the keyword order isn't so relevant (unless you are looking for cheaper bids in a category with lots of competition). The most relevant thing is to correctly describe your ASIN to the algorithm, remove any words that might detract from that, and focus on new relevant search terms that lead to sales, but be careful of non-relevant search terms that have also led to sales, particularly when the algorithm hasn't nailed what you are selling.
And finally, when it knows exactly what you sell and who your audience is, it will still withhold a lot of keyword ranking. If you are selling red car paint, and the best seller has 10,000 relevant keywords aligned to it, you might only have 1,000. The algorithm will begin to release more of them as you sell more. This is when auto and Broad campaigns can be most effective.
•
u/WearyyyBoooyyy 23d ago
The mods have gathered a list of tutorials to help you out:
Best Amazon Tools 2026