Google confirmed on August 14, 2026 that it is removing campaign-level language targeting from Search campaigns and AI Max for Search campaigns. Ginny Marvin, Google's Ads Product Liaison, announced the change in a LinkedIn post. The rollout begins in late September 2026. This is the third time Google has put a date on this change - it was originally scheduled for the end of 2025, then delayed, then delayed again, and this time the company is moving forward.
The core change is simple to state and harder to plan around: the manual language targeting setting disappears from campaign settings. In its place, Google's system decides which ads to show based on signals it already collects - the language of your ad creative, the language of your landing page, the language of the search query itself, and existing signals about what language the user understands, such as browser and account language settings. There is no toggle to turn this behavior off.
What Exactly Disappears From Campaign Settings
Today, advertisers running Search campaigns can pick one or more languages under campaign settings, and Google only shows ads to users whose language settings match that selection. After the late September 2026 rollout, that setting is gone for Search campaigns and for AI Max for Search campaigns specifically. Google's automated matching takes over completely for those two campaign types.
The replacement mechanism leans on creative and landing page language rather than an explicit setting. Google's system favors showing the ad and landing page combination whose language matches the language of the search query itself. If your ad copy is written in one language and your landing page is in another, or if a single campaign mixes ad groups in different languages without clean separation, the system has to guess which asset best matches the query - and guesses are where mismatches happen.
Announced and Delayed Twice Before - Why This Time Is Different
Google first signaled this change for the end of 2025. It slipped once, then slipped again, which led some advertisers to treat the removal as a low-priority item that would keep getting pushed back. The August 14, 2026 announcement sets a concrete late September 2026 rollout window, and nothing in Google's messaging this time suggests a further delay is likely.
The practical lesson from two prior delays is not that this will slip a third time - it is that advertisers who waited on the first two announcements now have a genuinely tight window before the setting is gone. Anyone still relying on the manual language targeting control to segment audiences should treat late September 2026 as a hard deadline, not a tentative one.
The Performance Max Nuance Most Coverage Is Skipping
Performance Max campaigns follow a different rule than plain Search campaigns, and this distinction matters if your account runs both. Inside Performance Max, language settings no longer apply to the Google Search results shown through that campaign type - the same automated creative and landing page matching described above takes over there too. However, language settings continue to guide delivery across YouTube, Display, Discover, and Gmail placements within Performance Max. Shopping ads served through Performance Max are unaffected entirely, since Shopping never used language targeting the same way text ads did.
That split means a single Performance Max campaign can have language settings that still do something (non-Search placements) sitting alongside a search surface where the setting no longer has any effect. Advertisers auditing their accounts need to check each placement type separately rather than assuming one uniform behavior across the whole campaign.
Language Exclusions Remain Unsupported
One gap does not change with this update: Google Ads has never let advertisers exclude a specific language from targeting, and that limitation continues after the removal. If you were hoping the new signal-matching system would finally let you block ads from showing to, say, users with a specific browser language setting, it will not. The system can favor a language match; it still cannot enforce a language exclusion.
The Google Ads API Will Start Rejecting Language Targeting Calls
Advertisers or agencies managing language targeting programmatically through the Google Ads API need to treat this as a code change, not just an account settings change. Starting with the late September 2026 rollout, API calls that attempt to set or read language criteria for Search campaigns will return an error instead of succeeding. Any script, bulk upload process, or internal tool that touches language targeting for Search campaigns needs that logic removed before the rollout, or it will start failing in production.
This is easy to miss if the only people reviewing the announcement are on the media buying side rather than the technical side of an account. Agencies running client accounts through API-based management tools should flag this internally now, since a failing API call discovered after the rollout is a worse position than removing the dead code proactively.
Who Actually Needs to Do Something
Advertisers who already structure campaigns by language - one campaign for English creative, a separate campaign for Spanish creative, and so on - do not need to restructure anything. Google will keep using the language of your creative and landing page as the matching signal, and a campaign built entirely around one language's ad copy and landing pages naturally continues to serve to users searching in that language. This is the least disruptive path through the change, and it is already how a large share of multilingual advertisers operate.
The real exposure sits with accounts that used the language targeting setting itself - rather than campaign structure - to control which language audience saw which ads, often inside a single mixed-language campaign. Once the setting disappears, those accounts lose the direct lever they were using, and Google's AI-driven signal matching takes over instead. If ad copy or landing page language inside that campaign is inconsistent, mismatches between the language a user searched in and the language of the ad they see become more likely.
A Pre-Rollout Checklist
- Identify every active Search and AI Max for Search campaign that currently uses campaign-level language targeting, not just the ones you remember configuring manually.
- For each one, check whether the campaign structure already separates ad groups and landing pages cleanly by language, or whether multiple languages are mixed inside a single campaign.
- Where languages are mixed inside one campaign, plan whether to split it into language-specific campaigns before late September 2026, since that restores the kind of control the removed setting used to provide.
- Audit ad copy and landing page language consistency for every campaign in scope - inconsistent language between creative and destination page is the single biggest source of new mismatches after this change.
- Search your codebase, scripts, and any third-party tools for Google Ads API calls that read or write language criteria for Search campaigns, and remove that logic before the rollout window opens.
- Confirm your Performance Max campaigns separately for Search placements versus YouTube, Display, Discover, and Gmail placements, since the rule differs by placement type within the same campaign.
Part of a Broader Pattern in Google Ads
This removal is not an isolated decision. It follows the same direction as the AI Max auto-upgrade that converts eligible Search campaigns automatically, and the ongoing move of Dynamic Search Ads toward AI Max. In each case, Google replaces a manual setting advertisers used to configure directly with automated signal matching the advertiser cannot fully control. The AI Max auto-upgrade rollout is worth reviewing alongside this change, since both affect how much manual control remains over Search campaign delivery through the rest of 2026, and both increase the importance of tight negative keyword and brand exclusion management as automated matching takes on more of the targeting decision.
Treat this as a trend rather than a one-time settings change. Advertisers who build a habit of reviewing which manual controls still exist in their account, on a recurring basis, will be far less exposed the next time Google narrows the gap between manually configured campaigns and its AI-managed default.
FAQ
When exactly does language targeting removal take effect?
The rollout starts in late September 2026, for Search campaigns and AI Max for Search campaigns specifically. Google has announced or delayed this change twice before, originally targeting the end of 2025, but the August 14, 2026 announcement sets a concrete window without signaling a further delay.
Do I need to restructure my campaigns before the rollout?
Only if you currently rely on the language targeting setting itself, inside a single campaign that mixes multiple languages, to control which audience sees which ads. Advertisers who already run separate campaigns per language do not need to change anything, since Google will keep using creative and landing page language as the matching signal.
Does this affect Performance Max the same way as Search campaigns?
No. Inside Performance Max, language settings stop applying to the Google Search results shown through that campaign type, but continue guiding delivery on YouTube, Display, Discover, and Gmail. Shopping ads within Performance Max are not affected by this change at all.
What happens to Google Ads API calls that manage language targeting?
Starting with the rollout, API calls attempting to set or read language criteria for Search campaigns will return an error. Any script or tool using that functionality needs the relevant code removed before late September 2026 to avoid failures in production.