Google Ads Is Removing Manual Language Targeting in September 2026: What Actually Changes

If your Google Ads account runs separate campaigns for different languages, English and Spanish split out on purpose, French creative aimed only at French-speaking searchers, a setting you have relied on for years is about to stop working the way it always has. Starting in September 2026, Google is removing the manual language targeting setting from standard Search campaigns entirely, along with the Search Network portion of Performance Max, and replacing it with automated, AI-driven language matching that decides which language version of your ad to show based on signals Google collects at the moment of auction, not a setting you control directly.

Google first signaled this change back in August 2025, when its own help documentation quietly stated the language targeting setting would be removed from Search campaigns by the end of that year. That deadline came and went with no removal. Ginny Marvin, Google's Ads Product Liaison, confirmed on August 14, 2026, in a LinkedIn post, that the removal is now actually happening, roughly nine months past the original timeline, with the change rolling out through September 2026. Delays of that length are not unusual in Google Ads deprecations, but the practical upshot for advertisers is the same regardless of how late it arrived: a setting you may have configured once and never thought about again is going away, and what replaces it works differently enough to be worth understanding before it lands in your account.

This post covers exactly what the Campaign.languages setting controlled before this change, what Google's automated matching does instead, which campaign types are affected and which are not, and what to actually check in your account this month if you run any kind of multilingual advertising. Miraflow's AI Image Generator is worth having open while you review this, since a fair number of the fixes below come down to needing distinct, language-appropriate creative fast rather than reusing the same visual across every language version of a campaign.

What the Language Targeting Setting Used to Do

Before this change, every standard Search campaign had a language targeting setting, sitting in campaign-level settings, that let an advertiser explicitly declare which language or languages of searcher Google should show that campaign's ads to. Google used the language a user had set as their Google interface language, along with signals from their recent browsing behavior, to decide whether that user counted as an English speaker, a Spanish speaker, and so on, and a campaign restricted to English would then only serve to users who matched that language setting.

This was the mechanism advertisers used to run genuinely separate campaigns for different language markets under one account: a campaign targeting English speakers with English-language ad copy and an English landing page, a separate campaign targeting Spanish speakers with Spanish-language copy and a matching landing page, each with its own budget, its own bid strategy, and its own performance reporting, kept cleanly apart by the language setting doing the traffic splitting.

The Search Network portion of Performance Max campaigns used the same underlying language setting to control which language version of assets got shown on Search placements specifically, while the campaign's other channels, YouTube, Display, Discover, and Gmail, relied on different signals entirely and are not touched by this change.

What Changes in September 2026

Starting in September 2026, Google is removing the language targeting setting from standard Search campaigns and from the Search Network portion of Performance Max campaigns. The setting itself disappears from campaign settings in the interface, and on the current Google Ads API version, an attempt to explicitly set a language criterion now returns an error rather than applying it. On older API versions still used by some scripts and bulk-management tools, the call does not error out, but the language value is simply ignored going forward, which means a script that believes it is still restricting a campaign by language is quietly no longer doing so.

In place of the manual setting, Google is relying on what it describes as enhanced AI-driven ad and asset group prioritization to automatically select the most relevant language version of an ad based on each user's search context and language preferences at the moment of the auction. The system is designed to favor the ad and landing page whose language matches the language of the actual search term being typed, rather than relying solely on a user's declared interface language the way the old system did. According to Google's own framing of the change, this is not eliminating language matching from Search, it is automating a process advertisers previously had to configure manually.

For advertisers using single-language account structures, a campaign built entirely around English ads and an English landing page, with no explicit multilingual targeting configured, Google states these campaigns will continue functioning as they do now. The practical risk of this change concentrates almost entirely on accounts running genuinely multilingual structures, separate campaigns deliberately split by language, or bilingual markets where an advertiser wants tight control over which language version reaches which searcher.

What Stays the Same

Google has been specific about four things this change does not touch, and it is worth being precise about each one, since some of the confusion around this update comes from assuming it changes more than it actually does.

Language exclusions remain unsupported, which was already true before this change and is not a new limitation introduced here. Ad creatives are not auto-translated by this system, Google's automated matching selects among the language versions an advertiser has actually created and uploaded, it does not generate a new translation of an ad that does not already exist in a given language. Reporting continues unchanged, meaning your existing performance data and segmentation are not retroactively affected by this update. And cross-language ad matching, showing an ad in a language different from a user's primary declared language when Google's signals suggest the user can understand it, was already possible in limited circumstances before this change and continues to work the same way.

