Polski
Google Ads · News

Google Ads drops language targeting. Automation decides

From the end of September 2026 the campaign language setting stops working in Search, in AI Max and in Performance Max, but only on Search. The criteria will stay in the account, Google will simply stop using them. What decides the language of an ad, what the change does not touch and what to check before the deadline.

Sebastian Baryś
Sebastian Baryś
15 August 2026 18 min read

Introduction

English version of an article first published in Polish on 15 August 2026. Read the Polish original.

On 13 August 2026 Google announced on the Google Ads Developer Blog that from the end of September the campaign language setting will no longer decide who sees your ads on Search. If you run campaigns for several countries, or for several language versions of one site, this is one of the more serious changes in Google Ads this year.

One thing straight away, because the headlines can mislead. Google is not abolishing language matching. Matching stays and keeps working. What disappears is the manual switch on the advertiser's side, and the decision passes entirely to automation. It is a change of control, not of mechanism.

I break the announcement down into specifics: what stops working and when, how the system will choose the language of an ad, what happens to Performance Max, where the trade press oversimplifies and what to do with your account before the deadline. At the end I come back to the thread that interests me most: what this change does to the weight of properly built language versions of a site.

What you will learn:

  • What exactly stops working from the end of September 2026, and why that is not the same as the end of language matching
  • The five signals Google will use to decide the language of an ad, and which two of them stay in your hands
  • Why a single Performance Max campaign will run two language mechanisms at once from September
  • Three things that, despite the headlines, are not changing, including the myth of language exclusions
  • Which error the Google Ads API will return when you try to set a language, and what that means for your automations
  • What to prepare before the deadline, and why neglected language versions of a shop now hurt twice

What exactly is changing

Google gives the date in general terms: the end of September 2026, with no specific day. The Help Centre already carries a notice about the change: "Starting in September 2026, the way language targeting works is changing for Search campaigns". The scope is wider than the word "Search" alone suggests.

Where the setting stops working

In Search campaigns, including those with AI Max switched on, and in the part of Performance Max that serves ads on Search. In all of these, the language criterion will no longer be taken into account when an ad is assessed for auction eligibility.

What happens to existing campaigns

Nothing. Campaigns keep running and the saved language criteria stay in the account. Google simply stops using them. You can delete them, but only for tidiness, because restructuring the account is unnecessary.

What takes over the decision

Google's automation. It looks at the language of the ad and the landing page, and at signals about which languages the user understands. When several language variants are eligible for one auction, AI-based prioritisation decides which one is chosen.

What the change does not touch

Channels outside Search. Display, YouTube, Discover and Gmail still respect the language setting, also when they are part of Performance Max. Language settings never covered Shopping ads anyway.

One sentence from the announcement, quoted by Search Engine Land, is worth remembering word for word, because it settles the most common doubt: "Existing language criteria can remain but will no longer affect targeting and can optionally be removed". The criteria stay, they stop working, deleting them is voluntary.

Nine months behind schedule

This is not a fresh idea, but an old announcement that has finally been given a date. In August 2025 Google's help documentation said the language setting would disappear from Search campaigns by the end of 2025. Search Engine Land covered it on 18 August 2025 under a headline that today reads like a joke about deadlines: "Google Ads to end manual language targeting in Search campaigns".

December passed and the setting stayed. PPC Land puts the delay at roughly nine months, from the original target of December 2025 to the start in September 2026. By Google's standards, nothing unusual. What is more interesting is that the scope of the change grew in the meantime.

August 2025

First announcement

  • deadline: end of 2025
  • scope: Search campaigns only
  • channel: a note in the help documentation

August 2026

Announcement with a date

  • deadline: end of September 2026
  • scope: Search, AI Max and Search within PMax
  • channel: the developer blog and a post by the Ads Product Liaison
The same change, two announcements. In between, AI Max and Search within Performance Max were added.

The practical conclusion is simple. There is no point turning your account upside down this week, but do not count on another postponement either. Google's deadlines can move, its direction never does. Anyone who put off preparations in 2025 because "they will probably push it back" was right and gained a year. The same move pays off less often the second time.

How Google will choose the language

After the rollout, five signals will decide whether an ad is eligible to show at all. Two of them you set yourself: the language of the ad text and the language of the landing page. The other three sit on Google's side, and the help documentation lists them explicitly as "search term language, the user's language settings, and preferences": the language of the query typed in, the user's language settings and their other preferences.

Signals on your side

Language of the ad text

headlines, descriptions, assets, extensions

Language of the landing page

