“$100 spent, zero conversions. Exclude it.” That is not a decision rule; it is a candidate-selection query with a delete button attached. A spending threshold earns a search term a place in Claude’s review queue. Evidence earns it a negative. The distinction matters most after an offer or demand shift, when yesterday’s conversion history can mislead in both directions. Say you cut two product lines and restructure pricing six weeks ago: the report now mixes evidence about the old business with evidence about the new one. Before Claude changes anything, it needs the current offer, conversion lag and exclusion scope. Otherwise, the cleanup can remove traffic you still want.

Myth 1: “Zero recorded conversions proves a search term is waste”

It is the cleanest-looking column in the search-terms report. Cost, clicks, conversions: three numbers, and the third one reads zero. No interpretation required. That is the attraction.

The problem is what the zero is made of. Google’s conversion-lag documentation says conversions can be reported up to 90 days after the click. Recent periods can look weaker than they are because spend reports fully while conversions are still arriving.

A term that spent $100 last Tuesday is not necessarily a failed term. It may be an unfinished one. Recent spend and mature conversion evidence are not the same thing.

Ask Claude to separate mature results from recent clicks

List search terms above my review threshold. For each, show the date range,
spend, conversions, and the account's conversion-lag evidence
(days-to-conversion distribution and conversion window).
Separate terms with mature results from those still awaiting conversions.
Flag missing evidence and conclusions the data cannot support.
Make no changes.

That prompt forces a distinction the report flattens. But time is not the only explanation for a zero. Two more possibilities sit in the same column:

  • A conversion happens offline and never returns to the platform.
  • The tracker drops the conversion entirely.

In a long r/googleads thread on lessons learned only after wasting budget, the top-voted lesson is that bad tracking distorts everything that follows. You optimize toward whatever is easiest to measure, then call the measurable thing success.

Ivitskiy makes the practical distinction in his discussion of terms with no recorded conversions: a query may describe your service perfectly and still need a landing-page fix rather than a negative.

My rule: establish whether the zero is mature and credible before treating it as evidence against the query. Claude should flag an unexplained zero, not quietly turn it into an exclusion.

Myth 2: “The terms that converted last quarter are my safe terms”

This one survives because the report sorts it into existence. Rows with conversions rise to the top, and a list with conversions attached looks like a keep-list. Nobody wants another audit of the keep-list. There is already enough spreadsheet in the day.

But those conversions describe the offer that existed when the clicks happened. Offers move. Pricing changes. Product lines disappear. A segment that was profitable last quarter may no longer be a segment you serve.

After that kind of shift, the report contains two different questions disguised as one:

  • Did this term work for the offer available then?
  • Does this term describe something worth buying from you now?

Historical performance is evidence, not permanent permission to keep buying. A converter under the old offer can be irrelevant to the new one. Equally, a relevant term with weak old results may deserve a fresh review rather than an automatic exclusion.

Give Claude the current offer before asking for exclusions

Evaluate these search terms against this current offer and these disqualifiers.
Separate historical performance from present-day relevance. Flag terms whose
recorded conversions came from an offer we no longer sell or a segment we no
longer serve. Separate evidence from before and after the offer change.
Rank by present-day fit, not by past conversion count. Make no changes.

I put the offer in the prompt because the search-terms report does not explain the business change. It can show a converting term for a discontinued service and make it look like a keeper right up until you notice the landing page 404s.

The same discipline applies when demand shifts: old results remain evidence about an earlier period, not a guarantee about this one. Tell Claude what changes before asking it to interpret what follows.

Keep the history. Judge relevance against what you sell now.

Myth 3: “A search term and a keyword are the same thing”

They look alike in the report, and that is where the damage starts. The keyword is what you target. The search term is what somebody types. Match type connects them; it does not make them interchangeable.

When one query looks bad and you pause the keyword behind it, you do not remove one query. You stop the keyword from matching other queries too, including ones that work. That is a large operation for a small diagnosis.

Negatives do not behave like positive keywords either. A positive keyword’s close-variant behavior is not a reliable guide to how negative keywords match. Google’s example is useful: a flowers negative blocks red flowers but not red flower. Cascader calls this gap leakage: a cleanup built around one word form can leave another running.

That creates two separate mistakes. One blocks too much by pausing a useful keyword. The other blocks less than intended by assuming a negative covers variants it does not.

Make Claude identify the object it wants to change

For each row, show the exact search term, the keyword that triggered it,
and the action you propose. Separate 'this query is irrelevant' from
'this keyword is underperforming.' If the query is the problem, propose
the narrowest negative that blocks it. Specify the match type and explain
what else it could block or leave running. Make no changes.

An irrelevant query from a useful keyword calls for a negative, not a keyword pause. A keyword that no longer deserves spend is a separate decision. I want Claude to explain which problem it sees before proposing either surgery.

Do not approve an action until the row names both the query and the keyword behind it.

Myth 4: “A bad query belongs in the account-wide negative list”

