Google is removing a setting that account managers have relied on for years. From late September 2026, the “campaign language” setting disappears from Search campaigns. Before you panic and restructure everything, one clarification matters: this is not a removal, it is a shift to autopilot. Google is not dropping language matching, it is simply taking the manual control away from you.
Here is what changes in practice, what stays the same, and above all how to keep control of your multilingual accounts.
What Google is changing, and when
From late September 2026, the language targeting setting at campaign level is removed for:
In practice, you will no longer select a target language for these campaigns. Your Search ads will be matched automatically based on the language they are written in, rather than on a setting you defined manually.
Good news: not everything goes away. The language setting stays in place for:
- video and Shopping campaigns,
- the other Performance Max channels, namely YouTube, the Display Network, Discover and Gmail.
For Performance Max, the nuance matters: the Search portion moves to the new automated logic, but the language settings you choose still apply to the other channels. Shopping ads within PMax have never depended on this setting and follow their own feed and market logic.
Google states it plainly: no action is required on your part for this change. If you manage an account through the API or scripts, however, one technical point deserves attention. From the switch onward, any attempt to add or edit the language criterion on a Search campaign will return an error. Make sure to remove these criteria from your automations and third-party integrations to avoid deployments that break.
Before and after: how language targeting used to work
The best way to grasp the impact is to compare the two logics.
A filter locked at campaign level
You chose one language per campaign. If the query was detected in another language, your campaign could not trigger, even when the user understood the language perfectly.
Google decides, query by query
The filter disappears. Google picks the ad to serve based on the language of your creatives, your landing pages and the signals specific to each user, with AI-driven prioritization at the ad group level.
When several of your campaigns are eligible for the same query, it is the AI prioritization at ad group level that selects the language deemed most relevant for that user.
A concrete example
A Belgian user, bilingual FR / EN, types their search in English. The advertiser has two campaigns: one French, one English.
The FR campaign is locked to "language: French". It cannot trigger on an English query.
Google can serve the French ad if it judges it the best match for this user, despite an English query.
So you lose yesterday’s mechanical certainty, but you gain theoretically finer delivery, based on each user’s actual profile rather than the language of their query alone.
What does not change (and why you don't have to redo everything)
The most important message often gets lost in other analyses: you have no restructuring to plan.
✅ The “one campaign per language” structure remains perfectly valid. Google says no overhaul is needed.
✅ You keep your FR, EN and other campaigns separate, with their own ads and translated landing pages.
✅ Geographic targeting is not affected. It remains your lever to steer countries and markets.
In other words, the backbone of your account does not move. What changes is the dial: control shifts from a manual setting to the quality of the signals you send the algorithm.
The real point of caution: regulated sectors
This is the least discussed topic, and yet it is where the change can sting.
In sectors such as insurance, finance or healthcare, the language in which information is communicated can carry contractual or legal weight. By removing the manual setting, Google makes it harder to prove and document the language actually served to a given user. And for now, no dedicated “by language” reporting comes with this change.
If this concerns you, a few habits help limit the fog:
- Use the search terms report: the language of queries remains a good indicator of what triggers your ads;
- Segment your conversion tracking by landing page URL (/fr/, /en/, /es/) to reconstruct the language served on the traffic side;
- Document internally the alignment between each ad and its page, to keep a record in case of an audit.
Worth watching in the coming weeks: Google could update its reporting on this point. Check the current state of play when the topic becomes sensitive for your campaigns.
To follow developments and check the latest official details, refer directly to Google support.Our recommendations
The change rewards clarity. The cleaner your signals, the better the algorithm will serve you where your language is actually understood. Here are the habits to adopt.
Monolingual ad groups
One language per group: keywords, ads and extensions aligned. It is the strongest signal you can send the algorithm.
Ad and page alignment
French ad, French page, from the H1 on. No redirect that changes the language without warning the user.
Clean technical signals
A correct lang attribute, no mixed languages on a single URL, and hreflang tags for your variants.
Tracking by language and market
Dashboards by language URL and by market to spot any delivery drift quickly, without flying blind.
API and script cleanup
Remove language criteria from your Search campaigns to avoid errors, and update your internal documentation.
FAQ
No. Google says no overhaul is needed. However, stricter segmentation by language at the ad group and landing page level is strongly recommended.
You lose the "language" box at the Search campaign level, but you keep three powerful levers: the language of your creatives, the consistency of your landing pages and geographic targeting.
No. Shopping keeps its own logic, as do the YouTube, Display, Discover and Gmail channels within Performance Max.
They simply stop influencing Search delivery. You can remove them to avoid confusion, and you must stop adding them via the API to avoid errors.