the content at the URL the ad leads to

Signals on Google's side

Language of the query

what the user actually typed

Languages the user understands

account settings and activity history

Other context and preferences

signals Google does not list

Two signals you set yourself, three you get from the system. After September that is all the control you have over language on Search.

For years Google's documentation has illustrated this with a user called Pat. She may see ads in two languages because "her activity on Google strongly suggests she understands English too": some of her queries are in English. This mechanism has existed for a long time. The only new part is that the campaign setting no longer takes precedence over it.

The most important sentence of the whole change

The language of the query does not have to be identical to the language of the ad. Search Engine Journal quotes Google verbatim: "The language of the query doesn't have to match the language of the ad". If someone searches in English and the system judges that they understand French, an ad in French can be eligible. Google also says it gives priority to the variant in the language of the query, provided one exists and the intent is clear.

Performance Max: two mechanisms in one campaign

In Performance Max the change does not cover the whole campaign, only part of it. That is the most awkward consequence of the entire announcement. The language setting does not disappear from the interface, nor does it stop mattering. It stops mattering only where ads are served on Search.

Search

setting ignored

The language of the ad and the landing page, plus Google's signals about the user

YouTube

setting applies

The campaign language setting still steers delivery

Display

setting applies

The campaign language setting still steers delivery

Discover

setting applies

The campaign language setting still steers delivery

Gmail

setting applies

The campaign language setting still steers delivery

Shopping ads

not applicable

Language settings never affected delivery anyway

One Performance Max campaign, two parallel language mechanisms from the end of September 2026.

In practice it comes down to this: if after the rollout you see Performance Max traffic from a market you did not expect, the first question is not "what did I break in the settings" but "which channel did it come from". From September, delivery on YouTube and on Search within a single campaign will follow different rules, and the aggregate report will not separate them.

If you are still getting to grips with this campaign type, I described how it works in more detail in my article on how to tame Performance Max. I go deeper into AI Max and ads in AI answers in the piece on ads in AI Mode.

Three things that are not changing

Alongside the announcement came a clarification from Ginny Marvin, Ads Product Liaison at Google. Three points that press coverage usually leaves out. Each corrects a different misunderstanding.

1. Language exclusions do not exist and never did

The quote is unambiguous: exclusions "are already not supported (e.g. leaving a language unselected doesn't mean it's excluded). That's not changing". This is not the announcement of a change, but the correction of a myth that has circulated in the market for years.

2. Google does not translate creatives

This also applies to text customisation in AI Max: "Google does not translate ad creatives". An ad in a given language will appear only if someone wrote it in that language. For companies that prepare copy separately for each market, especially with clauses required by law, this is often more important news than the removal of the setting itself.

3. Reporting is not being rebuilt

The structure of campaign performance data stays as it is. Your reports, rules and dashboards will keep working. The change will not rearrange columns or dimensions.

The first point deserves a moment of its own, because it concerns a distinction that is easy to trip over. The language setting told the system who the ad is allowed to reach: people who, according to Google, understand at least one of the selected languages. It did not say who to cut off. Leaving English unselected never blocked delivery to someone who understands English and, as it happens, Polish too.

So if someone tells themselves today that their campaign "does not pick up English queries because English is not selected", they are wrong. And they have been wrong for years, regardless of the September change.

Watch out for a quiet swap of meanings around reporting

"Reporting is not being rebuilt" is not the same as "you will get a language report". Google has not announced any new dimension that would show which language your ads were actually served in. The old columns work as they did, and there is no insight into the distribution of delivery by language. You did not need it before, because you set the language yourself. Now you neither set it nor see it.

What about the API and scripts

It is no accident that the announcement appeared on the developer blog. For integrations this change is harder-edged than for the interface. Reading stays: the language criteria of Search campaigns will still be returned in queries. Writing stops working.

google ads api ▸ from September 2026

reading the language criterion of a Search campaign

✓ works, the query returns the saved criteria

adding or changing the language criterion of a Search campaign

✗ ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT▮

Every operation that adds or changes the language of a Search campaign will end with the error ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. If you have anything that creates campaigns from a template (a Google Ads script, an API integration, a bulk upload tool or a campaign generator fed from a spreadsheet), that is where the change will reach you first.

Google's recommendation is simply to stop setting language criteria in new Search campaigns. I would add one sentence to that: do it before the rollout, not after. A script that falls over while creating a campaign is a silent failure. You will not see an alert in the interface, only a missing campaign where one was supposed to appear. Things like that usually surface a week later, at reporting time.

