Google Ads Removes Language Targeting: What Changes in September 2026

Google has announced that from late September 2026 it will remove the campaign-level language targeting setting from Search and AI Max for Search campaigns. The announcement comes from the Google Ads API team and sits in the Google Ads Developers Blog dated August 14, 2026. Instead of the manual language setting, Google will match ads automatically based on the language of your ads.

Most write-ups will turn this into a panic headline. The honest version is calmer: if you run a single-language account that serves English ads to English speakers, almost nothing changes. Google simply takes over what you used to set by hand. It gets interesting at the edges, and those edges are what I’ll name precisely here.

If you got this change by email or inside your account, you’re in the right place:

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. Effective late September 2026.

What exactly changes?

The core is a shift from a manual criterion to an automatic signal. Until now, you set at campaign level which languages a user had to prefer for your ad to be eligible at all. After the cutover, that control disappears on Search, and Google infers the language from your ads instead. On Performance Max, the setting is treated differently by placement:

Campaign type / placement	Language setting from late Sept 2026
Search	Removed, matching by ad language
AI Max for Search	Removed, matching by ad language
Performance Max on Google Search	Removed, same as Search
Performance Max on YouTube, Display, Discover, Gmail	Kept, still guides your audience

Put differently: on Performance Max you lose language control on 1 of 5 placements, and keep it on 4 of 5. When several eligible campaigns exist in an account, Google’s AI-based ad group prioritization decides the most relevant ad language.

When, and why is Google doing this?

The change was announced on August 14, 2026 and takes effect in late September 2026. It’s part of the same automation wave that keeps trading manual dials for inferred signals, the same direction as Google moving Display controls into Demand Gen. The official reason is simplification while keeping ad quality high. In practice that means fewer levers for you and more decisions made by the system, which now reads the language from your ad copy, landing page and user signals.

Does this even affect you?

For most accounts the answer is: barely. The change is only felt in clearly defined cases.

Situation	Affected?
English ads, English landing page, English-speaking audience	No, Google matches it automatically
One language in the account	No
Multilingual account (e.g. English plus Spanish in separate campaigns)	Yes, clean ad language matters more
Ad language different from audience (e.g. English copy aimed at a non-English market)	Yes, the signal no longer fits the audience
Search campaign deliberately steered via the language setting	Yes, that lever is gone

An honest look at my own practice: none of the Search campaigns I manage run on multilingual language targeting. One language, one audience, done. For those accounts the cutover is a date without an action. That lines up with the keyword research on this topic (as of August 31, 2026): 0 of 1,600 checked terms showed meaningful search volume around language targeting. It’s a technical detail update, not a mass-market topic, which is exactly why most people ignore it even though it matters for multilingual setups.

What should you do now?

For single-language accounts: nothing, other than noting the date in your reporting. For everyone else the list is short and concrete:

1. Align ad language and landing page. After the cutover, ad language is the primary signal. English ads belong on English landing pages, Spanish on Spanish. Mixing languages inside one campaign becomes a risk.
2. Create new Search campaigns without language criteria. The setting no longer applies, so skip the step.
3. Split multilingual accounts cleanly by language. One campaign per language, with unambiguous ad and landing page language, so Google’s automatic matching doesn’t have to guess.
4. API users: stop mutating CampaignCriterion.language on Search. Those calls will throw an OPERATION_NOT_PERMITTED_FOR_CONTEXT error after the cutover. Existing language criteria are still returned in queries, but no longer used for targeting. On Performance Max there’s no error, because language still counts on the other placements.
5. Note the date. If you see traffic shifts on multilingual setups after late September, check this date first before hunting for the cause somewhere else.

Because language is now inferred from your ad and landing page, it’s worth a second look at how match types actually match in 2026, since both changes move control away from the manual criterion toward an inferred signal, and the quality of your ad copy carries more weight than it used to.

What’s the bigger pattern?

Step back for a second. Language targeting is a small dial on its own. The direction is what matters. Google keeps retiring the manual controls you used to steer with hard, and replaces them with signals the system reads from your own assets. Ad copy, landing page and user behavior decide now, not a checkbox.

For you as an advertiser that means the quality of your inputs matters more, because they increasingly drive the targeting. A cleanly separated, language-clear account structure is no longer a tidiness luxury. It’s the mechanism Google uses to decide who sees your ad. Keep your ads and landing pages clearly in the target language and you hand the system a clean signal. Mix them, and you leave the decision to the automation’s guesswork.

FAQ

Do I need to change my existing English campaigns?

No, as long as they serve English ads to an English-speaking audience. Google will infer the language from your ads, and the result is the same as before. You only need to act on multilingual accounts, or where your ad language doesn’t match the audience.

What happens to my existing language criteria after the cutover?

They stay in the account technically and are still returned in API queries, but they’re no longer used for targeting. You can remove them for cleanliness, but on Search you don’t have to, because they simply have no effect anymore.

Does the change apply to Performance Max too?

Partly. On Google Search, Performance Max behaves like a Search campaign after the cutover, and the language setting drops there. On YouTube, Display, Discover and Gmail the setting stays and keeps guiding who sees your ads.

I run English ads for a non-English market. What does this mean for me?

That’s the case where you should act. If language is inferred from the ad, English copy signals an English-speaking audience to the system. Check whether ad language and actual audience line up, and split into separate, language-clear campaigns if needed.

Does anything change in the Google Ads API for other campaign types?

The error applies to Search campaigns: mutates to CampaignCriterion.language throw OPERATION_NOT_PERMITTED_FOR_CONTEXT there. On Performance Max no error is thrown, because language is still used on the remaining placements.

Your next steps

For single-language accounts it’s a one-liner: note the date, otherwise do nothing. For multilingual or off-language setups, it’s worth a quick check before the end of September that ad language and audience line up and that new campaigns are created without language criteria.

If you’re not sure whether your account falls into the affected cases, or whether your structure is clean enough for the increasingly signal-driven matching, book a free intro call. So you come in with the right expectation: in the intro call we clarify where your account stands and whether a closer review is worth it. The review itself is then the first step of working together. For the bigger picture on where an outside look pays off, see when a Google Ads audit is worth it.