The same removal was announced 360 days ago and never happened
Google is retiring campaign-level language targeting from Search and AI Max in late September. It said the same thing on 18 August 2025, with a deadline of "the end of 2025." Knowing that changes what you should do this week.
The announcement. On 13 August 2026 Google said that from late September the campaign-level language targeting setting will be removed from Search and AI Max for Search campaigns. Matching will run on the language of your ads and landing pages instead.
The part that is missing from the coverage. Google announced the identical removal on 18 August 2025, with a deadline of the end of 2025. It did not happen. Two announcements, 360 days apart, different dates, wider scope the second time.
What you get from this page. Why the mechanism replacing your setting is not documented yet, the exact API error to grep your code for, and how to tell whether any of this touches your account.
- You know tonight whether your account uses language as a separator, or only as a description.
- You know what survives: on YouTube, Display, Discover and Gmail the setting keeps working.
- You have the error string to search your automation for before it stops a campaign build.
- You have our count of how many Google help pages carry the notice, on a set you can rebuild yourself.
What this page is about
Language targeting inside Google Ads — the setting you tick when you build a campaign. Not the language of your website, which is an SEO question, and not ad translation, which stays your job. After this change it matters more, not less.
A platform announcement that arrives once asks you to reorganise. The same announcement arriving a second time, with a new date, asks for something different: get ready, but do not tear anything apart. Almost every write-up of this week's news is missing the fact that decides which of the two you are looking at.
Announced twice, 360 days apart
On Thursday 13 August 2026, Dora Sun of the Google Ads API team posted a short note on the Google Ads Developer Blog:
We're making changes to language targeting for Search, AI Max for Search, and Performance Max campaigns in Google Ads, simplifying campaign management while maintaining a high-quality ad experience.
The date and the first consequence follow: "Effective late September 2026 […] For Search and AI Max for Search campaigns, the campaign-level language targeting setting will be removed. Search ads will automatically match based on the language of your ads."
Read on its own, it is a routine deprecation. It stops being routine next to a piece Barry Schwartz published on Search Engine Roundtable on 18 August 2025, under the headline "Google Ads Language Targeting For Search Campaigns Going Away." The notice had appeared, in his words, "posted quietly" at the top of a help document. Its text:
Note: By the end of 2025, the language targeting setting will be removed from Google Ads Search campaigns. You won't have to set a campaign language targeting manually. Language will be automatically detected with the help of Google AI. Non-Search campaign functionality won't change.
The end of 2025 came and went. That the setting still exists is not our inference — the August 2026 post announces removing it, which means it is there. The gap between the two announcements is 360 days.
Two things did change in the second telling, and they are worth separating from the repetition. The scope is wider: the 2025 note explicitly said non-Search campaigns would not change, while the 2026 post pulls in Performance Max, for half of its surfaces. And the channel is different: a line that appeared silently in a help centre has become a signed developer-blog post with instructions for code.
What replaces it is not documented
When several campaigns in one account could answer the same search, something has to pick one. The post disposes of that in a single sentence:
In cases where multiple eligible campaigns exist within your account, AI-based ad group prioritization will select the most relevant ad language.
That is the most consequential line in the post and the most hurried, because it is the only place where Google says what takes over from your setting. So we opened the page describing that mechanism, "About ad group and asset group prioritization within a Google Ads account," to see how it chooses.
The page is real and detailed. It publishes a priority table: exact match keywords identical to the search term first, phrase and broad keywords or search themes identical to the term second, and third a row reading "Relevance: AI (artificial intelligence) based ad and asset group prioritization."
In the body of that page, the word "language" does not appear at all. Searched across the whole HTML it turns up exactly once, as the label on the footer language switcher — site furniture, not content. As of 14 August 2026, the mechanism that will choose which language to speak to your customers in is not described for language on the page Google points to.
This is not an accusation. Features are routinely announced before they are explained, and the page will probably be updated. But it is the fact that should govern what you do today: if nobody can say how the language will be picked, there is no sense in rebuilding an account around that choice. There is sense in tidying the only two signals Google explicitly names — your ads and your landing pages.
What language targeting is
Language targeting is the campaign setting that tells Google Ads which languages your ads are eligible to appear in, based on the languages Google believes a user understands. It translates nothing and filters no keywords: it decides only which people your campaign can enter an auction for.
There is a misunderstanding worth clearing first, because it explains why this setting never did what many advertisers thought it did. It does not look at the language of the query. It looks at the language of the person. Google's own documentation gives the example: someone who understands English and searches in Spanish for "zapatos azules" can be served an English ad matching the keyword "blue shoes."
So the box you are about to lose was never a precise switch. It was a soft filter, already interpreted by Google's systems. September does not introduce the automation. It removes the alternative.
What changes, campaign type by campaign type
The post splits into three cases that behave differently, and the difference is where the practical risk sits.
Search and AI Max for Search. The campaign-level setting is removed. Matching runs on the language of your ads.
Performance Max, Search surface. "The campaign-level language setting will no longer be used for ads shown on Google Search. Language matching will function the same as Search campaigns, using the language of your ads." The box stays in the panel; it simply stops applying there.
Performance Max, everything else. Unchanged, and this is the half almost nobody reports: "On other channels (like YouTube, Display, Discover, Gmail): The campaign-level language setting you select will continue to be used to guide who sees your ads."
The practical consequence is odd enough to be worth stating plainly. After September, inside a single Performance Max campaign, the same checkbox will be ignored on one surface and obeyed on four others. Anyone who clears it "because it does nothing now" is changing how that campaign behaves on YouTube, Display, Discover and Gmail without meaning to.
The API line, if anything writes to your account
If a tool, a feed or a script creates or edits your campaigns, this is the sentence that matters:
Any mutates to add or update Search campaign CampaignCriterion.language will result in a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error. For Performance Max campaigns, there will be no error as language targeting may be used on other channels.
Three things follow. Existing language criteria keep being returned by queries even though they no longer drive targeting, so a check that only reads will notice nothing. The error is write-only, and Search-only. And the case that actually breaks is the script that rebuilds campaigns from scratch on a schedule and sets language as an early step — that step will stop.
Google advises against setting language criteria on new Search campaigns and calls removing them from existing ones optional, "for cleanliness." On that second half we would not rush. An unused criterion harms nothing, while cleaning up a Performance Max campaign today removes a setting that its other surfaces still use.
How many help pages carry the notice
When a story says "Google put it in the documentation," the useful question is not whether that is true. It is how reachable the notice is for someone starting from their own account. So we counted.
On 14 August 2026 we pulled, from our own server, all thirteen Google Ads help pages linked from "About language targeting" — the entire neighbourhood someone starting there would walk through. Each fetched three times, with ?hl=en, ?hl=it and ?hl=ro: thirty-nine pages. We matched the notice as a whole, not a single word, so the AI Max announcements that also mention September 2026 in the same window would not be counted.
The notice appears on one page out of thirteen, and it is the same page in all three languages: "About language targeting." The other twelve do not carry it, in any language.
One of those twelve weighs more than the rest. "Choose your location and language settings" is the instructions page — the one someone opens while building a campaign to find out where to click. As of 14 August 2026 it still teaches the gesture that is being retired: "To edit your target language, enter a language in the search box. Check the box next to the language that you'd like to target." It goes on to explain how to change language across several campaigns at once, from the Edit menu. It carries no notice and no link to the change.
The line sits on the page that describes the feature. It is missing from the page that teaches you to use it.
On localisation the news is good this time, which is worth saying because last week it was the opposite. The notice is translated into Italian and Romanian, with the same September 2026 date. When we checked the Travel campaign migration two days ago, the localised pages did not carry the announcement at all.
Who actually feels this
For most accounts, nothing visible happens. A restaurant advertising in one language, to one country, with ads and a landing page in that language, has one language set. Remove the box and nothing moves.
The accounts that feel it are the ones where language was not a description but a tool:
- Officially bilingual regions. Running two campaigns with different budgets and messages, split by language, is standard practice in South Tyrol, in Ticino, in Wales, in Catalonia.
- Tourism selling across borders. A lakeside hotel buying traffic in German and English alongside the local language used the setting to keep three market budgets apart.
- Exporters covering several countries from one account, where language was the cleanest way to avoid paying for clicks from the wrong market.
For all three the lever does not vanish, it moves. Google says so in its recommendations: "Focus on Ad and Landing Page Language: Ensure your ad creatives and landing pages are clearly structured in the intended languages." Translated into decisions: a single-language landing page per market is worth more than it was, and a page that mixes two languages is worth less.
What to check
- The language column in the Settings tab under Campaigns. One language everywhere means you are done.
- The actual language of the ad copy in any campaign you were splitting by language. From September that is the primary signal, and mixed copy in one ad group makes matching unpredictable.
- Each campaign's landing page. It should be in the language you want to reach, not a switcher page that defaults to one language for everyone.
- Anything that writes to the account. Whoever touches
CampaignCriterion.languageon Search campaigns needs telling now, not in late September. - Performance Max campaigns, where the setting still serves YouTube, Display, Discover and Gmail. Leave those alone.
What does not change
- Location targeting is untouched. Location and language are separate settings; only the second one goes, and only on some campaign types.
- Existing campaigns keep running. Google says they continue without disruption, simply ignoring the setting.
- YouTube, Display, Discover and Gmail inside Performance Max carry on as before.
- Nothing translates your ads. The system reads the language you wrote in.
- Existing criteria are not deleted. They stay readable through the API, just unused.
- Nothing is confirmed by a rollout. As of 14 August 2026 there is an announced date, "late September," and a precedent where an announced date was not kept.
Before and after, in a table
| Aspect | Until September 2026 | From late September 2026 |
|---|---|---|
| Search campaigns | You pick one or more languages | The setting is gone |
| What drives matching | The setting, plus Google's signals about the user | Ad and landing page language, plus signals about the user |
| Performance Max on Search | Uses the campaign setting | Ignores it, behaves like Search |
| Performance Max, other channels | Uses the campaign setting | Keeps using it, unchanged |
| API writes on Search | Allowed | OPERATION_NOT_PERMITTED_FOR_CONTEXT |
| API reads | Returns the criteria | Still returns them, but they are not used |
Source: "Google Ads language targeting changes starting September 2026," Google Ads Developer Blog, 13 August 2026, and the help page "About language targeting," read on 14 August 2026.
Glossary, two columns
| Term | What it means here |
|---|---|
| Language targeting | The setting that decides which users, by the language they understand, a campaign is eligible for |
| Campaign level | A setting that applies to a whole campaign rather than one ad group |
| AI Max for Search | The automatically matched variant of Search campaigns, which Google is migrating settings toward |
| Search portion of PMax | The share of a Performance Max campaign's ads that appear on Google Search |
| CampaignCriterion.language | The API field holding a campaign's language |
| Mutate | A write operation through the API: create, update or remove |
| Ad group prioritization | The mechanism choosing which group enters the auction when more than one is eligible |
Three thresholds: find yours
- One language across the account. Nothing to do. Just confirm ads and landing pages share that language, which is good practice anyway.
- Several languages, managed by hand. You have until late September to move the split out of the setting and into the content: one ad group per language, copy that does not mix, one landing page per language. No need to dismantle campaigns.
- Several languages, with automation writing through the API. You are the only case with a real technical deadline. Ask whoever wrote the script whether it sets
CampaignCriterion.languageon creation. If it does, that step has to come out before the error stops campaign builds.
If you are in the second or third case, the work is less dramatic than it sounds: it comes down to lining up ads and pages by language. How we look at an account before touching it, and what we do not promise, is on the Google Ads campaign management page.
Questions nobody has actually asked us
The announcement is a day old, so nobody has written to us about it. These are the questions someone running a two-language account would have after reading the post, plus the ones that come back every time Google retires a manual setting.
What is changing in Google Ads language targeting in September 2026?
From late September 2026 the campaign-level language targeting setting is removed from Search and AI Max for Search campaigns, and it stops applying to Performance Max ads shown on Google Search. Matching will run on the language of your ads and landing pages, together with Google's signals about the languages a user understands.
Has Google announced this before?
Yes. On 18 August 2025 a note on a help page said the setting would be removed from Search campaigns by the end of 2025. It was not. The announcement returned 360 days later with a different date and a wider scope that now includes Performance Max.
Do I need to change anything now?
Not unless you run automation. Google says existing campaigns will keep operating without disruption and the setting simply will not apply. The useful preparation is on ad copy and landing pages, not on account structure.
What error will my script get?
On a Search campaign, ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT, on any write that adds or updates the language criterion. Performance Max returns no error, because language can still be used on its other channels. Reads keep working in both cases.
How will Google choose the language instead of me?
The post points to AI-based ad group prioritization. We read the page describing that mechanism on 14 August 2026: it publishes a priority table, but the word "language" does not appear in the page body at all. The exact criterion is not documented there yet.
Should I clear my existing language criteria?
Google calls it optional, "for cleanliness." On Search it makes no difference, since they will not be applied. On Performance Max, clearing them changes behaviour on the other channels, so early cleanup there is a risk with no upside.
Is this the same as the AI Max auto-upgrade?
No, although both land in September 2026 and both were announced through developer channels. The AI Max upgrade changes which campaign type you are running. This change removes one setting inside campaign types you already have.
Will my ads start showing to the wrong audience?
Google's stated model is that ads match on the language they are written in, alongside its existing signals about the user. What we cannot tell you is how it resolves a tie between two eligible campaigns, because the page it points to for that does not cover language.
Does the removal reach Shopping, Display or Video campaigns?
The post names Search, AI Max for Search and Performance Max only. For Performance Max it is explicit that YouTube, Display, Discover and Gmail keep using the campaign-level setting.
What would you check first in a multilingual account this week?
The language column in the Settings tab, to size the problem. Then the actual copy language inside those campaigns, because that becomes the primary signal. Then who has API write access, which is the only part with a hard deadline.
Last updated: 14 August 2026. The announced date is "late September 2026" and is not yet confirmed by a rollout. Quotations come from "Google Ads language targeting changes starting September 2026" on the Google Ads Developer Blog, by Dora Sun, 13 August 2026, and from the help page "About language targeting," read on 14 August 2026 in English, Italian and Romanian. The 2025 announcement is quoted from Barry Schwartz's Search Engine Roundtable article of 18 August 2025, which reproduces the text of the notice as it stood. The count across thirteen documentation pages is our own measurement, made on 14 August 2026. We will update this page when the removal actually ships — or when the date moves again.
