Google Ads Removes Language Targeting from Search Campaigns in September

Starting in late September, Google will remove campaign-level language targeting from Search and AI Max for Search campaigns. Advertisers will no longer pick which languages their Search ads target. Instead, Google's automated systems will match ads to users based on the language of the ad itself and signals about what languages the user understands. The change also partially affects Performance Max, where language settings will stop influencing Search ad delivery but continue to guide YouTube, Display, Discover, and Gmail placements.

What happened

Detail	Fact
Rollout date	Late September (year unspecified by Google)
Campaigns affected	Search, AI Max for Search, Performance Max (Search placements only)
Campaigns NOT fully affected	Performance Max non-Search channels, Shopping ads within PMax
Action required by advertisers	None for existing campaigns (per Google)
API error if you still send language criteria	ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT

Google is removing the campaign-level language targeting setting from Search and AI Max for Search campaigns. The setting will simply disappear from those campaign types. Language matching will then happen automatically, driven primarily by the language your ads are written in and signals Google collects about each user.

Those signals already go beyond a browser’s interface language. Google considers the language of the search query itself, user language preferences, and other behavioural signals. A user with a Spanish browser who searches regularly in English could receive ads in either language, depending on which campaign Google judges most relevant.

How does Performance Max language targeting change?

Performance Max gets a split treatment. For ads that appear on Google Search through a PMax campaign, language settings will stop applying and matching will work the same way as standard Search campaigns. But language targeting is not gone from PMax entirely:

• YouTube, Display, Discover, and Gmail placements will still respect advertiser-selected language settings.
• Shopping ads within Performance Max are not affected by language settings at all.

So if you run multilingual PMax campaigns, your non-Search channels should continue behaving as they do today. Watch the Search portion closely after September.

What about the Google Ads API?

Developers managing campaigns through the API need to stop adding or updating CampaignCriterion.language for Search campaigns before the change takes effect. Attempting to do so after rollout will return a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error. Existing language criteria can stay in place without causing problems, but they will have no effect on targeting and can be cleaned up at your discretion. Performance Max will not throw the same error because language settings still function on its non-Search channels.

Why it matters

This is Google handing off another manual control to its own automated systems. The practical risk is predictability. When you could select a target language explicitly, you had a clear lever for separating campaigns by audience. Now the matching logic is inside Google’s black box, informed by ad language and inferred user signals.

For businesses running single-language campaigns, the day-to-day impact may be small. For multilingual advertisers running separate campaigns per language, the risk is higher. Google’s AI-based ad group prioritization will decide which language variant is most relevant for a given user, and that decision is harder to audit or override. Our performance advertising work has shown repeatedly that automated targeting changes tend to be smooth for simple structures and messy for complex ones.

The ad creative and landing page language now carry more targeting weight than they did before. If those are inconsistent or mixed, expect noisy delivery.

Our take

Google frames this as a simplification. It is also a reduction in advertiser control, which is a pattern worth tracking across the platform. The stated reason, that Google already uses more than interface language to understand what users want to read, is fair. The browser language heuristic was always a blunt instrument.

That said, handing the decision entirely to Google’s signals removes a clear audit trail. If a multilingual campaign starts cannibalising itself, you now have fewer levers to diagnose or fix it. The honest advice: treat your ad copy and landing pages as the new de facto targeting setting. Clean, single-language ads pointing to single-language pages will behave more predictably than mixed creative.

This is also a reminder to keep campaign structures as simple as the business allows. The more segmented your multilingual setup, the more Google’s prioritization algorithm becomes a variable you cannot control. We cover similar automation shifts regularly in our AI and platform news coverage.

What to do about it

1. Audit every Search and AI Max for Search campaign that currently has language targeting set. Note what languages are selected and what audiences those campaigns serve.
2. Review your ad copy and confirm each ad is written in a single, clear language. Avoid mixing languages within the same ad.
3. Check landing pages linked from each ad. Make sure the page language matches the ad language, since Google will now use this as a primary signal.
4. If you use the Google Ads API, update your campaign creation and editing scripts to remove any CampaignCriterion.language calls for Search campaign types before late September.
5. Set up performance monitoring segments (by language or by campaign) so you can detect delivery shifts after the rollout date.
6. For Performance Max, confirm which channels your campaigns serve and decide whether any language settings on non-Search channels need adjustment before the change.

The practical takeaway: treat your ad and landing page language as your targeting tool from September onward, because that is exactly what Google will treat it as.

Source: Search Engine Land