How it will work in the auction

Take a typical setup: separate ads and landing pages in Polish, English and German, each in its own campaign. On the other side is a user who uses Google in English, spends time in Poland, has English and German queries in their history, and now types a query in German.

Today

The DE campaign has German selected, the EN campaign has English.

The ad is eligible for people who, according to Google, understand at least one of the selected languages, regardless of the language of the query itself.

The campaign language criterion is one of the conditions for entering the auction.

From the end of September

The campaign criterion is not taken into account.

Google looks at the language of the ad and the landing page, and at which languages this particular user understands.

When several variants are eligible, AI-based prioritisation makes the choice, with stated priority for the language of the query.

The same auction, two regimes. The difference is not that matching becomes looser, but that your layer of control disappears.

Let me be precise here, because it is easy to overstate things in the other direction. Language matching in Google was never strict. The system has always shown ads to people who, according to its data, understand a given language, even if they happened to be searching in another. The campaign setting was therefore a filter on your side, not a guarantee of a match with the language of the query. What disappears is the filter, not the precision, because precision in the sense of "a German ad only for a German query" was never there.

AI Max is a separate case. Google has confirmed that if a campaign contains an ad in French, it can appear for an English query, as long as the system decides the user understands French. With automatically generated assets, then, it is better to know exactly what the system is allowed to create on your behalf.

Where it will hurt

The most exposed accounts are those where the language setting was treated as a real limiter on delivery. A role which, as we now know, it never played. Beyond that, there are several situations worth checking in your own account.

  • Ad groups and landing pages with mixed languages. An English ad leading to a Polish page, or several languages in one set of assets, gives the system contradictory signals exactly where it makes its decision from September. Until now that kind of mess was a matter of message quality. Now it is the main material automation bases its decision on.
  • Brand queries in several countries. A brand name usually does not reveal a language. For such a query Google will lean more heavily on its own data about the user than on anything that comes from you. This is the most predictable place where the split between markets will shift.
  • AI Max and automatically created assets. A system that picks the content itself and a system that picks the language itself. Two levels of automation at once. If you do not have a solid landing page in a given language, do not hand automation material that lets it send traffic there.
  • Industries with documentation requirements. After the announcement, advertisers from the insurance industry raised a compliance question: how to demonstrate equal access to ads in English and Spanish when delivery is controlled by automation. Google's answer, "providing ads in both English and Spanish signals the advertiser's intent", is about the advertiser's intent, not about the ad actually being delivered. As I mentioned, no language reporting has been announced so far.
  • Interpreting the data after the rollout. The change may shift the distribution of queries, countries, conversions and costs. A falling CPA in one market and a rising one in another does not have to mean you broke something. It may mean that the rules of auction eligibility changed. Without data from before the change you will not be able to tell.

What to do before the end of September

You have about six weeks. For a change that does not require restructuring the account, that is a lot. It is more than enough to calmly take a baseline export before a "before and after" comparison stops being possible.

September 2026 is not a single change

For the same month Google has also scheduled the automatic switch-over for automatically created assets and for campaign-level broad match, and after September you will no longer be able to create a new Dynamic Search Ads (DSA) campaign. The migration of DSA to AI Max itself has been pushed back to February 2027, but even so, when you compare October with August you will see the effect of several changes at once and you will not be able to separate them after the fact. All the more reason to take the export now and note next to it what changed in the account and when. I laid out the whole timetable in my article on ads in AI Mode and AI Max.

1. Take a baseline export

Save the results from the last 8 to 12 weeks: cost, conversions, CPA and ROAS, search terms, countries, devices and which landing page collected the traffic. Without it, after the rollout you will not be able to tell seasonality from the effect of automatic matching. This is the only item on the list that cannot be made up for later.

2. Review the language of your creatives

In every ad group, keep one language across headlines, descriptions, assets and extensions. Mixing languages "for reach" used to be plain sloppiness. Now it is a signal the system bases its delivery decision on.

3. Match the landing page to the creative

An ad in German leads to a full German page at its own URL. Not to the Polish version with a language switcher, not to a general English landing page, not to a page translated by a script after it loads. This is the most concrete thing you can do for the quality of matching.

4. Check your automations

Scripts, API integrations, spreadsheet-based campaign generators, agency tools. Anything that sets a language when creating a Search campaign will start returning an error. Better to check it now, calmly, than to find out from a missing campaign in October.

5. Set your rules for AI Max

Decide whether you allow automatically created assets and text customisation. Remember that Google does not translate creatives. An ad in a given language will appear only if you supply it yourself or let the system generate it.

