The day you enable AI Max on a Search campaign you hit a contradiction. Google's own guidance is to wait roughly two weeks before making changes such as adding negative keywords, so the campaign can ramp and the bidding model can stabilise. At the same time, the search terms report starts filling with the wider, automated matching AI Max does — and some of what it matched on is a competitor's brand, a product you do not sell, or a free-version query that has never once converted in your account. Wait two weeks while that spends, or negate it now and risk kneecapping the learning phase?
The resolution is that these are two different instructions aimed at two different problems, and the trap is treating them as one. “Wait two weeks” is about not pruning a campaign faster than it can learn. “Negate the obvious waste” is about not funding queries that no amount of learning will ever make relevant. Both are correct; they just apply to different rows in the same report. This post gives you the rule that splits them: watch the report daily from day one, negate a short list of category errors on sight, and hold everything borderline until the ramp settles. Get that split right and you neither bleed budget on obvious junk nor starve the model of the signal it needs.
What the two-week ramp actually is
When you turn AI Max on, the campaign enters a deliberate exploration phase. The system widens matching beyond your existing keywords, tests queries it has not served before, and tries different creative and landing-page combinations against them to find what converts. Conversion rates frequently dip during the first two to four weeks as this plays out, then recover as the model accumulates data. Google's AI Max reporting guidance reflects this by asking you to leave the campaign alone for about two weeks before significant changes — the ramp is not idle time, it is the model actively learning your account.
The “significant changes” that guidance is protecting are the strategic levers: bids, budgets, conversion-value targets, campaign settings, and a sweeping negative pass that reshapes where the campaign is allowed to go. Change those mid-ramp and you are moving the goalposts while the model is still aiming at them. What the guidance is not protecting is your right to stop paying for a search that was never going to work. Keeping those two apart is the whole discipline here, and the rest of this post is about where the line sits.
Why negating too early can distort the ramp
A negative keyword in an automated, broadly-matched campaign does more than remove a single query — it removes signal. During the ramp the bidding model is still evaluating a wide spread of search space to decide what converts for you, and each query it serves is a data point in that evaluation. Negate aggressively on tiny samples in week one and you prune query space the model had not finished judging, which narrows reach and hands the system a distorted read of what works. This is the same over-negation risk that exists in any broad-match campaign, covered in over-negating and throttling good traffic, only sharper because the campaign is at its most volatile.
That is why the significance discipline you apply to a normal search-term negation — the question of how many clicks before you negate a term — matters even more during the ramp. A borderline query on three clicks and no conversions is not a verdict in week one; it is a query the model may still pair with a better creative or landing page, exactly the kind of combination AI Max is built to discover. Cutting it early forecloses that. The crucial word, though, is borderline. The over-negation warning only applies to queries that had a plausible path to converting. It says nothing about queries that never did.
Negate on day one: the queries that never ride out the ramp
Some queries are category errors, not underperformers, and for those statistical significance is irrelevant — waiting two weeks only buys you two weeks of the same waste. Negate these on sight, from day one, regardless of the ramp. There are four kinds. Brand-safety and clearly off-product queries: searches for something you do not sell or do not want to appear against, which cannot convert however the model learns. Competitor brand terms, when your strategy is to exclude rather than bid on them — AI Max can expand into competitor searches quickly, and the decision to negate or bid on competitor terms does not change just because the campaign is new.
The other two: obvious informational or free-version intent that your account has a long, consistent history of never converting — “how to”, “free”, “DIY”, “salary”, “jobs” patterns that are wrong for a commercial campaign on their face. And high-impression, high-spend, zero-conversion queries that are plainly irrelevant — not a borderline term on a handful of clicks, but the expensive, obviously-wrong searches that are already visibly eating budget. For all four you are not second-guessing the model; you are removing noise it should never have been evaluating as signal. As one AI Max setup guide puts it, negatives in an automated campaign are “essential guardrails” that align the automation with business intent, not optional optimisations you defer.
Let it ride: the borderline queries the ramp is for
Everything that is not a category error gets left alone until the ramp settles. These are the queries sitting on the edge of your intent: a related-but-adjacent product, a query that could be research or could be a buyer, a term that converted once and not again, a phrasing you would not have thought to bid on but that might be exactly the incremental reach AI Max is supposed to find. On small early samples you genuinely cannot tell these apart from winners, and that uncertainty is the point of the learning window — resolving it is the job you enabled AI Max to do.
Hold these not out of caution for its own sake but because negating them early destroys the very information that would tell you whether to negate them at all. A borderline query needs volume and time before its conversion pattern is readable, and the ramp is where that volume accumulates. If you cut it in week one you will never know whether it was a winner, and you will have told the model that a chunk of adjacent search space is off-limits before it finished testing it. Note these terms, resist the urge, and let the campaign hand you a real answer in a fortnight. For the mechanics of isolating the AI Max traffic from your existing keyword traffic while you do this, see segmenting the AI Max search terms report.
How to run the daily pass without disrupting the ramp
Reviewing is not intervening, and the distinction is what lets you watch daily without breaking the two-week rule. Pull the search terms report every day, filter it to the AI Max match source so you see only the expanded automated matching rather than your established keyword traffic, and read it top-down by cost. Looking at the report costs the campaign nothing; the ramp is unaffected by your attention. What you do with what you see is the only thing that can disrupt it, and during the ramp your only permitted action is adding negatives for the four day-one categories above.
Everything else stays frozen. Do not touch bids, budgets, conversion-value targets, or campaign settings during the window — those are the strategic changes the guidance asks you to hold, and they are what actually destabilise a ramping campaign. The daily cadence exists for one reason: AI Max can expand into expensive, obviously-wrong query space fast, and a daily look means you catch a competitor term or an off-product query the day it starts spending rather than finding it in a two-week-later audit with the damage already done. It is a tripwire for category errors, nothing more.
After the ramp: the real negation pass
Once the campaign has stabilised you switch from triage to a full negation pass, and the borderline queries you deliberately left alone are now judgeable. They have accumulated enough data that your normal significance threshold applies, so you work through them on their merits, negating the genuine underperformers and — crucially — grouping recurring patterns into shared negatives rather than adding one term at a time, the approach in pattern grouping versus single negatives. This is the pass the two-week wait was reserving: the one that reshapes where the campaign is allowed to go, done with real data instead of ramp-period noise.
From here the cadence relaxes. The daily pass was a ramp-period measure for fast-spending category errors; a stabilised campaign only needs the weekly-or-fortnightly review you would run on any mature account. Fold the campaign into your standing routine — the broader 2026 search hygiene audit playbook covers that cadence — and when a later forced upgrade or migration reshuffles things again, the post-migration negative keyword audit is the next checklist to run. The ramp-window rule is a one-time discipline for the first two weeks; after that, AI Max is just another campaign that needs its search terms watched.
Related reading
For the full set of reconciliations to run when a campaign first moves onto AI Max, see the AI Max migration search-terms checklist. For the significance question underneath the “let it ride” call — how much data a single term needs before a negation is a verdict — see how many clicks before negating a search term. And for when a negative you add during the ramp silently blocks a keyword you still want serving, see AI Max negative keyword conflicts.