Google Ads Language Targeting Removal (September 2026): What Small Advertisers Should Know Before the Setting Disappears

On August 14, 2026, Ginny Marvin, Google’s Ads Product Liaison, posted on LinkedIn that campaign-level language targeting will be removed from Search and Performance Max campaigns starting in September 2026. Her framing — “I know it sounds like a big shift, but it really isn’t” — is why most small advertisers will skim it and move on.

Skimming is the mistake. The removal is the boring half. Almost nobody is discussing the second change shipping alongside it: Google will begin prioritizing the ad and landing page whose language matches the search term. That is not a deletion. That is a new serving rule switching on.

What exactly is Google removing from Search campaigns in September 2026?

Google is removing the campaign-level language dropdown from Search, AI Max for Search, and Performance Max. After the change, Search ads are matched using the language of your ad creative and landing page, the language of the search term, and the user’s own language settings and history.

Search Engine Land’s Anu Adegbola reported the rollout on August 13, 2026 and put the timing at “late September”; PPC Land’s Luis Rijo covered Marvin’s post on August 14. Both agree: the setting goes, matching continues, no action required.

Performance Max gets a split. On Google Search, PMax now behaves like a standard Search campaign — your language selection stops applying. Those settings keep steering YouTube, Display, Discover and Gmail. Shopping ads inside PMax were never governed by language settings and still aren’t. One campaign type, two language regimes, depending on the surface.

Why does the “it really isn’t a big shift” framing not hold up?

Scope. Google’s help documentation in August 2025 said the setting would leave Search campaigns by the end of 2025, and explicitly said non-Search campaign functionality would not change. Performance Max is a non-Search campaign type, and it is now named in scope. If you filed PMax under “not affected,” that filing is wrong.

The prioritization change. Today, when a bilingual user could understand two of your creatives, the tiebreaker is their inferred preferred language. From September, an unambiguous query language wins the tiebreak instead. Google presents this as “better control” — better in the sense that a thermostat you cannot see is better than one you can.

The calendar collision. September 1, 2026 is also when automatically created assets and campaign-level broad match convert to AI Max, confirmed in a Google email dated August 5, 2026. Two structural changes in one four-week window means any September movement has two plausible platform-side causes, and a solo operator cannot separate them.

How does the new language matching actually work?

Three checks: one switched off, one switched on.

• Comprehension — can this user read the language of your ad and landing page? Active today, stays active.
• Campaign setting — does your configured language match a language the user has? Active today, switched off in September.
• Prioritization — when a user can read more than one of your variants, which serves? For queries with no clear language (brand names) Google keeps using the user’s preferred language. For queries with a clear language, it now prioritizes the matching creative — switched on in September.

The load-bearing definition is “user language.” Per Google’s own graphic it includes any language the user has set, interacted with regularly, or searched in — a far wider net than an interface preference. A Toronto homeowner whose phone is set to English but who searches in French twice a month is eligible for both your creatives, and from September the query decides which shows.

That mechanism predicts cases nobody has covered. One English campaign in Miami: nothing visible changes, because a single creative means prioritization never fires. Parallel English and Spanish campaigns: volume redistributes. An English campaign whose landing page auto-redirects Spanish-browser users to a Spanish page: the ad language Google matches on no longer describes the page it resolves to, and Google does not translate creative, so nothing patches that gap.

Does this change my CPA, or something else?

Probably not your CPA. Almost certainly your reach composition. Read it through direct response and the verdict lands close to Google’s: the setting was one input among several, the others remain, cost per acquisition should hold. Direct response asks whether the money still works, and it probably does.

Read it through brand-building and mental availability — the Ehrenberg-Bass tradition arguing growth comes from being noticeable to more category buyers rather than converting the same ones harder — and the verdict changes. This does not move price. It moves who is in the room. Reallocating impressions between your English and Spanish creative by query language redraws who ever encounters your brand, in a direction you no longer set.

That lens is right for one concrete reason: you can hold CPA flat while the pool shrinks. If prioritization concentrates delivery onto whichever creative is better written, conversion rate holds while the other language’s impression share erodes. A CPA dashboard shows nothing. Impression share by language shows everything.

Who actually loses money here?

The freelancer running eight accounts, and anyone whose second language was carrying the cheaper volume.

