Google Ads Removed Language Targeting: What Multilingual D2C Brands Do Now

The setting you relied on is gone

If you opened a Search campaign in the last couple of weeks and went looking for the language targeting dropdown, you may have found it missing. That's not a bug. On August 14, 2026, Google's Ads Product Liaison Ginny Marvin confirmed that campaign-level language targeting is being removed from Search campaigns, with the rollout landing in late September — roughly nine months after Google's original end-of-2025 deadline for the change. Her framing was reassuring: "I know it sounds like a big shift, but it really isn't."

For most advertisers in a single-language market, she's right. For Indian D2C brands running a messy, beautiful mix of English, Hindi, Hinglish, and regional-language campaigns, it's worth understanding exactly what moved — because the setting you used to lean on for control is now doing its job somewhere you can't see.

What exactly changed

The setting is removed, not replaced with another setting

The campaign-level language option is gone from Search and from AI Max for Search. In Performance Max, only the Google Search portion loses it — the other channels still read language targeting as before. If you manage campaigns through the Google Ads API, Google's guidance is to stop sending language criteria when you create or update Search campaigns; existing criteria can stay but won't affect Search targeting anymore.

How matching works now

Instead of comparing your campaign's configured language against the user, Google now decides whether to show your ad based on two things working together: the language of your ad creative and landing page, and Google's own signals about which languages a given user understands. Those signals include the language of the query, the user's account settings, and AI-derived guesses about their comprehension.

When a user understands several eligible languages, Google's ad group prioritization picks the best match. For a query in a clear language, it leans toward the ad and landing page written in that language. For an ambiguous query — a brand name that reads the same across languages — it falls back to the user's preferred language. The query itself no longer has to match the ad's language for your ad to be eligible.

One thing that didn't change

Google does not translate your ad creative. AI Max's text customization rewrites and reshuffles your copy, but it does not turn English into Tamil. The words you write, and the language of the page you send people to, now carry the full weight of telling Google who this ad is for.

Why this hits Indian campaigns harder than most

India isn't a single-language market, and that's the whole reason this feels bigger here than it did in, say, the US. A typical D2C brand in India might run a polished English campaign for metro buyers, a Hindi campaign for the Hindi belt, and a couple of regional pushes during festive season. The old setting let you draw a clean line around each.

Here's the reassuring part: Google's logic actually leans in your favour for the common case. A searcher typing a clearly Hindi query should more reliably pull your Hindi creative, even if they're bilingual, because Google now prefers the ad that matches the query's language. The messy part is the bilingual searcher with an ambiguous or brand-name query — Google will use its own read of their preferred language, and you have no dial to overrule it.

So the practical shift isn't "rebuild everything." It's "your copy and your landing page are now your targeting." A half-English, half-Hindi landing page sends a muddy signal. A campaign whose ad copy doesn't clearly commit to one language gives Google less to work with. Clarity in the creative is no longer just good practice — it's the control mechanism.

Before and after: what you actually need to check

A worked example: one brand, three campaigns

Picture a skincare brand running three Search campaigns — a polished English one for metro buyers, a Hindi campaign for North India, and a Tamil push for a festive regional launch. Under the old system, each had its language set at the campaign level, and that setting did the sorting.

Now the sorting comes from the creative. The English campaign's ads and landing page are in English, so an English query from a user Google reads as an English speaker pulls that campaign — unchanged in practice. The Hindi campaign works the same way, as long as both the ad copy and the landing page are genuinely in Hindi, not English ads pointing at a Hindi page or the reverse. The Tamil campaign is where discipline pays off: if its landing page is half-English because someone rushed the festive build, Google gets a mixed signal about who the page is for, and matching gets fuzzier.

The bilingual Mumbai user searching your brand name in English is the genuine edge case. Google will decide, from its own read of that user, which campaign's ad to prefer — and you no longer hold a lever to force it. For a brand query that's usually fine; the user knows your brand either way. The lesson is to stop worrying about the edges you can't control and fix the signals you can: one language per campaign, matched copy and page, no mixing.

Festive timing makes this sharper. If you're spinning up regional-language campaigns for a Diwali or regional-festival push, build them clean from the start rather than cloning an English campaign and swapping a few headlines. A cloned campaign that still points at an English landing page, or mixes English headlines with Hindi descriptions, now sends exactly the muddy signal that costs you relevance in the one month you can least afford it. Five minutes checking copy-and-page language per campaign at build time saves you guessing why a regional push underdelivered in week two.

What to do this month

Don't restructure in a panic — Google explicitly said you don't need to, and tearing apart working campaigns in the middle of festive season is how you lose a quarter. Instead, run a short audit. Confirm that each Search campaign's ad copy commits clearly to one language, and that it points to a landing page in the same language. Mixed-language pages are the single biggest own-goal under the new system.

Then watch, because September was a noisy month. The same window pushed automatically created assets and campaign-level broad match into AI Max, so if your numbers wobble in late September or October, the language change is only one of several possible causes. Pull your search terms report and check the languages of the queries you're actually matching — that's now your only real visibility into whether Google is reading your audience the way you intend.

If you run compliance-sensitive or tightly segmented campaigns where language was doing more than matching — regulated categories, or region-specific offers — flag those for closer monitoring, since Google has said the specialised use cases are "less settled" and it hasn't added new language reporting to prove delivery.

For brands that would rather have this handled as part of a proper account structure — one where creative, landing pages, and bidding are built to work with Google's AI instead of fighting it — our growth marketing team runs exactly this kind of audit and rebuild for Indian D2C stores. The accounts that stay calm through changes like this are the ones that were already clean.

Bottom line

Google took away a lever, but it didn't take away your control — it just moved it into your creative. For single-language campaigns, almost nothing changes day to day. For India's multilingual reality, the work is to make every campaign's language obvious in the copy and the landing page, accept that you have less say over bilingual edge cases, and keep a closer eye on your search terms than you used to. Tighten the signals you can control, and let the ones you can't go.