Google Ads Is Removing Language Targeting in September. The Setting Was Never the Point.
The short version
Starting September 2026, Google removes the campaign-level language targeting setting from Search, from AI Max for Search, and from the Search Network portion of Performance Max. If you run single-language campaigns and nothing automated builds your campaigns, close the tab: Google is right that you have nothing to do. Everyone else has three things to know. The setting being removed never excluded a language, so most accounts are losing a control they already did not have. The real change is underneath it: the language of the query, not the user's inferred preference, now decides which of your creatives serves. And the part that will reach you first is not in the interface at all, it is CampaignCriterion.language writes on Search campaigns returning a hard error, which breaks duplication scripts, bulk templates and third-party platforms. Performance Max will not throw that error, so testing there tells you nothing.
What Google announced
On August 14, 2026, Ginny Marvin, Google's Ads Product Liaison, posted that the campaign-level language targeting setting is going away. Trade press had it under embargo the day before; Search Engine Land published on August 13 and put the rollout in late September. Google's language targeting help document now carries a note at the top, quoted verbatim by Search Engine Roundtable: "Starting in September 2026, the way language targeting works is changing for Search campaigns and the Search Network portion of Performance Max campaigns."
The mechanics, as Google states them. Search campaigns: the campaign-level setting is removed, and ads match automatically based on the language of the ads. AI Max for Search: in scope. Performance Max: the campaign-level language setting stops applying to ads on the Google Search Network, but continues to apply to YouTube, Display, Discover and Gmail; Shopping ads inside Performance Max are unaffected by language settings either way. The Google Ads API: stop setting language criteria on new Search campaigns; existing criteria can stay but will not apply.
Marvin's framing, also verbatim: "I know it sounds like a big shift, but it really isn't." And the reason: "As language targeting has evolved, the campaign-level setting has become redundant." Google says no action is required.
One piece of context the announcement does not include. Google documented this exact removal in August 2025, said it would be done by the end of 2025, and said at the time that non-Search campaign functionality would not change. It is roughly nine months late, and Performance Max, a non-Search campaign type, is now explicitly named. Both halves of the 2025 statement are now inoperative.
What it actually means
Start with the deflation, because it is real and because the rest of this brief is not credible without it.
The setting you are losing never excluded anything. Google says so in this announcement, and says it as a correction rather than a change: leaving a language unselected has never meant that language was excluded, and that is not changing. You can verify this against Google's own live documentation, which has said for years that ads are eligible "where the keywords match and Google believes that the user understands at least one targeted language," and which has carried an example of a Spanish-interface user being served an English ad. If you have ever set language targeting to English believing it fenced your campaign to English speakers, the fence was never there. Losing a control you already did not have is not an emergency. For a large share of accounts the correct response to this announcement is nothing at all.
Now the three things that are not nothing.
1. The behavior change is the prioritization flip, not the removal
Google's own explainer graphic breaks serving into three checks and marks each active or inactive, before and after. Check one, whether the user understands your ad and landing page, is active now and stays active. Check two, whether the campaign's language setting matches a user language, is active now and goes inactive. That is the deletion everyone is writing about.
Check three is prioritization, and it is what actually ships. When a user can understand your ads in more than one language, Google picks. For queries with no clear language, a brand term being Google's own example, it prioritizes the user's most preferred language, and that continues unchanged. For queries with a clear language, it prioritizes the ad and landing page matching that language, and that is marked inactive today, active in future. In Google's words from the graphic: "We prioritize ads that match the user's search term language."
Take Google's own long-standing documentation example: a user who reads English and Spanish, with a Spanish browser interface and heavy English search activity. Today, either creative can win, and the tiebreaker leans on her inferred preference. From September, a clearly Spanish query pulls the Spanish creative. That is a real change in which asset takes the slot, it applies whether or not you ever touched the language setting, and it is a tightening. Which is worth saying plainly, because the reflex on any 2026 Google announcement is to assume advertisers lost something. Here the removal is cosmetic and the substantive change is arguably in your favor, assuming your creative and landing pages are actually in the languages you think they are.
2. Inside Performance Max the setting does not die, it goes half-alive
This is the part no coverage has laid out, and it is the most confusing state in the announcement. After September, a Performance Max campaign has one language field that governs some of its surfaces and not others.
| Performance Max surface | Campaign language setting after September 2026 |
|---|---|
| Google Search Network | No longer applies. Behaves like a standard Search campaign. |
| YouTube | Still applies |
| Display | Still applies |
| Discover | Still applies |
| Gmail | Still applies |
| Shopping (within PMax) | Never applied, unchanged |
So the field stays in your settings panel, still editable, still governing three of the five channels a Performance Max campaign can serve on, and silently ignored on the one that usually carries the most volume. In a campaign type where channel-level visibility has been the standing complaint, a partially-honored setting is worse than a removed one. A removed setting teaches you it is gone. A half-live setting lets you keep believing it works.
3. The API returns a hard error, and it does not respect Google's rollout calendar
Attempts to add or update CampaignCriterion.language on a Search campaign will return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. Not a deprecation warning. Not a silent no-op. An error that fails the operation.
If you are picturing the settings panel, you are picturing the wrong surface. Think about everything that writes to a campaign. Campaign duplication scripts, which is how most agencies clone a proven build across clients or markets. Bulk sheet templates with a language column, which is how most agencies launch in volume. Third-party campaign management platforms, which write the full campaign object whether or not you asked them to set a language. Any of those can break, and the person who finds out is not the person reading this brief. It is whoever is launching at four o'clock on a Friday for a client who signed on Tuesday, working off a checklist whose step four says "set language targeting to match the market."
Two details make this worse than it looks. Performance Max does not return the same error, because language still influences its non-Search channels, so a team that tests on PMax gets a clean result and a false sense of safety. And this error is not new: it is the same error Google already returns today when you try to attach language criteria to campaign types that do not accept them, which means the enforcement machinery exists and Search is simply being added to it. That is why the API side is the part least likely to slip. The interface rollout is a September date on a change already nine months late. The API enforcement is a switch on a system already running.
Google is removing a setting that never excluded anything. The change worth your Monday is the one underneath it: the query's language now picks your creative, and your build script is about to start throwing errors.
Signal or noise: low for the setting, high for the build path
Low signal for the removal itself. Google's characterization is fair. Single-language campaign structures keep working, reporting does not change, exclusions were never supported, cross-language serving continues, and Google does not translate your creative and has now said so on the record, which matters for regulated advertisers running per-market compliance copy.
High signal if anything automated writes your Search campaigns: scripts, bulk sheets, Editor workflows, or a third-party platform. That is a hard failure with a fixed error string, and it is a per-process problem rather than a per-account one, which makes it cheap to test and expensive to ignore.
Medium signal if you run Performance Max, because you now have a setting that governs three of five surfaces and no interface cue telling you which. Worth one pass through your campaigns to decide whether the surviving three are the ones you meant to constrain.
And a scheduling note that is itself the verdict: do not plan against Google's month. This change was promised for the end of 2025 and arrived nine months late. Plan against your own next campaign launch.
The Monday-morning playbook
- Run the ten-minute process test first, because it covers your entire book. Build one throwaway Search campaign through whatever you normally launch with: your script, your bulk sheet template, Editor, or your third-party platform. If it sets a language criterion, it will fail once enforcement lands. Test the launch path, not the settings panel.
- Do not run that test on Performance Max and call it done. PMax will not return the error. A clean PMax result proves nothing about your Search launch path.
- Search your automation for language criteria. Duplication scripts first, because cloning a proven build across markets is exactly the workflow that writes language on create. Bulk templates with a language column second. Paste
OPERATION_NOT_PERMITTED_FOR_CONTEXTinto your internal runbook so the person who hits it on a Friday afternoon can find the answer in one search. - Ask your platform vendor in writing. If a third party creates campaigns on your behalf, you cannot fix their write path. Get their remediation date before September, not after.
- Apply the two-question test to decide whether the rest of this matters. Do you run more than one language of creative that the same user could plausibly read? Does anything automated build your campaigns? Two noes and you are done, genuinely.
- Build the split-state table for your own Performance Max campaigns. For each one carrying a language setting, note that Search stops honoring it while YouTube, Display, Discover and Gmail continue to. Decide per campaign whether constraining only those three is what you actually want.
- Audit ad and landing page language on whatever survived step five. These are now the primary matching signal, and Google does not translate creative. A landing page in the wrong language is a serving problem now, not a housekeeping item.
- Freeze a September 1 baseline on Search before anything else lands. Export search terms and asset performance ahead of the AI Max auto-upgrade, which hits automatically created assets and campaign-level broad match campaigns that same day. Two platform changes inside one reporting month means one clean boundary is the only way to tell them apart later.
The bottom line
This is a small announcement wrapped around a medium one. The setting Google is deleting was a placebo for most advertisers, and saying otherwise to manufacture urgency would be dishonest. But the prioritization flip underneath it changes which creative wins a bilingual auction, the Performance Max split leaves a live setting quietly governing three of five surfaces, and the API error is a hard break aimed squarely at the automation most agencies launch from. The pattern is familiar from AI Max and from the bid target change: the headline is a control being retired, and the consequence is somewhere else in the stack. Spend ten minutes on your build path this week. Spend zero on the dropdown. (For the strategic version of the argument about what happens as Google's observation layer narrows, that is The Sealed Auction on Uncommon Move.)
Sources
- Google Ads Help: "About language targeting", the primary document, updated with the September 2026 note
- Search Engine Land: "Google Ads is removing language targeting from Search campaigns", August 13, 2026, first coverage under embargo, and the source for the API error constant
- Search Engine Roundtable: "Google Ads Language Targeting Update Coming In September", August 14, 2026, quotes the help doc note verbatim and reproduces Google's explainer graphic and the advertiser email
- PPC Land: "Google Ads drops language targeting in September, nine months past deadline", August 14, 2026, for the three-check graphic breakdown and the 2025 deadline history
Google announced this through the Ads Product Liaison's social posts and an advertiser email rather than the Google Ads announcements page, which has published nothing since May 20, 2026. The API error constant reaches this brief through Search Engine Land's reporting of Google's developer blog rather than from the developer blog directly; it will be reconfirmed against the primary post and this brief updated if the wording differs.
Frequently asked
When is Google Ads removing language targeting?
Google announced on August 14, 2026 that campaign-level language targeting is being removed starting in September 2026, affecting Search campaigns, AI Max for Search campaigns, and the Search Network portion of Performance Max. Search Engine Land reported the rollout as beginning in late September. Google first documented this same removal in August 2025 and promised it by the end of 2025, so the current date is roughly nine months past the original deadline and has already moved once.
Does language targeting still apply to Performance Max?
Partly. From September 2026 the campaign-level language setting no longer applies to Performance Max ads shown on the Google Search Network, which will behave like standard Search campaigns. The language settings you select do continue to apply to YouTube, Display, Discover and Gmail within the same campaign. Shopping ads inside Performance Max were never governed by language settings. So one language field will govern three of the five surfaces a Performance Max campaign can serve on.
Why does setting language targeting return OPERATION_NOT_PERMITTED_FOR_CONTEXT?
Once the change is enforced, attempts to add or update CampaignCriterion.language on a Search campaign through the Google Ads API return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. It is a hard error rather than a deprecation warning, and it affects anything that writes a full campaign object, including duplication scripts, bulk sheet templates with a language column, and third-party campaign management platforms. Performance Max campaigns do not return the same error, because language still influences their non-Search channels, so testing only on Performance Max produces a false all-clear.
Get the next brief in your inbox
When Google ships something that matters, you'll get the decode: what changed, whether it's signal or noise, and the move worth making this week. Free, no firehose, unsubscribe any time.