Google is removing the campaign-level language setting from Search and AI Max for Search campaigns from late September. Language matching moves to Google’s systems, which will serve ads based largely on the language of the ad plus signals about which languages a user understands.
Google says no action is required. That is true in the narrow sense that nothing will break on the day. It is not true for any account that used language targeting as a structural device.
Key Highlights
- Late Sept: Rollout begins
- Zero: Manual language controls left in Search
- A total of four: PMax channels where language settings still apply
What Actually Changes?
For Search and AI Max for Search, the campaign-level language setting disappears entirely. Ads are matched on the language they are written in.
Performance Max is split. On Search placements, campaign-level language settings stop applying and matching works the same way as standard Search. Advertiser-selected languages still guide delivery on YouTube, Display, Discover and Gmail. Shopping ads inside PMax were never governed by language settings and are unaffected.
Read this one carefully: the PMax language setting stays in the interface and still does work — just not for Search. One control, two behaviours, no visible distinction in the UI. Anyone auditing a PMax campaign in October and reading the language setting at face value will draw the wrong conclusion about Search delivery.
How Google Decides
Google already looks past interface language to work out what someone reads. On Search, the signals include the language of the query itself, user language settings and other preferences.
The practical consequence: someone with a browser set to Spanish who habitually searches in English can be served either. Where multiple eligible campaigns exist, Google says AI-based ad group prioritisation picks the candidate with the most relevant language.
That is the sentence to sit with. In a bilingual market, the thing that used to separate your campaigns was a checkbox. Now it is a model decision you cannot see, cannot override and cannot report on.
“The language setting was never a hard filter. But it was a lever you controlled. Removing it doesn’t make matching worse, it makes it unaccountable.” — 360 OM Editorial
Who This Actually Affects?
If you run a single-language account in a single market with language set to All, this is a non-event. Most well-structured accounts have run All Languages for years precisely because the setting keyed off user preferences rather than query language and was leaky in both directions.
The exposure sits in three places:
Bilingual and multilingual geographies. Canada, Belgium, Switzerland, and any brand splitting Spanish and Catalan or running multiple languages inside a single EU market. If your campaign separation was location plus language, you now have location only. Two campaigns targeting the same country with the same product intent are about to compete on Google’s read of language relevance rather than your structure.
Budget allocation by language. Where each language campaign carried its own budget, the split stops being deterministic. Spend will follow whichever campaign the auction and prioritisation logic favours. If those budgets mapped to regional P&Ls or local market owners, expect that conversation.
Brands serving English ads to non-English markets. Language targeting was a crude guard against English creative reaching users who don’t read it. That guard is gone. The ad and the landing page now carry the load.
Creative And Landing Pages Become The Targeting
Google’s own guidance points here: ads and destination pages should be clearly structured in their intended language. That is a reasonable ask and it is also the only lever left.
For eCommerce, the weak point is usually the destination, not the ad. Localised ad copy pointing at a partially translated PDP: checkout strings in English, size guides untranslated, review content in the source language. This was survivable when language targeting fenced the traffic. It is less survivable when the destination is part of how Google decides who sees the ad at all.
Pre-September Audit
Step 1:
Filter Search campaigns for any language setting other than All languages. That list is your exposure. Everything else is noise.
Step 2:
Find campaigns duplicated by language inside the same geography. Decide now whether to consolidate or to differentiate them properly on keywords, ad copy and landing page.
Step 3:
Check destination pages actually resolve in the intended language end to end, PDP, cart, checkout, and not just the template.
Step 4:
Audit scripts, bulk sheets and API integrations for language criteria on Search campaigns. These will error, not fail silently.
Step 5:
Baseline CTR and conversion rate by campaign in multilingual markets before late September. It is the only way you will detect a shift after the fact.
The API Change Is The One That Bites Developers
Google recommends dropping language criteria when creating or updating Search campaigns. Existing criteria can stay but will no longer affect targeting, and can be removed.
Attempts to add or update CampaignCriterion.language on Search campaigns will return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. Performance Max won’t throw the same error, because language still influences its non-Search channels.
Anyone running templated campaign builds, MCC-level scripts or a bulk creation layer should test against this before the change lands. A build sheet that has silently included a language criterion for five years is going to start failing at creation, not at delivery.
The Pattern
Read this alongside the AI Max auto-upgrade for Search and the August Smart Bidding changes. Three moves in short order, all in the same direction: a setting that was an advertiser decision becomes a model decision, and the interface stops showing you what happened.
None of them is individually unreasonable. Language targeting genuinely was imprecise. But the cumulative effect is an account where the levers that used to explain performance are being retired faster than the reporting that would replace them. There is no language dimension in Search reporting, so you will not see which language Google matched on, only the downstream effect on CTR and conversion rate, weeks later, mixed in with everything else.
The response is not to complain about it. It is to move the control into the assets you still own: keyword structure, ad copy, landing pages, feed and margin data. Those are the inputs Google still has to respect.
360 OM Verdict
Useful
For most single-market accounts, this removes a setting that was already doing very little. If you ran All Languages, nothing changes. Matching on ad language is arguably closer to intent than matching on a user’s interface preference.
Caution
Bilingual markets lose their separator. Canada, Belgium, Switzerland and multi-language EU setups had campaign structures built on location plus language. From late September that is location only, with prioritisation deciding the rest.
Caution
Scripts and API builds will error, not degrade. Anything setting CampaignCriterion.language on Search campaigns returns a hard error. Check bulk templates and automated build processes before the rollout.
Honest
The real cost is diagnostic, not immediate performance. No reporting dimension shows which language Google matched on. When multilingual performance moves, you will be inferring the cause rather than reading it.
Need a fresh perspective? Let’s talk.
At 360 OM, we specialise in helping businesses take their marketing efforts to the next level. Our team stays on top of industry trends, uses data-informed decisions to maximise your ROI, and provides full transparency through comprehensive reports.
.png)
