The Google Ads AI Max Auto-Upgrade Is Live: What It Flips On and What It Breaks

The Upgrade Is Not Optional, and It Is Happening Now

The Google Ads AI Max auto-upgrade started on September 1 and runs through the end of this month. If you have Search campaigns using the campaign-level broad match setting or Automatically Created Assets, Google is moving them into AI Max in place, on its own schedule, whether or not anyone on your team clicks a button.

I want to be precise about what this is and what it is not, because most of the coverage is written for the person staring at the Google Ads UI. That is not where the pain lands. It lands in your reporting pipeline, on the landing pages you already optimized for organic, and in the joins your analysts built when they assumed the URL on the ad matched the URL a person actually saw.

This is a paid search story with an SEO problem baked inside it. Here is the honest read.

What AI Max Actually Changes

AI Max is not a new campaign type. Your campaign IDs survive the migration, so nothing obvious breaks in a time series on September 1. What changes is the machinery underneath.

Two cohorts are in scope this month:

• Campaign-level broad match campaigns. These are upgraded with search term matching turned on by default.
• Automatically Created Assets campaigns. These are upgraded with both search term matching and text customization turned on.

Standard Search campaigns built on Responsive Search Ads with keyword-level match types are not being migrated. If you never touched campaign-level broad match or ACA, you are not in the September queue. Dynamic Search Ads were originally slated for this window too, but Google pushed that migration to February 2027 after advertiser feedback about fourth-quarter risk. That is a reprieve, not a pardon.

One useful detail: since early August, you can no longer create new campaign-level broad match or legacy ACA campaigns. That means the affected set is fixed and countable today. You can build the exact list of campaigns in scope right now instead of guessing.

AI Max left beta this past summer, and Google's own number is roughly seven percent more conversions or conversion value at a similar CPA or ROAS when the full feature suite is running. I treat that figure the way I treat every vendor-reported lift: directionally interesting, not a promise, and worthless without your own holdout to check it against.

The Part That Should Worry an SEO

Here is the headline buried in the settings. AI Max ships with final URL expansion, and when it is on, Google decides which page on your site receives the click. Not you.

For years, the advertiser controlled the destination. You wrote the ad, you pointed it at a page, and that page was the page. Final URL expansion breaks that contract. Google may replace your final URL with a different page it judges more relevant to the query. It requires text customization to be enabled, which is exactly why the ACA cohort gets both settings switched on together.

Think about what that does to the work you have already done:

• The landing page you hand-tuned for intent, proof, and conversion can be swapped for a page Google picked from a crawl.
• Ad copy and destination can drift apart, which is the whole reason ad-to-page governance exists.
• The organic page you spent a quarter earning authority for can start absorbing paid clicks it was never designed to convert, with no note to anyone.

This is why I keep telling teams to stop treating these channels as separate departments. I wrote the case for that in running paid and organic search as one system, and final URL expansion is the sharpest example yet. The same URL is now a paid destination and an organic asset, chosen by two different algorithms, measured in two different reports. If your paid and organic leads do not talk, this update will quietly put them in conflict.

The Data Join That Fails Silently

The reporting layer is where careful teams get caught. AI Max introduces new surfaces in the API: a search term match source segment, a combined search-term-to-ad view, and an expanded landing page view. Those are additions you can adopt on your own timeline.

The silent one is final URL expansion. Because the page a person landed on is not always the final URL stored on the ad, any join keyed on that URL degrades without throwing an error. Your dashboard still renders. Your numbers still add up. They are just quietly wrong, because the URL you are joining on is no longer the URL that carried the click.

If you have invested in a clean data spine, this is precisely the kind of break it exists to catch. If you have not, this is your reminder to read server-side tagging and the future of marketing data before the discrepancy compounds across a full quarter. And when the destination URL becomes an algorithmic decision rather than a fixed field, your models need to account for it, which is the entire argument I made in attribution in a multi-touch, AI-mediated world.

There is a second-order effect worth naming. Search term matching works on inferred intent, not the exact wording of the query. Google clarified this late last year, and it explains a lot of the reporting discrepancies advertisers keep flagging. The term you see reported and the intent the system acted on are not the same object. Do not build a narrative on search term data as if it were a transcript. It is a summary.

The AI Max Blast Radius Audit

Here is the checklist I am running with teams this month. Work it in order. It takes an afternoon, not a sprint.

1. Scope the blast radius. Pull every Search campaign using campaign-level broad match or ACA. Since new ones cannot be created, this list is final. Rank the campaigns by spend so you know where a mistake costs the most.
2. Decide before Google decides. For each in-scope campaign, choose one path: migrate deliberately now with your own settings, or opt out where the account is mature and the defaults would hurt. Letting the auto-upgrade catch you on its schedule, with its defaults, is the one choice I would not make.
3. Govern the destination. If you allow final URL expansion, set URL inclusions and exclusions so Google cannot route paid clicks to pages you would never pay for. Protect your strongest organic pages and your thinnest conversion pages first. This is ad-to-page governance, and it now matters as much as ad copy. Your URL design has to age well because the algorithm is reading it as a menu.
4. Fix the join before it lies. Confirm your reporting keys off the expanded landing page view, not the ad's stored final URL. Adopt the new search term match source segment so you can separate keyword-driven from keywordless traffic. Do this before the month closes, not after the QBR.
5. Watch the learning window. Review the search terms report weekly for the first 30 to 60 days. That window is when the system learns most from your negatives and exclusions, so your inputs there shape its behavior far longer than any single week of spend.

One more thing that is easy to miss: a separate change later this month removes certain language targeting settings, and that one touches everyone, not just the AI Max cohort. Single-language advertisers can shrug. Anyone running multi-market Search should read the fine print.

The Honest Bottom Line

The upgrade itself is not the danger. Google is not seizing your budget, and the feature set can genuinely perform. The danger is being moved without knowing it, keeping defaults you never chose, and reporting on joins that broke in silence.

Numbers over noise. Do the audit, own your destinations, and verify the lift against your own holdout instead of a vendor's average. Control the settings while you still can, because after September the defaults become the baseline everyone forgets they never picked.

If you are staring at a list of in-scope campaigns and want a second set of eyes before you commit, the channel here is open by introduction. Bring your campaign list and your reporting schema. That is where this conversation actually gets useful.