Google Ads removes campaign-level language targeting
Released on , Google confirmed that from late September the campaign-level language targeting setting will be removed from Search and AI Max for Search campaigns, with matching switching to the language of the ads themselves. Read the Google Ads Developer Blog announcement here.
Language targeting has been a standard part of Google Ads campaign setup for well over a decade. It sat alongside location targeting in the settings panel, it appeared on every build checklist, and for most accounts it was set once and never revisited. From late September 2026 it stops being a control that advertisers hold for Search campaigns, and becomes something Google infers from the creative.
The announcement arrived on the Google Ads Developer Blog, which is where it is likely to be missed. The framing is technical and the audience is people writing code against the API, but the substance is a targeting control disappearing from the interface. Anyone managing Search campaigns has a change to absorb here, whether or not they have ever touched the API.
How it works
Two things happen in late September. For Search and AI Max for Search campaigns, the campaign-level language setting is removed outright. Google will match ads based on the language of the ads themselves, read alongside the user's own language preferences. For Performance Max campaigns the setting survives, but its scope narrows: on Google Search it stops being used and matching behaves as it does for Search campaigns, while on YouTube, Display, Discover and Gmail the campaign-level setting continues to guide who sees your ads.
That Performance Max split is the part most likely to be misread. The control does not vanish from those campaigns, so an advertiser glancing at the settings panel will see something that looks unchanged while its influence has been quietly halved. Google's guidance also notes that where an account holds several eligible campaigns, AI-based ad group prioritisation will select the most relevant ad language, which means the resolution happens inside Google's systems rather than through anything the advertiser configures.
Underneath, the language targeting criterion does not disappear from the data model. Google says existing language criteria will still be returned when querying, even though they no longer drive targeting. What changes is that attempts to add or update a language criterion on a Search campaign will be rejected. For Performance Max no error is raised, precisely because the setting still does a job on the other channels. In plain terms: the old settings stay visible as historical records, they simply stop meaning anything for Search.
Examples and use cases
Consider a UK retailer running a single English-language Search campaign to a UK audience. The language setting said English, the ads are in English, and the landing pages are in English. Nothing about this change should alter who sees those ads, because the old setting and the new signal already agreed. This describes the majority of UK accounts, and for them the change is genuinely administrative.
Now consider a UK business that used language as a quiet audience filter. A firm advertising to Polish-speaking or Portuguese-speaking communities in the UK may have run English-language ads while setting the campaign language deliberately, or run translated ads with a matching setting. Under the new model, the ad copy is doing all the work. A campaign with translated ad copy will continue to reach the intended audience, but a campaign that leaned on the setting while running generic English creative loses the mechanism it was relying on.
The third case is the UK agency or advertiser running one campaign across several European markets. Language targeting was frequently used to keep a single campaign tidy across borders, pairing broad location targeting with a narrow language setting. From late September that pairing no longer holds for Search, and the campaign's reach is defined by location targeting plus whatever language the ads are written in. Where a campaign carries ads in more than one language, Google's ad group prioritisation decides which is served, and the advertiser's lever becomes the structure of the account rather than a setting.
What this means for UK advertisers
For most UK accounts the honest answer is that very little changes, and it is worth saying that plainly rather than manufacturing urgency. Single-language accounts serving a domestic audience were already aligned. The change removes a setting that was doing no independent work for them, and the campaigns carry on. The campaign-level change worth diarising instead is the Dynamic Search Ads upgrade, which Google moved out to February 2027, and which does change how those campaigns are built.
The work sits in three narrower places. First, ad copy quality becomes a targeting input rather than purely a creative concern, which raises the cost of sloppy or mixed-language creative in a way it was not raised before. Second, any build template, standard operating procedure or script that sets campaign language on new Search campaigns needs updating, because from late September that instruction will be rejected rather than ignored. Third, multilingual accounts need to check whether the language setting was doing structural work that the ads themselves do not replicate.
For agencies, this belongs in the same category as any other silent platform change: it needs a scheduled check rather than a reaction. We fold changes like this into the routine review cycle on the accounts we run through our Google Ads management work, on the principle that a targeting control leaving the platform deserves a deliberate look at the accounts most exposed to it, and a shrug for the ones that are not.
Practical considerations
The main caveat is that Google has given a month rather than a date. "Late September 2026" is not a deadline you can put in a calendar with confidence, and progressive rollouts mean two accounts in the same manager account may change on different days. That argues for checking twice, once in early October and once a fortnight later, rather than assuming a single clean switchover. There is also no error, warning or notification for advertisers who work only in the interface. The setting will simply stop being there.
The second caveat is measurement. If a campaign was relying on language targeting to hold back reach, the symptom after the change will be a rise in impressions alongside search terms you do not recognise, not an alert. That is a pattern worth understanding in the context of how the auction decides which ads to show in the first place, which we covered in our guide to how pay-per-click advertising actually works. Segment by language where your reports allow it, take a baseline before the end of September, and compare. Finally, resist the temptation to strip language criteria out of existing campaigns as a precaution. Google has said explicitly that leaving them in place causes no disruption, and a bulk edit across a large account carries more risk than the tidiness is worth.
FAQ
When exactly does the language targeting change take effect?
Google has said late September 2026 without naming a single switchover date. On past form these changes roll out progressively rather than flipping every account at once, so two accounts under the same manager account may see the setting disappear on different days. Treat late September as the point by which the setting should no longer be part of your build process, not as a deadline you need to act on at the last minute.
Do I need to remove the language settings from my existing campaigns?
No. Google is explicit that existing Search and AI Max for Search campaigns keep running without disruption, because the language settings simply stop applying. Removing them is optional housekeeping. The one thing worth doing is updating any build checklist, template or script that sets language on a new Search campaign, since that is where the change will actually bite.
What replaces the setting for deciding who sees my ads?
The language of the ads themselves, read alongside the user's own language preferences. Google also points to landing page language as a supporting signal, which is why the guidance asks advertisers to make sure creatives and landing pages are clearly structured in the intended language. Where an account holds several eligible campaigns, Google says AI-based ad group prioritisation picks the most relevant ad language.
Does this affect Performance Max campaigns as well?
Partly, and the split is the detail most likely to be missed. On Google Search, Performance Max stops using the campaign-level language setting and behaves like a Search campaign. On YouTube, Display, Discover and Gmail, that same setting continues to guide who sees your ads. So the control stays in the interface for Performance Max, it just governs less than it used to.
Will this change who my ads reach in the UK?
For a single-language UK account running English ads to a UK audience, the practical effect should be close to nothing, because the ad language and the old setting already agreed. The accounts worth watching are those that used language as a de facto audience filter, for example targeting a specific language community within the UK, or UK advertisers running one campaign across several European markets.
How would I spot a problem after the change lands?
Segment by language where the report allows it, and watch impressions and search terms in the fortnight either side of the rollout. A campaign that was quietly relying on the language setting to hold back reach will tend to show it as a rise in impressions paired with unfamiliar queries, rather than as an error message. Nothing about this change produces a warning in the interface, so a scheduled look is the only reliable way to catch it.
