Google is removing campaign-level language targeting from Search and AI Max for Search campaigns starting in late September 2026, with the Search channel of Performance Max matching the same behaviour. As Search Engine Journal put it, Google is retiring language targeting in Search campaigns and will instead decide which ads to serve based on the language of your creative and landing page plus its own read of the languages each user understands. Google frames it as a no-action-required change, but for B2B SaaS accounts that used the setting as a qualification filter, the default behaviour is shifting underneath live campaigns.
The impact is uneven. If you run a single-language campaign in a single-language market, you will barely notice, because there was never a large pool of other-language users to exclude. The exposure sits with multilingual and multi-region accounts — English-only campaigns in the EU, LATAM, or APAC — where language targeting was doing quiet filtering work that now has to be rebuilt from creative language, landing-page language, and negative keywords. This guide covers what actually changes, who is exposed, and the concrete steps to keep unqualified traffic out of the funnel before the setting disappears.
What is actually changing
Today, the campaign-level language setting tells Google to serve your ads only to users it believes understand a chosen language. It is an explicit, advertiser-controlled filter: set a campaign to English, and Google withholds it from users it judges to be, say, Spanish-only. After late September 2026, that control is removed for Search and AI Max for Search. In Google’s replacement model, it relies on the language of the creative and landing page, together with existing signals about the languages a user knows, to decide who sees the ad. The lever moves from a setting you control to an inference Google makes.
One nuance matters for Performance Max. The campaign-level language setting is only removed for the Search channel inside PMax; for the other channels — YouTube, Display, Discover, and Gmail — the setting still applies. So a PMax campaign does not lose the control entirely, but its Search delivery starts behaving like a Search campaign with no language filter. PPC Land noted the change arrives nine months past its originally signalled deadline, so accounts that set language targeting long ago and forgot about it are exactly the ones most likely to be caught out.
Which B2B SaaS accounts are exposed
The accounts that need to act are the ones that used language targeting as a proxy for audience qualification. The classic case is a B2B SaaS company selling into multiple countries with a single English-language product and English-only ads, running campaigns across the EU, LATAM, or APAC. There, language targeting kept spend away from users Google judged unlikely to read English ads — a cheap, invisible filter that reduced wasted clicks. Remove it, and those campaigns can begin serving to a broader set of users, some of whom will click an English ad they cannot fully act on, or who were never in your qualified audience to begin with.
The accounts that can largely ignore this are single-market, single-language setups: a US SaaS selling to US buyers in English, or a German SaaS targeting Germany in German. With no meaningful other-language population to exclude, the setting was doing little, and its removal changes almost nothing. If you are unsure which bucket you fall into, the fast test is to open each campaign and check the language setting: campaigns set to anything other than “all languages” are the ones whose behaviour changes, and those are where you concentrate the audit. This is the same campaign-hygiene discipline behind location targeting for B2B SaaS, where a single mis-set control quietly leaks budget for months.
Creative and landing-page language become the filter
Because Google now leans on the language of your ad and landing page to decide who sees it, that language has to be unambiguous. Mixed-language assets — an English headline with a localised description, or a landing page that switches language partway down — muddy the signal Google uses to match your ad to the right users. The practical instruction is to make each campaign’s creative and destination consistently one language, so the system has a clean signal to work from. If you serve multiple languages, separate them into their own campaigns or ad groups with matching creative and landing pages rather than relying on a single campaign to sort users by language.
This raises the stakes on AI-generated assets. If you use automatically created assets or AI Max asset generation, the system can produce variants, and you now depend on those variants staying in your intended language to keep serving aligned with your audience. Review generated assets for off-language output and prune anything that drifts. The same care applies to your responsive search ad inputs — the discipline we cover in writing RSA ad copy for B2B SaaS now carries an extra job: the language of every asset is also a targeting signal, not just a message.
Rebuilding the filter with negative keywords
Where language targeting was blocking other-language search queries, negative keywords are the replacement lever. If your English campaigns were quietly excluded from Spanish or Portuguese queries by the language setting, you may start to see those terms in your search terms report once the setting is gone. Mining that report and adding other-language query terms as negatives is the most direct way to reinstate the filter you are losing. This is reactive by nature — you catch the leak in the search terms report and plug it — so the cadence of review matters more than it did when the setting handled it automatically.
Build the negative list the same way you would for any spend-control problem: start from the actual queries triggering your ads, group the other-language and out-of-intent terms, and add them at the campaign or account level. Our guide to negative keywords in Google Ads covers the mechanics, and the principle holds here: the search terms report is the source of truth for what to exclude. The difference now is urgency — with language targeting removed, this report is no longer a nice-to-have cleanup task but the primary place you will spot and stop unqualified, other-language traffic.
Why this compounds with the AI Max migration
The timing is not incidental. Google is simultaneously moving accounts toward AI Max for Search, auto-upgrading campaign-level broad match and automatically created assets, a shift we cover in detail in our guide to the AI Max broad match auto-flip. AI Max already broadens matching and can generate its own assets, which widens the set of queries and users your ads reach. Removing language targeting takes away one more guardrail on that reach, so the two changes compound: broader matching with fewer manual filters.
In an AI Max world, the language of your creative and landing page is not a formatting detail — it is one of the few remaining signals that keeps serving aligned with your intended audience. If you are being migrated this autumn, treat language integrity, asset review, and negative keywords as a single hardening pass rather than separate chores. The same logic applies to accounts still planning their move; our walkthrough on migrating Dynamic Search Ads to AI Max pairs naturally with this audit, because both are about replacing manual controls with clean signals the automation can read.
A pre-deadline action plan
The work is concrete and bounded. First, audit every campaign with a language setting other than “all languages” and flag the multilingual and multi-region ones as your priority. Second, confirm that each of those campaigns has creative and landing pages unambiguously in the intended language, splitting languages into separate campaigns where needed so Google gets a clean signal. Third, pre-load negative keywords for the other-language terms you expect to surface, and schedule a tighter search-terms review for the weeks after the change so you catch leaks early.
Fourth, if you run AI-generated or automatically created assets, add an off-language check to your review. And fifth, monitor the geography and search terms reports for a post-change rise in out-of-market or other-language traffic, treating any spend leak as a prompt to reinforce the creative and negative-keyword layers rather than to look for a setting that no longer exists. Handled this way, the removal is a manageable hygiene project. Ignored, it is the kind of quiet budget leak that only shows up when someone finally reads the search terms report — the same failure mode behind broader audience targeting for B2B SaaS, where the traffic you never chose to pay for is the traffic that erodes your CAC.