Google is pulling the campaign-level language targeting control out of Search campaigns and out of the Search inventory inside Performance Max, according to a report from Search Engine Journal. The setting currently lets an advertiser declare which languages an ad is allowed to serve in. Once it disappears, that decision routes entirely through automated signals Google already collects, and it becomes the latest manual lever advertisers lose as the platform pushes control toward its own systems.
The mechanics matter here. Today, Google checks two things before serving a Search ad: the language an advertiser selected at the campaign level, and Google’s own read on what languages a searcher understands. That read comes from query language, account settings and other signals its AI derives. Google also confirms whether the searcher can read the language used in that specific ad and its landing page. Starting late September, the campaign-level setting disappears for standalone Search campaigns and for AI Max, Google’s automated Search format. What remains is the ad copy and the page it points to, read together with whatever Google has already inferred about the person searching.
Performance Max splits by channel. Search Engine Journal reports that Performance Max’s Google Search inventory will follow the same rule as standalone Search campaigns, dropping the campaign setting entirely. Other Performance Max channels keep using it.
When a searcher qualifies for more than one language, a person equally fluent in English and Spanish, say, Google’s ad group prioritization system picks the stronger match. Where the query itself points clearly at one language, the matching creative and page get served, assuming they exist. Brand searches complicate that logic. An identical brand name across languages gives the query little to work with, so Google says it falls back on other signals and favors the searcher’s preferred language instead.
Google frames the removal as a fix for campaigns that unintentionally choke off eligible traffic: cases where a language setting blocks a user Google believes actually understands the ad. Teams that manage campaigns through Google’s Ads API should drop language criteria when submitting new or updated Search campaigns. Existing criteria will stay in the account but stop influencing delivery. Accounts already split by language, English and Spanish in separate campaigns, for instance, can keep that structure.
Two open threads surfaced when Search Engine Journal’s Brooke Osmundson raised nuanced use cases during a Google advertiser roundtable held ahead of the announcement. Regulated advertisers, an insurance advertiser was the example Google used, asked how they would document equitable delivery across language groups once Google, not a campaign setting, decides who sees which language. Google said running ads in both languages signals intent to reach both audiences. It did not announce any new reporting that breaks out which languages served or how performance differed between them. That gap stays open, and it is the detail worth tracking, since compliance and internal documentation needs do not disappear just because the control does.
The second thread involves AI Max. Advertisers asked whether a Quebec campaign’s AI-generated French creative could serve against an English-language query. Google confirmed it can. The ad creative generates first, and only afterward does Google’s comprehension check decide whether the searcher understands the resulting ad, regardless of the query’s own language.
Google told the roundtable that current language-matching behavior itself is not changing, only the control surface is. As Google put it, “the way things are behaving now aren’t changing.” That claim is testable once the rollout lands, and the evidence will be traffic composition, not Google’s assurance.
For multilingual advertisers, the task before late September is straightforward: audit every ad group to confirm the actual language of the ad copy and landing page matches the intended audience. Creative language, not a dropdown setting, becomes the sole language signal Google reads once the change lands.
Search Engine Journal, reported by Brooke Osmundson on August 13, 2026.