The instinct is to clean up wherever your eyes happen to be sitting when the bad row appears. At one extreme, the same junk term gets added separately across ad groups. At the other, one bad query gets a word banned across the account, including campaigns nobody checks during the cleanup.

Same habit. Bigger coat.

A negative outlasts the report that prompts it. Cascader’s term for the risk is blast radius, and scope helps determine it. An account-level list applies across the account’s Search and Shopping inventory. Google’s warning is plain: too many negatives can mean reaching fewer customers.

The failure can also be quiet. A negative that overlaps an active keyword can prevent ads from showing for matching searches without pausing that keyword. The keyword still looks active. The traffic is missing. Those are not contradictory observations, which is precisely why the problem survives.

I cover that failure in more detail in The Negative Keywords Mistake That Is Costing You Conversions.

Before saving a negative, BattleBridge recommends a test worth stealing: play it against the last 90 days of converting search terms. If it would block useful converters, narrow the scope or drop the proposal.

There is an important connection to Myth 2 here. A historical conversion is a warning to inspect, not an automatic veto. Check whether that converting query still fits the current offer. Otherwise, the safety check can preserve traffic for a product you no longer sell.

Require a reason for the scope, not just the exclusion

For each proposed negative, show the intended scope (account, campaign or
ad group), match type, useful traffic it could block, and why a narrower
action would not suffice. Test each proposal against my last 90 days of
converting queries. Flag overlaps and check whether those queries still
fit the current offer. Make no changes.

List length is not proof of control. Across audited accounts, Igor Ivitskiy finds almost no relationship between negative-list size and zero-conversion waste share, with Pearson’s r ≈ -0.10. A longer list can document more activity without demonstrating a better result.

Name the scope before writing the negative. If Claude cannot explain why the narrower action fails, I do not approve the broader one. One bad query is not an account-level pattern.

Myth 5: “One-step undo makes careless exclusions harmless”

This is the one I find hardest to kill because the first half is true: undo works. Restore the setting and the exclusion disappears. It feels reasonable to conclude that the cost of guessing is close to zero.

But undo restores a setting, not the auctions it already costs you. An account-level negative that runs for three wrong weeks can withhold your ad from matching searches throughout that stretch. Removing it does not recover the clicks you miss. A competitor is not keeping them warm for you.

Conversion lag makes the mistake harder to spot. The first convincing sign of trouble can arrive well after the change, when the exclusion no longer feels recent enough to be the suspect.

Cut-paper ledger with an undo arrow as auction tickets marked “missed” fall off the table

groas logs every change with its reason, and any change can be undone in one step. That is the right tooling, but the log and the undo button do different jobs. The log makes the decision auditable: what changes, at what scope, and why. Undo provides the emergency exit. Neither supplies evidence that was missing when the decision was made.

The workflow I want is deliberately less dramatic than “find waste and fix it”:

  1. Claude produces a shortlist with evidence attached.
  2. You review and approve specific exclusions.
  3. The approved changes land with their reasons recorded.
  4. After one full conversion-lag length, you compare outcomes with the pre-change baseline and revisit the reasoning.
Apply only the negatives I approve in this list. For each, record the
supporting evidence, scope and match type in the change log. Set a review
date one full conversion-lag length out. At that review, compare outcomes
with the pre-change baseline and flag evidence that challenges the original
decision. Make no unlisted changes.

Five fields before permission to act

Every review prompt here removes the delete button until the reasoning catches up. The standard I use for a tool claiming to find wasted search terms is the same standard I use for Claude: what comes back with the row?

A threshold gets a term into the queue. Before approving an exclusion, I want these five fields:

  1. Date range and lag position. Where the clicks sit against the account’s days-to-conversion distribution, whether results are mature, and whether the period crosses an offer change.
  2. Downstream evidence. Recorded conversions, any available offline or CRM outcomes, and present-day fit with the offer. A zero nobody checks against sales remains an unverified zero.
  3. Search term and triggering keyword. Two different objects. The proposal must say which one is the problem and why.
  4. Scope and match type. Exactly what gets blocked, at which level, and in which matching form. “Add a negative” is not a complete instruction.
  5. Blast radius. Useful traffic the action could block, checked against the last 90 days of converting queries and interpreted against the current offer.

The opening instruction returns a search term, some spend and a zero. It does not establish whether the term is irrelevant, whether the result is mature, or what the proposed exclusion takes with it. Calling that a completed analysis does not make it one.

For the scoreboard, I prefer the metric Ivitskiy watches: month-over-month share of spend on zero-conversion terms, rather than negative-list length. It still needs the lag and tracking checks above. But it asks about spending outcomes instead of congratulating the account for accumulating prohibitions.

The prompt set for working through a live account with Claude is in this walkthrough. I run the workflow through groas rather than stopping at a CSV export because the back half matters: approved changes land with their reasons recorded, and each can be undone in one step. The export supplies rows. The workflow preserves the decisions behind them.

That is a reason to make review easier, not permission to skip it. The undo button is so persuasive because it does exactly what it promises. It restores the setting. It does not restore the auction.