Google Ads Is Removing Language Targeting: What Advertisers Should Do Before Late September 2026

Google Ads is changing how language works in Search advertising. From late September 2026, the campaign-level language setting will be removed from Search and AI Max for Search campaigns. Search ads will instead match on the language of the ad and landing page, combined with signals about the languages a user understands.

Google announced this on 13 August 2026 and says existing campaigns will continue without disruption, with no mandatory action required. That is reassuring but incomplete. Multilingual advertisers should still audit their accounts before rollout: confirm every active language has accurate ad copy and a matching landing page, keep location and language decisions separate, review mixed-language search terms, and record a performance baseline now.

With the rollout only weeks away, the window for a clean pre-change snapshot is closing. Export your baseline data this week, not next month.

What changes in late September 2026

Google's language-targeting documentation describes the new model in three parts:

• Campaign language settings are no longer required for Search.
• Language comprehension signals align eligible ads with languages a user understands.
• When a search term has a clear language, Google prioritises the ad and landing page matching that language.

Google infers language from account settings, stated preferences, search behaviour and other interactions. A bilingual user may remain eligible for ads in more than one language. The meaningful shift is prioritisation: when the query itself is clearly in one language, the matching creative gets preference.

Source: Google Ads Help and the Google Ads Developer Blog.

This is not automatic translation. Advertisers still need deliberate, accurate creative and landing pages for every language they want to serve. Removing a dropdown does not create a reviewed Hindi, Punjabi, Spanish or French customer journey where none existed.

Search and Performance Max do not change the same way

The most common implementation mistake will be assuming the language setting disappeared everywhere.

Performance Max serves across Search, YouTube, Display, Discover, Gmail and other inventory. After this update, only its Search portion adopts the new matching behaviour. A result you observe on Search cannot be assumed to explain a change across the whole campaign. Segment before you diagnose.

Why multilingual advertisers should care

The change matters most where customers move fluidly between languages. In India, someone may use an English interface, search in Hindi, type Punjabi in Latin characters and then fill out a form in English. The same pattern appears across other multilingual markets.

Language is not only a targeting field. It shapes the promise made in the ad, the clarity of the landing page, form completion rates, call handling and lead quality. A technically eligible ad can still perform badly when the click lands on a page the user does not comfortably read.

Treat language as part of the whole conversion journey rather than one setting Google now manages for you.

An eight-point pre-rollout audit

• 1. Map the languages customers actually use: Start with evidence: search terms, website analytics, call notes, chat transcripts, sales conversations. Separate the language a customer understands from the language they use when expressing commercial intent. These are often different. Include transliterated and mixed-language queries. Label these patterns rather than forcing every query into a clean language bucket.
• 2. Inventory ads and landing pages by language: Build a simple map: campaign, ad group, ad language, final URL, landing-page language. Flag any path where the ad and page disagree, or where the page switches language before the conversion action. For regulated or contractual offers, confirm disclaimers remain accurate in every version. Do not publish unreviewed machine translation to expand coverage.
• 3. Keep thematic campaign structure clear: Google's AI-based ad-group prioritisation considers query meaning, keywords, ad-group context and landing pages. The update does not make account structure irrelevant. Keep language versions separate when you need independent budgets, local offers, approval workflows, reporting or distinct landing pages. A shared structure works when the offer, geography and conversion journey are genuinely the same. Choose structure for control and measurement, not because a dropdown appeared or vanished.
• 4. Review keywords and search terms together: Check whether ad groups in different languages can match the same intent. Pay attention to brand queries, short product terms and borrowed words that carry no clear language signal. These ambiguous searches will lean more heavily on the user's preferred-language signals. After rollout, review the query, the served ad, the landing page and the conversion outcome as a single unit. A healthy click-through rate can mask a poor post-click experience.
• 5. Audit responsive search ad assets: Every intended language needs enough accurate headlines and descriptions to communicate the offer, location, price condition and next step. Check pinned assets, legal wording and promotion dates, and confirm the final URL supports the same promise. If AI Max text customisation is enabled, inspect the generated assets directly. Language automation is not a guarantee of translation quality.
• 6. Treat Performance Max as a channel-specific case: Document the campaign's selected languages and each asset group's languages. Search inventory adopts the new behaviour; YouTube, Display, Discover and Gmail still use campaign language settings; Shopping ads are unaffected. If results move after rollout, segment reporting as far as the platform allows and examine asset groups, search terms and placement context before blaming the language change.
• 7. Record a clean baseline now: Export at least the trailing four weeks of impressions, clicks, cost, conversion rate, cost per qualified conversion and conversion value by campaign. Save search terms and landing-page performance where volume allows. Do this before rollout, since you can no longer collect a fresh four-week window in advance. Annotate promotions, budget changes, tracking fixes, seasonality and AI Max migrations. Without this, ordinary demand swings or a simultaneous bid change will be misread as a language effect.
• 8. Use a controlled monitoring window: On rollout day, check serving status, disapprovals, spend pace and destination URLs. Over the following two weeks, inspect language patterns, search terms, lead quality and any shift between parallel campaign versions. Low-volume accounts need longer. Do not change language structure, bid strategy, conversion goals and budgets at the same time unless something genuinely urgent forces it. One clean change produces more usable evidence than five reactive edits.

A timing caution for Indian and other festive-season markets: October and early November demand rises sharply ahead of Navratri, Dussehra and Diwali. A short before-and-after comparison across that period will blend the language change with seasonality. Compare against the same weeks last year where you can.

A practical structure for three common situations

• Single-language local business. Confirm ads, pages, forms and call handling all use the same language. Do not add translations without customer demand and the operational capacity to support them.
• Bilingual lead-generation business. Use dedicated language paths where creative, pages, budgets or sales handling differ. Compare qualified leads, not clicks.
• Multilingual ecommerce store. Align ad language with localised product details, currency, shipping, returns and support. Test the full checkout journey in each language.

What advertisers should not do

• Do not assume that leaving a language unselected previously acted as a guaranteed exclusion.
• Do not merge every language into one ad group simply because Google can prioritise eligible ads.
• Do not send translated creative to a landing page in another language.
• Do not judge success on search volume alone. Monitor qualified leads, revenue and support quality.
• Do not adjust location targeting in response to this change. Language and geography answer different questions.

What this means for API users

Google says language criteria may still appear in API queries even though they no longer apply to Search targeting. Attempts to add or update CampaignCriterion.language for Search will return an OPERATION_NOT_PERMITTED_FOR_CONTEXT error.

Stop setting language criteria on new or updated Search campaigns. Removing existing criteria is optional. Performance Max is the exception, since its non-Search channels still use language targeting. Also check any scripts, automated rules, bulk upload sheets or Editor workflows that reference the language field, as these can fail quietly.

Frequently asked questions