Why Google Made This Change

Google's stated rationale is consistency with how Performance Max and its broader AI Max products already operate. AI Max campaigns and Performance Max have both leaned increasingly on automated signal-matching rather than advertiser-configured targeting rules, on the logic that Google's models, evaluating a specific search term, a user's actual language signals, and the available ad and landing page language versions at the moment of auction, can make a more precise, real-time match than a static campaign-level setting that was configured once and rarely revisited.

That reasoning tracks with a genuinely busy year of automation-by-default changes across the platform. Standard Search campaigns using campaign-level broad match or automatically created assets are being auto-upgraded to AI Max starting September 1, 2026, a change Miraflow covered in detail in our piece on the AI Max Search auto-upgrade. Target CPA and Target ROAS bidding behavior changed for budget-limited campaigns on August 17, ending a pattern where those strategies often quietly delivered a lower actual cost per acquisition than the target an advertiser had set, covered in our breakdown of the August 2026 target bid strategy update. Local Inventory Ads became the default on every Shopping campaign on August 31, removing another manual opt-in the same month. None of these changes share a mechanism with language targeting removal, but they share the same underlying shape: a setting that used to require deliberate advertiser configuration is being replaced by a system-level default, and an account team that only checks Google Ads settings occasionally is the group most likely to be caught off guard by more than one of these landing in close succession.

Who This Actually Affects, and How Much

The honest answer here depends heavily on your account structure, and the two ends of that spectrum look almost nothing alike.

If You Run a Single-Language Account

If your entire Google Ads account runs English-only campaigns, or whatever your single primary market language is, with no deliberate multilingual splitting, this change is close to a non-event for you. Google states these campaigns will continue functioning as they do now, and the automated matching system has no meaningfully different job to do when there is only one language of creative and one language of landing page in play. It is still worth a quick check that nothing in your account was quietly configured for multiple languages by a past agency or team member without your current team's knowledge, but for a genuinely single-language advertiser, the practical action item here is minimal.

If You Run Genuinely Multilingual or Bilingual-Market Campaigns

This is where the change deserves real attention. If your account deliberately separates campaigns by language, whether that is a national brand serving both English and Spanish speaking markets, a European advertiser running distinct campaigns per country language, or any account where language targeting was the mechanism keeping traffic cleanly split, the new automated system introduces genuine uncertainty that a static setting did not have.

The core risk is a subtler version of cross-contamination between campaigns that used to be cleanly separated. Once the language setting stops constraining which campaign a given search term's traffic flows into, Google's automated system is making that decision instead, based on the language of the search query and the language of your available ad and landing page assets. If your Spanish-language campaign and your English-language campaign are both eligible to serve on overlapping keywords, which is common for bilingual markets where the same core keywords get searched in either language depending on the individual searcher, the automated system's language-matching decision determines which campaign's budget actually gets spent on a given impression, not your account structure.

There is also a new prioritization behavior worth understanding specifically: the system is designed to favor the ad and landing page whose language matches the language of the search term itself, even when a bilingual user might understand either language equally well. In practice, that means a bilingual searcher typing a query in Spanish is more likely to see your Spanish-language ad, even if that same user has historically converted well on your English-language landing page, or vice versa. For a brand that has spent real time optimizing one language version's landing page and conversion rate more heavily than the other, this shift in matching logic can meaningfully change which version of your funnel gets the traffic.

What to Check in Your Account This Month

Here is the practical sequence worth running through if any part of your account touches multiple languages, whether through deliberate campaign splitting or a Performance Max campaign with Search Network placements active.

Step one: identify every campaign currently using a non-default language targeting setting. Go through your account's Search campaigns and any Performance Max campaigns with Search Network placements enabled, and note which ones have an explicit language restriction configured today. This is your actual exposure list, everything outside this list is largely unaffected.

Step two: check whether your ad copy and landing pages actually exist in every language your campaign structure implies. Since the new system does not auto-translate anything, it can only match a searcher to a language version you have genuinely created. If a campaign was relying on the old language setting to restrict traffic while quietly running ad copy that was never actually translated for that audience, that gap becomes more visible under automated matching than it was under a manual restriction.

