The Language Target Removal: Why Google Is Dropping Campaign-Level Language Rules for Search

What changes in late September 2026?

Google is removing the campaign-level language targeting setting from Search and AI Max for Search campaigns. According to the official August 13 announcement, Search ads will match based on the language of the ads rather than a manual language criterion attached to the campaign.

The same logic will apply to the Search portion of Performance Max. The campaign's selected languages will continue guiding delivery on YouTube, Display, Discover and Gmail. Google's updated language-targeting documentation also says Shopping ads inside Performance Max are not affected by language settings.

What “matching based on the language of your ads” actually means

The new rule changes the eligibility signal, not the advertiser's obligation to write the ad. Google has not announced that it will translate an English RSA into French or Spanish for this process. If a brand wants a French ad experience, it should provide approved French creative and a properly localized landing page.

This matters in Canada. A bilingual user searching in French may still be eligible for an English ad if Google's signals indicate that they understand English and the query otherwise matches. A campaign name, a French keyword list or an old “French” language criterion will not, by itself, guarantee a French creative experience.

The stronger control is end-to-end localization: one language per ad group or tightly governed campaign segment, native-language RSA assets, matching sitelinks and callouts, a localized landing page, and a conversion path that stays in the same language.

Why multilingual campaign structure now matters more

Language separation becomes a creative and destination design problem rather than a campaign-checkbox problem. That does not mean every advertiser must rebuild one campaign per language. It means the account must make the intended language unambiguous at the point where ads and landing pages are selected.

When several campaigns or ad groups are eligible, Google says AI-based prioritization will select the most relevant ad language. That creates a practical risk: mixed-language asset pools can make the serving path harder to predict and the reporting harder to interpret.

The Performance Max split requires two control models

Performance Max does not lose language targeting everywhere. As Google's Help documentation confirms, Search inventory adopts ad-language matching, while YouTube, Display, Discover and Gmail continue using the campaign language setting. This means one Performance Max campaign now contains two language-governance paths.

For multilingual Performance Max campaigns, review asset groups as if their text and destinations are the Search-language control surface. Then review the campaign language selection separately for non-Search inventory. If the same campaign contains several languages, reporting by asset group, landing page and downstream lead language becomes more important because channel-level totals can hide cross-language leakage.

What changes for Google Ads API integrations?

Integrations should stop writing language criteria to Search campaigns. Existing language criteria can still be returned in queries even though they no longer apply to targeting. The developer announcement says attempts to add or update CampaignCriterion.language for Search will return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT.

Removing existing Search language criteria is optional cleanup, not a serving requirement. Performance Max mutates do not receive the same error because the language setting still applies to other inventory. Builders should therefore branch validation by campaign type rather than deleting the language field from every workflow.

A five-step multilingual account audit

1. Inventory every language surface

   Export Search, AI Max and Performance Max campaigns. Map ad groups, asset groups, RSAs, assets, landing pages and campaign language settings by intended locale.

2. Remove mixed-language creative pools

   Check every eligible text asset—not only RSA headlines. Separate inconsistent sitelinks, callouts, structured snippets, promotions and lead forms.

3. Trace the landing-page journey

   Test final URLs, redirects, URL expansion, language selectors, consent experiences, forms and thank-you pages. The journey should not silently revert to the site's default language.

4. Add language to measurement

   Capture ad or asset-group language, landing-page locale and form language in analytics and the CRM. Compare qualified-lead rate, sale rate, CPA and revenue by language—not just click-through rate.

5. Monitor overlap after rollout

   Review search terms, served ads, landing pages and language-specific conversion quality. Use negative keywords, tighter creative grouping and URL controls where irrelevant overlap appears.

Frequently asked questions

The operational takeaway

Campaign language is no longer a reliable Search budget wall. Creative language, destination language and measurement design become the controllable system.

Do not delete multilingual structure blindly. Keep separation where it supports budgets, reporting, legal requirements, regional offers or sales operations. But stop treating the campaign language checkbox as the mechanism that guarantees a localized Search journey.

Related reading and tools