Take an agency-of-one running paid search for eight home-services clients across Houston and San Antonio. The standard build is paired campaigns, one English and one Spanish, because Spanish-language CPCs in those metros have historically cleared at a discount. Say the Spanish campaign runs $900/month at a $38 cost per lead and the English campaign $1,600/month at $61. If the Spanish side loses even 25% of its impression share to the English creative, roughly six leads a month reprice from $38 to $61 — about $140 per client, per month. Across eight accounts that is $1,100 a month, with no line item naming it.

The B2B SaaS founder in Montreal has the inverse problem: English creative, one campaign, no French variant. French-language queries from prospects who read English fine become less likely to surface an English ad when a French-writing competitor is bidding. They lose eligibility they never knew they had.

How should a one-to-three person team prepare before late September?

Seven steps, all doable in one working week with the Google Ads interface and a spreadsheet.

1. Take a language-segmented baseline now. Pull impressions, clicks, conversions and impression share for the last 60 days by campaign. This is the only “before” snapshot you get.
2. Audit ad-to-landing-page language consistency. Geo-redirects, browser-language auto-switching and translation widgets all create mismatches, and a mismatch is now a signal working against you.
3. Stop treating an unselected language as an exclusion. Marvin restated this explicitly: leaving a language unselected does not exclude it, and exclusions remain unsupported. If your account was built on that assumption, it is about to become unfixable.
4. Keep your paired language campaigns. Google confirmed single-language structures continue to function as they do now. Do not consolidate — the structure is still how you read the numbers, even once it stops driving targeting.
5. Sharpen the weaker creative. The ad’s own language is now a primary matching signal, so the campaign with vague, translated-sounding copy loses the tiebreak. If your Spanish ads are machine-translated English, rewrite them natively this month.
6. Fix your API calls if you run scripts. From rollout, adding or updating CampaignCriterion.language on a Search campaign returns ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. PMax will not throw the same error, since language still governs its non-Search channels. Test any bulk-creation script before September.
7. Set one reminder for October 7. Compare September against your baseline — impression share by language first, CPA second. Do not act on week-one data; the AI Max conversions contaminate that window.

What dates should be on the calendar right now?

• August 13, 2026 — Google stopped accepting new campaign-level broad match configurations.
• September 1, 2026 — Automatically created assets and campaign-level broad match convert to AI Max, per Google’s August 5 advertiser email. Our walkthrough of the August 17 Target CPA enforcement covers the bidding side of the same wave.
• Late September 2026 — Language targeting removed from Search, AI Max for Search and PMax; search-term-language prioritization activates.
• October 2026 — Q4 CPC inflation begins in earnest: the worst month to diagnose an unexplained volume shift, and the argument for baselining now.
• February 2027 — Dynamic Search Ads automatic migration to AI Max, pushed back from September 2026 on June 13, 2026.

One more piece of context: Lunio published a retail study on August 12, 2026 reporting 72% more invalid traffic on AI Max campaigns. That is a third-party finding, not a Google figure, and retail-specific — but if your account converts on September 1 and your language setting vanishes weeks later, invalid-traffic monitoring belongs on the September list too. campaignpress.ai can carry some of that watching; the baseline in step one is free and matters more.

Frequently asked questions

Do I need to restructure my account before September?

No. Google says no action is required, and separate single-language campaigns keep working as they do now. Do the cheap defensive work instead: baseline your numbers by language, verify each ad’s language matches its landing page, rewrite machine-translated creative.

Will Google translate my ads into other languages?

No. Marvin stated directly that Google does not translate ad creatives, and that AI Max text customization — which generates headlines and descriptions from your landing page and existing assets — does not render them into another language. To appear in a second language you still write that creative and build that page yourself.

Does this affect my Performance Max campaigns or not?

Partly, and the split is the confusing bit. For PMax ads on Google Search, the campaign language setting stops applying and matching works like standard Search. For PMax delivery on YouTube, Display, Discover and Gmail, your language settings still apply. Shopping ads within PMax were never governed by language settings and remain unaffected.

Can I still exclude a language I don’t want to serve in?

You never could. Language exclusions have never been supported in Google Ads, and leaving a language unselected has never excluded it — a misconception Google named as one reason the setting is being retired. Unchanged in September. Your only real language control is the language of your creative and your landing page.