6. Do not delete your language structures

Separate campaigns or ad groups for each language still give you budget, bids, clear reporting and room for testing. The change takes away only one of their functions: auction eligibility. The rest stays. Removing the saved criteria is optional too.

7. Plan how you will monitor the first weeks

After the rollout, look above all at search terms, the share of each country, cost and conversions, separately for each market and not as an account-level total. The total will mask exactly what you are looking for. You will have to keep an eye on landing page language in your analytics anyway, because Google Ads will not show it to you.

What it means for SEO and hreflang

I will start with a caveat, to avoid over-interpretation. This is not a change to the organic algorithm and it does not concern the hreflang attribute. Google Ads and organic search are separate systems, and hreflang does not affect ad delivery. Nobody has announced that and there is no reason to suggest it.

Something else is changing, and that is the interesting part. Until now the language of the landing page was a matter of hygiene in a campaign. It influenced landing page experience and, through it, indirectly the Quality Score. From the end of September it is promoted to one of the two signals you can control at all. The same work that is done for international SEO starts working for the results of paid campaigns as well.

A language version without its own URL does not exist for Google

If the German version of a shop sits at the same URL as the Polish one and is swapped in by a switcher or a script, Google has nothing to read. Neither as a language signal when assessing ad eligibility, nor as a separate page in the index. The same gap, just seen from two sides.

The minimum you need for this change to work in your favour has been known for years and is not exotic at all. Part of it works on both sides, such as separate URLs and content that is actually translated, and part only organically, such as hreflang. The work is shared, though, so there is no point splitting it into two projects:

  • separate, indexable URLs for each language version, not a session parameter or content swapped in the browser,
  • correct, reciprocal hreflang pairs with a self-reference,
  • content that is actually translated, not just the menu, header and footer,
  • local currency, delivery terms, contact details and calls to action,
  • one language along the whole path: keyword, ad, landing page, conversion.

What I am most curious about is whether this will change the approach of those shops whose hreflang tags are simply neglected. As long as it was "an SEO topic", it could be put off indefinitely. There is always a more urgent priority than tags nobody in the company can see.

Now the same mess stops being an abstraction and starts to concern a budget that is spent every month. I suspect that for more than one management board, the argument "Google will choose the language of your ad by itself, based on the page you send people to" will work better than five years of audits.

You can see it even in search data, though not in volumes, only in bids. According to Senuto (a Polish SEO tool), the query "hreflangs" gets 390 searches a month on Google in Poland, and "hreflang" gets 260. So the traffic is there, but across the top forty queries in this group the average CPC is 0.12 PLN, because apart from the two main ones none has any bid at all. Nobody is bidding, because it is hard to sell anything on a query like that. Meanwhile, for the query "sprzedaż za granicę" (selling abroad), with a volume of just 140 searches, a click costs the advertiser 6.26 PLN on average. Somebody pays for expansion. Nobody pays for its foundation.

I cover language versions and technical order in a shop in more depth as part of SEO for online shops. And if you are wondering how to split a budget between channels in the first place, I described that in my article on choosing between SEO and Google Ads.

FAQ: frequently asked questions

When exactly does the campaign language setting go away?

Google says the end of September 2026, without a specific day. The change was announced on 13 August 2026 on the Google Ads Developer Blog, and the Help Centre mentions September 2026. Assume that in the last week of the month the setting will stop affecting ad serving in Search campaigns.

Do I have to remove language criteria from my campaigns?

No. Google states plainly that existing criteria can remain and will simply stop being applied, and that removing them is optional, a matter of tidiness. No account restructuring is required. Separate campaigns or ad groups for each language still make sense: budget, bids, messaging and reporting.

Does the change apply to Performance Max?

Partly. In Performance Max the language setting stops working only where ads are served on Search. The mechanism there will be the same as in Search campaigns. On YouTube, Display, Discover and Gmail the selected languages still steer delivery. Language settings never affected Shopping ads anyway.

Can I exclude a language in Google Ads?

No, and that option never existed. It is the most common misunderstanding about this setting. Leaving a language unselected never meant excluding it. This is confirmed by Ginny Marvin, Ads Product Liaison at Google, in a clarification published alongside the announcement: language exclusions "are already not supported" and "that's not changing".

Will Google translate my ads into other languages?

No. Google does not translate ad creatives, and that includes text customisation in AI Max. An ad can appear in a given language only if someone wrote it in that language. This matters most in industries where content with legal requirements is prepared separately for each market.

