Google Ads shuts the gate on manual language targeting

Why Google Ads language targeting disappears this September#

A fox does not need a signpost to know which trail is safe. It reads the wind, weighs the scent, and moves. From September 2026, Google Ads is asking every multilingual advertiser to trust the same instinct: Google Ads language targeting, the campaign-level setting that let you tell Search which languages an ad group should speak, is being removed. Not throttled, not deprecated with a grace period, removed.

The change is confirmed in Google's own language targeting help documentation, which states plainly that the campaign-level language targeting setting will be removed for Search campaigns, and that Search ads will instead automatically match based on the language of your ads. Search Engine Land reported the rollout as landing in late September 2026, and Search Engine Journal independently confirmed the same window, giving advertisers a firm, if quiet, deadline to work against.

The scope catches more than plain Search campaigns. Performance Max carries the same setting today, and the Search Network portion of Performance Max loses it too, a scope expansion first flagged by PPC Land's coverage of the rollout, which noted the change lands roughly nine months after Google's own 2025 documentation had originally promised it would be Search campaigns only. That is a real widening, and it is the detail most worth catching before you assume your Performance Max setup is untouched.

What still gets a manual language setting#

Performance Max is not losing language control everywhere at once. Per Google's Performance Max documentation, a Performance Max campaign spans YouTube, Display, Search, Discover, Gmail and Maps from one place, and the language setting you configure continues to govern everything except the Search slice. YouTube, Display, Discover and Gmail keep reading your manual setting after September. Only the ads competing on the Google Search results page, whether they arrive through a Search campaign or through Performance Max, move to automatic matching.

Advertisers who manage campaigns through the API rather than the interface feel this at code level too. Per the Google Ads API release notes, any attempt to add or update a language criterion on a Search campaign after the change ships will simply be rejected, and Google recommends developers stop sending language criteria for Search campaigns entirely rather than build around an error.

Read that quietly and it sounds administrative, tidy even, a setting Google decided was redundant once its own systems got good enough to infer it. Read it as an advertiser running campaigns across a dozen markets and it sounds like Google Ads language targeting was the fence keeping traffic in the right field, and from September the fence comes down.

How automatic matching replaces the old manual lever#

Take away a manual setting and something has to fill the gap, and Google is explicit about what that something is. Google's help page describes “AI-based ad group prioritisation” that ranks ad candidates by “the most relevant language(s) for the user,” built on the same prioritisation layer already rolling through AI Max Search campaigns.

This is not a new campaign type bolted on top of the old one. Per Google's own explanation of how AI Max Search campaigns work, it is an optimisation layer sitting inside the Search campaigns you already run, quietly widening match types and creative selection, and language now joins that same layer.

Four signals now do the work a dropdown used to do, and none of them are new, Google has simply promoted them from background context to the whole decision.

Put plainly, Google Ads language targeting, the manual kind, is being replaced by something closer to scent-tracking than switch-flipping. The old setting was a single, static instruction issued once at campaign level. The new system reads four live signals on every auction and picks a language the way a fox picks a path through brush, constantly, quietly, and without asking permission first.

AI Max Search campaigns, briefly explained#

If the phrase AI Max Search campaigns is new to you, it is worth thirty seconds. Google launched the feature in May 2025 as a suite of targeting and creative tools layered onto existing Search campaigns, including broader keyword matching and automatic landing page and text customisation.

Google's own case data, published on Google's product announcement, claims advertisers who activate it typically see roughly 14% more conversions or conversion value at a similar cost per action, a figure worth treating as Google's own internal benchmark rather than an independently audited number. The Google Ads language targeting change folds into that same machinery rather than sitting apart from it, which is precisely why folkfox is treating this as an PPC and creative problem together, not a settings-page footnote.

Why folkfox's multi-market clients feel this first#

folkfox runs paid search for operators and brands across iGaming, FinTech, healthcare and music industry clients, and almost every one of them advertises in more than one language somewhere in the EU or beyond. That is exactly the profile most exposed by Google Ads language targeting disappearing, because the manual setting was doing quiet, unglamorous work: keeping a Portuguese-language campaign from bleeding budget into Spanish searchers, or stopping a German compliance page from being matched against a Polish query where the regulatory wording simply does not carry across.

The risk is not that Google mistranslates anything. Nothing in Google's own documentation suggests ad copy gets auto-translated, and folkfox has found no evidence anywhere that it does. The real risk is mismatched impressions: an ad shown to a searcher whose signals suggest the wrong language fit, burning spend on a click that was never going to convert because the landing page could not close the gap the old manual language targeting used to guard. That is the practical cost of losing Google Ads language targeting: rarely a broken campaign, usually just a blurred one.

Every folkfox vertical carries a different flavour of exposure, and worth mapping before September rather than after.

None of that is catastrophic on its own. It is the kind of drift that shows up three weeks later as a soft dip in conversion rate that nobody can quite explain, the sort of thing a patient prowl through the account, not a panicked rebuild, actually catches.

The audit to run before September 2026#

The good news, and it is genuine good news, is that fixing exposure to Google Ads language targeting going away does not require touching campaign structure. It requires making the four automatic signals say the same clean thing your manual setting used to say by itself.

Search interest in the change itself is still small, which tracks: this is an account-hygiene story, not a headline one, and most advertisers have not gone looking for it yet.

That third row is worth a pause. Advertisers used to search "unsupported language google ads" when the platform blocked a language pairing outright, an error that told you something was wrong before you spent a cent. Once the setting is gone, that particular guardrail disappears with it. There is no longer a wall to hit, which means there is no longer a warning either, and that is the entire case for auditing now rather than waiting for a dashboard to tell you later.

None of that is dramatic, and none of it requires waiting for Google Ads language targeting to actually disappear before you start. It is the same discipline folkfox already applies across content marketing work: write for the reader you actually want, in the language they actually speak, and the machines reading over your shoulder tend to sort themselves out.

What to watch once the switch flips#

Google's own product liaison addressed the change directly once advertisers started asking questions, and PPC Land's reporting captured the tone: the campaign-level setting had become redundant once Google's systems could already read language from context, and the shift would land more quietly than the announcement made it sound. That may well be true for an account with clean, single-language copy already. It is a much bigger claim for an account that has never had to think about it.

The honest measurement plan starts from the assumption that Google Ads language targeting leaving does not create a visible failure. Nothing breaks, nothing errors, campaigns keep spending. The cost, if there is one, shows up as drift: impressions holding steady while conversion rate softens in exactly the markets where language used to be doing quiet work.

Track three things monthly from September, per market: impression share, click-through rate, and conversion rate, read together rather than in isolation. If impressions hold while conversion rate slides in one language pair specifically, that is not a bidding problem or a landing page speed problem, that is a Google Ads language targeting problem wearing a performance costume, and the fix is the same audit from the section above, not a bid strategy change.

The question worth asking your account, monthly#

Pick one line to defend at the next review: conversion rate by inferred market, held flat or better, for every language your account serves. It is a small, specific claim, and specific claims are exactly what survive an algorithm change that a vague one does not. It is also, not coincidentally, the same discipline folkfox brings to every SEO and GEO engagement: name the number, watch it monthly, and treat any drift as a signal worth outfoxing rather than an outcome to accept.

Two other Google changes worth reading alongside this one, both live on the account structure side of the same coin: On 17 August, your budget-capped campaigns stop overachieving, on how Smart Bidding retunes budget-limited campaigns, and The quiet price of the AI Max upgrade nobody opted into, on the invalid traffic climbing through the same AI Max layer this language change now shares.

Frequently asked questions#