Google is removing campaign-level language targeting from Search and AI Max for Search campaigns in late September 2026, whether or not you touch your account. Google confirmed the timing to Search Engine Roundtable on August 14, 2026, and Search Engine Land reported the same window on August 13 — putting the change inside the next two weeks.
For most of the country this is a housekeeping item. For advertisers in Metro Detroit — where 54.5% of Dearborn residents reported Middle Eastern or North African ancestry in the 2020 Census and roughly 67% of Hamtramck adults speak a language other than English at home — it quietly rewrites how your ads get matched to the people you were trying to reach on purpose.
What is changing with Google Ads language targeting in September 2026?
The campaign-level language targeting setting is being removed from Search campaigns and from AI Max for Search campaigns. Google will decide which language ad to serve using the language of your ad creative plus its own signals about which languages a searcher understands.
Performance Max gets a split treatment. For ads on the Google Search Network, the campaign-level language setting stops applying and PMax behaves like a standard Search campaign. Your selected settings still govern YouTube, Display, Discover and Gmail. Shopping ads inside PMax were never affected and still aren’t.
There is an API dimension too. Google recommends developers stop setting language criteria on Search campaigns; attempts to add or update CampaignCriterion.language there will return a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error. Existing criteria can stay — they simply won’t apply — and PMax won’t throw the same error, because language still drives its non-Search channels.
Why does removing one setting matter more in Metro Detroit than in most markets?
Because the region has an unusually high concentration of households that search in a language other than English, and local advertisers built account structures around that fact. Roughly 190,000 Arabic speakers live in Metro Detroit — about 13% of all Arabic speakers nationally — and Arabic is Michigan’s third most-spoken language at home.
Think about who that describes: an immigration attorney in Dearborn running one Arabic campaign and one English campaign, a dental group in Sterling Heights fielding Chaldean and Albanian inquiries, an HVAC contractor covering Hamtramck and Warren with Bengali and Polish landing pages. Every one of those accounts used the campaign-level language setting as a fence. That fence is being removed, and the auction is being asked to rebuild it from ad text.
How does Google decide which language ad to serve now?
Google reads the language of your ad creative as the primary signal, cross-references it against signals about the languages the user understands, and — when multiple eligible ads exist — resolves the conflict with AI-driven ad group and asset group prioritization at auction time. Google Ads Liaison described that prioritization publicly on August 14, 2026.
The user-side signals are broader than interface language. Search Engine Land reported they include the language of the query itself, account language settings and other stated preferences — so someone with a Spanish browser who habitually searches in English is eligible for either.
Here is the mechanism that matters, because it lets you predict cases nobody wrote an article about. Language used to be a gate evaluated before the auction: if the campaign wasn’t targeting Arabic, the ad simply wasn’t eligible. Now language is a ranking input evaluated inside the auction, alongside everything else that determines Ad Rank. Gates are binary and predictable. Ranking inputs get outvoted.
Run that forward. An Arabic ad group and an English ad group both eligible on the same query no longer carry a structural guarantee that the Arabic ad wins for an Arabic-preferring searcher. If the Arabic ad group has thinner historical CTR — which it usually does, having less volume — the English ad can take the impression, earn a worse click-through rate from that user, feed that back into Quality Score, and raise your cost per click on the keyword you were winning cheaply. The account doesn’t break. It gets more expensive in a way that looks like seasonality.
Does Google Ads still support language exclusions?
No. Google explicitly confirmed that language targeting did not support exclusions before this change and still won’t after it. There is no way to tell Google “never serve my English ad to a Spanish-preferring searcher.”
That’s the part advertisers keep missing when they read the announcement as neutral. The old setting was coarse, but it was an instrument. Its replacement is not a different control — it’s the absence of one. Your only remaining levers are ad copy language and landing page language.
Is Google’s “no action is required” actually true?
It’s true about your account structure and misleading about your results. Google is telling you nothing will error out and no campaign will stop serving — a statement about continuity, not performance.
Google’s own guidance gives the game away: it says single-language campaign structures “will continue to function normally,” then in the same breath tells advertisers to make sure creatives and landing pages are clearly structured in the intended languages. Those two statements only coexist if the second is doing the work the removed setting used to do. If ad language is now load-bearing, accounts with sloppy ad language have a problem — and “no action required” describes the accounts that were already clean.
The advertisers most exposed wrote English ad copy pointing at a non-English landing page, or mixed both languages in one ad group because the campaign setting handled separation. That was a reasonable build last month and a liability in two weeks. If you inherited an account and aren’t sure which pattern you have, a structural audit is the fastest way to find out — the same review we run when we take over a Google Ads account in Metro Detroit.
What should a Michigan advertiser do before the setting disappears?
Seven steps, all of them doable this week by a team of three or fewer.
- Inventory every campaign with a non-English language setting. In the Google Ads UI, add the Languages column to your campaign view and sort. Write down which campaigns currently rely on that fence. This list is your risk register.
- Export a 90-day performance baseline per campaign — impressions, CTR, CPC, conversion rate, cost per conversion — and save it dated September 2026. Without a pre-change baseline you can’t prove whether the rollout moved your numbers.
- Audit ad-copy-to-landing-page language consistency at the ad group level. Every ad in a given ad group should be in one language, pointing at a page in that same language. Mixed ad groups are where the new matching logic gets confused.
- Check that non-English landing pages declare their language in markup. Set
<html lang="ar">,lang="es",lang="bn"orlang="pl"as appropriate. A page that claims English while displaying Arabic contradicts the exact system now making the call. - Split mixed-language ad groups into single-language ad groups before the rollout, not after, so performance data accrues to a clean structure the prioritization system can read unambiguously.
- Strip language criteria from API-managed Search campaigns. If campaigns are created programmatically, stop sending
CampaignCriterion.languageon Search campaigns now to avoid theContextError. Existing criteria can stay or be cleaned up. - Add a weekly search terms review through October. Non-English queries appearing in an English campaign — or the reverse — are the first visible symptom. Catching it in week one is a copy fix; catching it in week six is a rebuild.
What dates should be on the calendar?
- Late September 2026 — campaign-level language targeting removed from Search and AI Max for Search; PMax Search Network delivery switches to the same logic.
- September 1–30, 2026 — Google’s automatic migration window for Campaign-level Broad Match and ACA campaigns into AI Max, per Search Engine Land. If both changes touch one campaign, isolate the variables before attributing any swing.
- Week of September 29, 2026 — first clean post-rollout week. Compare against your saved baseline, not against last week.
- Mid-October 2026 — enough data to judge CTR and Quality Score movement on bilingual ad groups. Earlier reads are noise.
Frequently asked questions
Will my separate Spanish and English campaigns stop working?
No. Google confirmed that single-language campaign structures continue to function and no account restructuring is required. What changes is that the campaign setting no longer enforces the separation — your ad copy and landing page language do. If those are already clean and consistent, this structure is the one best positioned for the change.
Does this affect YouTube or Display campaigns?
Not directly. The removal applies to Search campaigns, AI Max for Search, and the Search Network portion of Performance Max. Language settings you select in a Performance Max campaign continue to apply to YouTube, Display, Discover and Gmail delivery. Shopping ads within Performance Max were never governed by language settings.
Can I exclude a language instead of targeting one?
No. Google stated that language targeting did not support exclusions before this change and will not after it. The practical workaround is writing ad copy and landing pages so unambiguously in one language that the matching system has no reason to serve them to speakers of another — which is a weaker guarantee than an exclusion, and worth planning around.
How will I know if the change hurt my account?
Watch CTR and search terms first, not conversions. A language mismatch shows up as irrelevant impressions and falling click-through well before it moves cost per acquisition. Compare the week of September 29 against your saved 90-day baseline, and segment by ad group rather than campaign so a healthy English ad group doesn’t mask a struggling non-English one.
The short version for Michigan advertisers
A setting most national advertisers will never notice losing is load-bearing in a metro where Dearborn, Hamtramck, Warren and southwest Detroit each search in a language the ad account may not assume. The work is small — audit ad group language consistency, fix your lang attributes, save a baseline — and the window is roughly ten days. If your account was built around the language fence and nobody has looked at it since, that’s worth a conversation before the rollout rather than after the October reports land.
Comments are closed