Step three: for bilingual or multi-market accounts, decide which language version should be the priority for keywords that get searched in either language. Since the new system prioritizes matching the search term's own language, if you have a real business reason to prefer one language version's conversion path for a given keyword regardless of which language it was searched in, you will not be able to enforce that through a targeting setting anymore, and need to think through your landing page and creative strategy accordingly.

Step four: audit any scripts, bulk upload templates, or third-party tools that reference language criteria at the API level. If a script is still submitting a language criterion against an older API version, it is not erroring, it is being silently ignored, which means your tool's own logs or dashboard may still show a language restriction that is no longer actually being enforced on the live campaign. Update any such scripts to stop relying on the deprecated field.

Step five: pull recent performance data by campaign after the rollout completes and look specifically for changes in language-mismatched traffic. A Spanish-language campaign suddenly showing meaningfully different traffic volume or a shift in which landing page is converting is the clearest signal the automated matching system has started actively reshaping how your bilingual traffic gets split.

Step six: for API-managed accounts, stop submitting language criteria on any new or updated Search campaigns going forward. Google's own guidance is direct here, once this rollout completes, continuing to submit Campaign.languages values on current API versions returns an error, and any automation pipeline that has not been updated to remove those calls will start failing on campaign creation or updates rather than just having the setting ignored.

What Advertisers Should Actually Do

Beyond the audit steps above, there are a few structural decisions worth making deliberately rather than letting the automated system decide by default.

Ensure every ad and landing page is unambiguously written in the language it is meant to serve, and structured clearly enough that Google's language-detection signals have an easy job. A landing page that mixes languages, or ad copy that is technically translated but reads awkwardly, gives the automated matching system a weaker signal to work with and increases the odds of a mismatch.

Review multilingual campaign structures with a genuine eye toward what happens if traffic that used to be cleanly split starts overlapping. For accounts where that overlap creates a real business problem, distinct offers or promotions that should not cross language lines, for example, consider whether a stronger structural separation, distinct domains or distinct ad group naming that reinforces the language distinction through other signals, gives you more confidence than relying on the new automated system alone.

Monitor performance closely for the first several weeks after the rollout completes rather than assuming existing performance patterns hold. Because the underlying matching mechanism changed, historical performance data for a given campaign may not predict how that same campaign performs once automated language matching is actually deciding its traffic mix.

For any script, bulk template, or automation pipeline, migrate away from Campaign.languages now rather than waiting for it to start erroring in production. This is the one piece of this change with a hard technical deadline attached, since a pipeline that keeps submitting the deprecated field will fail outright once the current API version stops accepting it.

Common Mistakes to Avoid

The first mistake is assuming this only affects advertisers running international or heavily multilingual campaigns. Any account with even one bilingual-market campaign, or one Performance Max campaign with meaningful Search Network volume in a market where more than one language is commonly searched, has real exposure here, not just accounts running dozens of country-specific campaigns.

The second mistake is treating the removal of the language setting as removing language matching altogether. Google's own framing is specific on this point, language matching is being automated, not eliminated, which means the practical question is not whether your ads will reach the right language audience, it is whether the automated system's matching logic aligns with the campaign structure and priorities you built manually.

The third mistake is assuming an older API version protects you from any disruption because the deprecated field does not error there. Silent failure is still failure. A script submitting a language criterion on an older API version is no longer having any actual effect on campaign targeting, even though nothing in that script's own execution log shows an error, which is exactly the kind of quiet mismatch between what a management tool believes is configured and what Google is actually doing that causes real surprises weeks later.

The fourth mistake is doing nothing simply because your account currently looks unaffected in a spot check. This change specifically shifts behavior for keywords and search terms that could reasonably be searched in more than one language, which is not always obvious from a quick glance at campaign settings, and is worth actually pulling performance data to confirm rather than assuming.

The fifth mistake is conflating this change with the AI Max Search auto-upgrade happening in the same general period. They are separate mechanisms, one governs which campaign type your Search campaign runs as, the other governs how language-based traffic gets matched within whatever campaign type you are running. Reviewing only one while assuming it covers the other leaves a real gap in your audit.

Building Language-Specific Creative Faster With Miraflow