Should I merge my language campaigns into one?

There is no need to, and usually no reason either. Google confirms that restructuring is not required. Separate campaigns still give you control over budget, bids and clear reporting. Only one layer disappears: language as a criterion for auction eligibility.

What will happen to my script or API integration?

Reading the language criteria of Search campaigns will still work, queries will return that data. Writing changes: every attempt to add or modify the language of a Search campaign will end with the error ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. If you have automation that creates campaigns from a template, check it before the rollout, not after the first failed run.

Will I get a report showing which language my ads were served in?

As of the publication date of this article, Google has not announced any new language reporting. It has only said that the existing structure of campaign performance data will not be rebuilt. Those are two different things. Old reports work as they did, but there is no insight into the actual distribution of delivery by language.

Worth remembering

  • From the end of September 2026 the campaign language setting stops working in Search, in AI Max and in the part of Performance Max that serves ads on Search. On YouTube, Display, Discover and Gmail it keeps working.
  • Language criteria will stay in the account and remain visible. Google will simply stop using them when deciding auction eligibility. Removing them is optional and restructuring the account is unnecessary.
  • Five signals will decide: the language of the ad, the language of the landing page, the language of the query, the user's language settings and their other preferences. The first two depend on you, the other three do not.
  • The language of the query does not have to match the language of the ad. With multilingual users and brand queries this will happen more often than you assume.
  • Language exclusions do not exist and never did. Leaving a language unselected never meant excluding it. Google is correcting a myth here, not introducing a change.
  • Google does not translate ad creatives, neither in classic Search nor with text customisation in AI Max. An ad in a given language exists only if you write it yourself.
  • The change raises the importance of the landing page. If a language version has no indexable URL of its own, Google has nothing to read, neither for ads nor for organic results.

Summary

Google is taking one switch away from the advertiser and handing its role to automation. It is another step along the same road that Performance Max and AI Max are on. Campaigns will not stop working, accounts do not need to be rebuilt, and the saved language criteria can safely stay where they are.

You used to tell Google: "this campaign should reach people who speak language X". From the end of September all you can do is show it good, separate variants X, Y and Z, and then check who its automation assigned them to, and in which language.

The biggest problem is not the matching itself, because that was never fully yours anyway. The problem is the asymmetry. There was less control than it seemed, but what remained is now disappearing entirely, and you get no insight in return into how automation uses it. As long as there is no reporting by language, the only place where you really set anything is your creatives and landing pages.

Rather than wait for September, I would start with two things. The baseline export, because after the rollout nobody will be able to take it retrospectively. And a review of how well each ad matches its landing page in every language. The first takes an afternoon. The second, if the shop does not have properly separated language versions, will take much longer, because it is not a checklist task but work on the site itself. Better to find that out now than from the October report.

And will the change itself be good for campaigns? Time will tell. I have one suspicion, and I will gladly withdraw it if it does not hold. A language cannot be excluded and never could be, so the job of policing who sees the ad will move to where exclusions are allowed: negative keyword lists, locations, audiences. I will not be surprised if in six months the balance looks like this: automation added reach, and advertisers gained more entries on their exclusion lists. We have been through this before with Performance Max and with broad match.

Running campaigns in several markets?

I will check whether your creatives and landing pages give Google a clear language signal, before automation makes the call for you.

See Google Ads campaigns

How this text was written

I will not pretend it was written entirely by hand, by candlelight. For the research, the proofreading and the code of this page I used a language model. It is a good tool for digging through documentation and catching the typos you no longer see on the third read of your own text. The English version was also prepared with a model, from my Polish original.

What the model did not do: it did not choose the topic, form the arguments or decide what this data means for your site. That stays with me, as does the last word on what goes into the text and what comes out of it.

Where the model helped

  • digging through sources and organising data
  • proofreading and the English version of the text
  • code, page layout and infographics

What stays with me

  • the choice of topic and what is worth saying about it
  • the arguments, the reading of the data and the conclusions
  • fact-checking and the decision on what goes into the text
Sebastian Baryś – freelance SEO specialist

Written by

Sebastian Baryś

Freelance SEO specialist · Częstochowa, Poland, and remote

I started when nobody had dreamt of Core Web Vitals and rankings were checked by hand. Today I work on making companies visible not only in Google, but wherever people ask questions. I write only about things I check myself in client projects.

SEOGoogle AdsTechnical SEOSEO in the AI era

Let’s talk about multi-market campaigns.

I will help you put your creatives, landing pages and account structure in order, so that Google's automation works in your favour.

Get in touch