Google Ads Language Targeting Change: Your September Audit

Late this month, Google Ads is retiring campaign-level language targeting on Search, AI Max for Search, and the Search inventory inside Performance Max. If you run any of those campaign types, especially in a multilingual account, the google ads language targeting change hands the language-matching decision to Google’s AI ad group prioritization.

Google says no action is required. That is technically true. It is also the kind of “no action required” statement that hides real work for anyone running paid search at scale. Your account will not break. Your reports will not glitch. But your language delivery will shift under the hood, and the accounts that get ahead of it now will not spend October wondering why their Spanish landing pages are showing to English searchers.

This is the operator plan. What is actually changing, what is not, and the six audit steps you should complete before the rollout finishes.

What the google ads language targeting change actually does

Starting late September 2026, the campaign-level language setting disappears from Search and AI Max for Search campaigns. Google’s automated systems match ads to searches using the language of your ad creative, the language of your landing page, and existing user language signals. When multiple eligible campaigns or ad groups match a query, AI-based ad group prioritization picks the language it thinks is most relevant for that user.

Performance Max is more nuanced. The campaign-level language setting no longer applies to Search inventory inside Performance Max, but it still applies to YouTube, Display, Discover, and Gmail. Shopping ads inside Performance Max are not affected by the setting either way. So your PMax campaigns keep the setting in place, and it keeps working, just not for the Search slot.

On the API side, any attempt to add or update `CampaignCriterion.language` on a Search campaign returns `ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT`, per the Google Ads Developer Blog announcement from August 13, 2026. Performance Max mutates do not error, because the criterion is still valid for other channels. Existing language criteria stay in the object model but stop affecting Search delivery.

What Google is not doing with this change

Google is not translating your ads. If you have Spanish creative and English creative in the same account, the system routes each search to the version whose language matches best. It does not generate a new French ad because Google detected a French searcher.

Google is not adding new reporting either. There is no new language-level segmentation on the search terms report or the auction insights report. If you want to know how the automated matching is splitting your traffic across your language versions, the answer is the campaign, ad group, and asset-level performance data you already had.

Ginny Marvin, ads product liaison at Google, characterized the shift in an August roundtable summarized by Search Engine Journal: the way things are behaving now are not changing. The point of the update, according to Google, is simplification. Most advertisers should see no measurable performance change. For English-only accounts, this is close to a non-event. For anyone splitting a Search account by language, the six audit steps below matter more.

Why the google ads language targeting change matters for multilingual accounts

If your account uses one Search campaign per language, that structure still works. Google explicitly says you do not need to restructure. What changes is the enforcement mechanism. Yesterday, you could tell Google “this campaign serves Spanish, period” and the setting acted as a hard filter. Tomorrow, that filter is gone, and the language of your creative and landing page is doing the routing work.

That matters for three reasons. First, a Spanish campaign whose ads or landing pages are not clearly written in Spanish is now leaking signal. The automated system reads the creative and the page. Any mixed-language copy, boilerplate English footers, or English CTAs on a Spanish landing page gets factored into the language decision. If your Spanish page has an English navigation bar and a translated hero block, you probably need to tighten that up.

Second, cross-language matching becomes more common by default. Someone who searches in English on a browser configured in Spanish could receive an ad in either language, and the AI decides. If you have a hard business reason to serve one language regardless of the search language, you no longer have a campaign switch to enforce it. Your only real control is which ad and landing page you show, and whether both exist in the language you care about.

Third, any bulk-management script, connector, or bid management tool that mutates language criteria on Search campaigns is going to start throwing errors as soon as the rollout completes. That is the API error path, not a logical error path, so it will fail the API call, not silently ignore it. Anything running on the older API versions that ignores the field silently is worse: your dashboards will still show a language restriction that is no longer being enforced. Either way, the fix is the same: stop sending the criterion for Search campaigns.

The six-step google ads language targeting change audit

Block 45 minutes on your calendar for each multilingual account. English-only accounts can skip most of this.

Step one: list every Search and AI Max for Search campaign in the account that has a non-default language setting today. Also list every Performance Max campaign where a language other than “all languages” is configured. That is your exposure list. Everything not on the list is largely a non-event.

Step two: check that ad copy and landing pages exist in each language your account structure implies. The automated system routes searches to the language version you actually created. It does not generate a French landing page for you. If a “French” campaign is pointing to an English landing page today, that mismatch will get harder to hide once the campaign-level setting is gone.

Step three: audit landing page and creative hygiene. Every ad and landing page should be unambiguously written in the language it is meant to serve. Mixed-language navigation, English CTAs on non-English pages, or boilerplate footers in the wrong language are the kind of noise the system will pick up on. Same principle you already apply to real-time policy reviews, applied to language.

Step four: audit any script, bulk upload template, or third-party bid tool that references language criteria at the API level. On current API versions, those calls will start returning errors on Search campaign creation or update. On older API versions that some agency tools still use, the calls will not error but the field will be ignored, which can create a silent gap between what your dashboard shows and what the live campaign is actually doing. Update any tool that references `CampaignCriterion.language` on Search campaigns to stop sending it.

Step five: after the rollout completes, pull two weeks of performance data and look for shifts in language-mismatched traffic. A Spanish campaign whose landing page conversion rate changes materially, a bilingual campaign whose ad group split changes materially, or a French campaign that suddenly starts serving on more or fewer queries, are all signals that the automated matching is reshaping delivery. That is the point of the change. Watching for it early is how you catch a bad shift before it burns two months of spend.

Step six: for API-managed accounts, stop submitting language criteria on any new or updated Search campaign going forward. This is the direct guidance from Google’s team. Bake it into your campaign creation templates now, so nothing new goes into production still carrying the deprecated field.

How the google ads language targeting change fits your September operating cadence

September has stacked up. The local services ads migration is issuing 14-day countdown emails. The Shopping policies consolidation lands this month. The local inventory ads default is a week old. The AI Max for Shopping retail rollout is still working through accounts. Layer the language change on top and September starts looking like a full account review month, not a normal service month.

Group the audits. Every multilingual account gets one calendar block: language-setting exposure list, creative and landing page hygiene, API script audit, PMax Search-inventory check, and a September operating review. The experimentation tools playbook gives you the testing framework if you want to validate a specific creative variant before or after the rollout. Anything that touches Search language, PMax Search inventory, or bulk-management scripts should be reviewed and closed out in the same session.

The playbook is the same one you would use for any other September deadline. Batch the overlap. Give each client one clean update note at the end of the month covering everything you audited, not five separate emails. That is the difference between an agency that scales through a busy Google month and one that spends October catching up on what changed while it was busy.

If you want a template for the client-facing note that goes out after the language rollout completes, or you want help auditing a multilingual account before the change lands, book a free consultation and we will walk through it with you. Let’s Grow!