Whichever side of this change your account falls on, single-language and largely unaffected, or genuinely multilingual and now needing tighter, more deliberate creative for each language version, there is a real practical task attached: making sure every language version of your ad creative is strong enough to compete on its own, rather than relying on a shared visual with a weaker, secondary translated headline bolted on.

This matters more under automated language matching than it did under manual targeting, precisely because the system is now actively deciding, search by search, which language version of your ad and landing page gets the impression. A Spanish-language ad with genuinely tailored, culturally appropriate visuals and copy has a real advantage over one that is simply an English ad with translated text pasted over the same generic stock imagery, especially now that the matching decision itself is happening automatically rather than being pre-filtered by a campaign-level language restriction.

Miraflow's AI Image Generator makes it realistic to build genuinely distinct creative for each language market quickly, directly in the browser, rather than treating translation as an afterthought layered on top of a single shared visual. Text-to-image generation covers a new visual concept built specifically for a given market, while image-to-image editing and inpainting let you adapt an existing creative, a background, a prop, a setting detail, that reads better for a specific audience without redoing the whole asset from scratch. The same generator is useful for building Google Ads display banner creative that matches each language version's distinct visual identity, so a bilingual campaign structure has real creative differentiation behind it, not just translated text.

If you are also reviewing other Google Ads mechanics that changed with limited advance notice this year, Miraflow's coverage of Google's Ask Advisor AI agent inside Google Ads is a useful companion read for asking account-specific questions about a change like this one directly inside the platform, rather than digging through settings screens manually every time something shifts.

Frequently Asked Questions

When exactly does this change take effect? Google first announced the removal in August 2025 with an end-of-2025 target that was missed. Ginny Marvin confirmed on August 14, 2026 that the removal is rolling out through September 2026, roughly nine months past the original timeline.

Does this affect Performance Max campaigns entirely, or just part of them? Only the Search Network portion of Performance Max is affected. Language settings continue to guide YouTube, Display, Discover, and Gmail placements within a Performance Max campaign as they did before. Shopping ads running inside Performance Max are unaffected by this change.

Will my ads suddenly show in the wrong language to my customers? Google states that single-language account structures will continue functioning as they do now. The real risk is concentrated in accounts running genuinely multilingual or bilingual-market campaigns, where automated matching now decides which language version of your ad and landing page a given searcher sees, based on the language of their search term, rather than a manual campaign-level restriction.

Do I need to do anything if my account only runs one language? Little to no action is required, though it is worth a quick check that no legacy multilingual configuration exists in your account from a past agency or team member that you are not currently aware of.

What happens to my existing language targeting settings if I do nothing? Existing language criteria can remain in your account and will simply no longer influence targeting going forward. You can optionally delete them for account cleanliness, but leaving them in place does not cause an error or a functional problem beyond the fact that they no longer do anything.

Will Google auto-translate my ads into other languages now? No. The automated matching system selects among language versions of ad copy and landing pages that you have actually created. It does not generate a new translation of an ad that does not already exist in a given language.

What should I do with scripts or bulk tools that still reference the old language targeting field? Update them now rather than waiting. On the current Google Ads API version, submitting a language criterion returns an error. On older API versions it is silently ignored rather than applied, which can create a mismatch between what your tool believes is configured and what is actually happening in the live campaign.

Conclusion

This is a change that will pass unnoticed for a large share of Google Ads accounts and matter quite a bit for a smaller, specific group, anyone running genuine multilingual or bilingual-market campaign structures where language targeting was doing real, deliberate work. The setting itself disappearing is not really the story. The story is that a decision advertisers used to make explicitly, which language version of an ad a given searcher sees, is now being made automatically by Google's models at the moment of auction, and the practical result of that shift depends heavily on how strong and how genuinely distinct your different language versions of creative and landing pages actually are.

Check whether your account has any real multilingual exposure this month, migrate any scripts still referencing the deprecated field, and if your different language markets have been sharing the same generic creative with only the text translated, treat this as a real reason to build something more deliberately tailored for each one. Miraflow's AI Image Generator is a fast way to close that gap directly in the browser, and pairing genuinely distinct, market-appropriate creative with a clear understanding of how the new automated matching behaves is a better long-term position than hoping the old campaign structure keeps working exactly the way it always did.