Google is removing campaign-level language targeting from Search campaigns, and from the Search inventory inside Performance Max, in a rollout landing in late September 2026. The setting is not being replaced with another setting — Google now decides which language to serve using the language of your ad copy, the language of your landing page, and its own read of which languages the user understands. Language criteria already sitting on your campaigns can stay; they just stop doing anything on Search. If you run one language, this is a non-event. If you run English and Spanish side by side, the thing that kept them apart just left.
What Google actually removed
The announcement went out on the Google Ads Developer Blog on 13 August 2026 and the rollout arrives in late September. Three things are worth being precise about.
Search campaigns lose the campaign-level language setting outright, and so does AI Max for Search. Performance Max is a split decision: the setting stops governing Search inventory but still applies to YouTube, Display, Discover and Gmail, so a Performance Max campaign keeps its language setting and only half of it still matters. And on the API side, adding or updating CampaignCriterion.language on a Search campaign now returns ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT.
What replaces it is not a control. It is a matching system. Google reads the language of the ad creative and the landing page, combines that with user-level language signals, and uses ad group prioritisation to pick which ad serves when more than one qualifies. Google's own framing is that behaviour is not really changing — the language targeting help page has already been rewritten around ad language rather than campaign settings, and the developer blog post says existing criteria can remain but will no longer influence Search targeting.
That framing is accurate for most accounts. It is also doing a lot of work.
"No restructuring required" holds until you run two languages
Google says you do not need to restructure, and that is true. Keep your separate English and Spanish campaigns. We are keeping ours.
But separate campaigns were never only about targeting. In a Dallas–Fort Worth service account — which is most of what we run — English and Spanish get split for four reasons at once: separate budgets, separate bids, separate creative, separate landing pages. The language setting was the wall that made the first two mean something. Take the wall out and the budgets are still separate on paper, but both campaigns are now eligible to serve to the same bilingual user, and Google decides which one wins that auction.
The setting you lost was a budget fence, not just a targeting control. That is the part the news coverage keeps skipping.
Here is the concrete version. A home services client runs a $4,000 English campaign and a $1,200 Spanish campaign. The $1,200 exists because someone decided, deliberately, that Spanish-language demand deserved protected spend and would otherwise get starved by a bigger English campaign with better historical data. Nothing in the new system honours that decision. If Google's read of a bilingual searcher favours the English ad, the Spanish campaign underspends and the English campaign absorbs the demand, and your client's reporting shows a Spanish program quietly shrinking for reasons nobody wrote down.
None of that is Google behaving badly. It is a genuinely reasonable matching system. It just means the intent behind your structure now has to live somewhere the machine can read.
Your creative and landing page are the targeting now
This is where the work is, and it is unglamorous.
Every ad group needs ad copy in exactly one language, and every final URL needs to be a page in exactly one language. The failure cases we find most often in audits:
- A single URL serving both languages behind a switcher. Google crawls one version, usually the default, and the Spanish ad points at a page it reads as English. Give each language its own URL.
- Mixed-language pages. An English hero, Spanish body copy, an English form and an English footer. Very common on pages that were translated halfway and never finished. It reads as neither language cleanly.
- A missing or wrong
langattribute, and no hreflang. Both are cheap to fix and both are signals Google already uses. If the HTML sayslang="en"on your Spanish page, fix that today. - AI-written assets drifting across languages. If you have Automatically Created Assets or AI Max text customization enabled, Google can generate headlines that do not match the language you intended for that ad group. Worth reviewing per ad group — we covered the brand-control side of this in our AI Max rollout playbook.
Fix the pages and the new matching system mostly does the right thing. Leave them ambiguous and you are asking a language model to guess what you meant.
The API error that will break your automation first
The reporting change is slow. This one is immediate.
Anything that builds a Search campaign from a saved template and sends a language criterion with it will now fail outright. Agency onboarding scripts are the classic case: one blueprint that spins up a new client's campaign structure in a few minutes, written once, working for three years, and it sets the language because of course it does. Same story for bulk upload sheets, third-party campaign builders, and the n8n or Zapier flows plenty of agencies use to provision accounts.
The fix is small. Remove language criteria from any create or update call that touches a Search campaign. Leave them on Performance Max, where the setting still governs the non-Search channels. Then run the flow against one account before you point it at the whole book.
If you have been through the recent Google Ads Data Manager API migration, this is the same class of problem: a field that has been safe to send for years suddenly becomes an error, and the first symptom is a silent failure in an automation nobody has opened since it was built. Go find those scripts now rather than during a client onboarding call.
The reporting hole nobody has filled
Google has not announced any language-level reporting to go with this. There is no column telling you which language actually served, and no performance breakdown by user language.
For most advertisers that is a nuisance. For anyone documenting language coverage for compliance — healthcare, legal, financial services, anything with a language access obligation — it is a real gap, because campaign structure used to be the documentation.
The workaround is the landing page. If each language lives at its own URL, the landing page report in Google Ads and the page path dimension in GA4 both become a serviceable proxy for what language the user was actually shown. Tag the final URLs so language is readable downstream, rebuild your client-facing language breakdown from the page dimension instead of the campaign name, and label the campaign name for what it now is: a budget bucket, not evidence.
And take your baseline before the rollout hits the account. Export 30 days of spend, conversions and cost per conversion per language campaign right now. Without a clean before, every shift in October is going to look like it might be seasonality, and you will spend a week arguing about it instead of fixing it. We make the same argument about rebaselining after the attribution migration — the platform changes underneath you, and the only defence is a snapshot taken before it does.
What this actually means for local bilingual advertisers
If you are running Spanish-language search in a market like ours, the honest read is that this is a small net negative that is easy to manage and expensive to ignore.
You lose a control that was doing useful work. You gain a system that will probably serve the right language most of the time, because ad copy and landing page language are strong signals and Google has been using them for years anyway. The accounts that get hurt are the ones where Spanish was a half-finished afterthought — translated headlines pointing at an English page, one budget line item, no separate tracking. Those accounts were already leaking. The change just makes the leak visible.
Accounts with real Spanish creative, real Spanish landing pages and separate measurement will be fine. That is also the structure that was already working better, which we go into in our Dallas local SEO guide — the language of the page has been the real targeting signal on the organic side for years. Paid just caught up.
The bottom line
Do four things this week. List the Search campaigns still carrying a language criterion. Confirm every language has its own single-language URL with the right lang attribute. Strip language criteria out of any script that creates Search campaigns, and leave Performance Max alone. Export a 30-day per-language baseline before the rollout reaches you.
Then watch the spend split weekly for a month and only move on a shift that holds for three weeks. One noisy week after a platform change is not a signal, and the most common mistake we see is an agency reacting to week one and never finding out what week three would have said.
If you are running bilingual campaigns and are not sure whether your landing page signals are clean enough to carry the targeting on their own, that is exactly the kind of thing we check in a free automation audit — we will look at the language criteria in the account, the page-level signals behind every final URL, and the scripts that are about to start throwing errors.