Google Ads Language Targeting Is Going Away: The Operator Playbook

Google just quietly reshaped one of the oldest settings in your Search account. In a note published August 13 by Search Engine Journal, and confirmed on the PPC Land policy tracker, Google Ads language targeting is being removed from Search campaigns and from the Search inventory inside Performance Max. The change starts rolling out in late September 2026, and it is going to change how you audit accounts, how you brief clients, and how your API tools push new campaigns.

Most posts about this update lead with “Google’s AI will handle it, do not worry.” That is not the operator take. If you run paid media at scale, google ads language targeting has been one of your cleanest guardrails against wasted spend for a decade. The removal does not break your account overnight, but it does shift a real lever from your team to Google. This is the playbook we are using at Elevarus to prepare our client accounts before the September rollout.

What Is Actually Changing in Google Ads Language Targeting

The core update is simple. The campaign-level language setting is going away for Search campaigns and for AI Max for Search campaigns. Inside Performance Max, the setting will keep working for Display, YouTube, and Discover surfaces, but the Search slice of PMax will follow the new Search rule. Google is telling advertisers that it will now decide language eligibility on its own, based on ad creative language, landing page language, the language of the user’s query, and other user-side signals.

Ginny Marvin, Google’s ads liaison, framed it as a redundancy cleanup during the advertiser roundtable Search Engine Journal covered. The public position is that “the way things are behaving now aren’t changing” because Google already used AI signals alongside your setting. In practice, though, the manual field was a hard filter that stopped a lot of cross-language serving. Removing it turns that hard filter into a soft signal.

Two things are worth pinning to your project board before September. First, existing campaigns keep running, and Google says you do not need to restructure by language. Second, if you use the Google Ads API to spin up new Search campaigns, any add or update to language criteria will start returning a ContextError. Your automation code needs a patch before the rollout, or the next fresh campaign your tool builds will fail.

Why the Change Matters More for Lead Gen Than for Brands

If you sell direct to consumer with strong creative and a clean landing page, the AI-driven approach will probably feel invisible. If you run lead generation for HVAC, home services, insurance, or legal, the story is different. Your CPL depends on filtering out searches your operator cannot actually serve. That includes the language filter.

Take a Los Angeles HVAC advertiser who runs one campaign in English and a smaller campaign in Spanish. Under the current rules, the English campaign never serves against a query typed in Spanish, even if the user’s phone is set to English. After the update, Google may decide that user understands the ad and serve anyway. Sometimes that is good. Sometimes it means a call center gets a call it cannot close.

Value-based bidding accounts have the most to lose here because they train on downstream signals. If more mixed-language calls flow in and your CRM marks them as low value, your model may over-correct on totally unrelated segments. Our value-based bidding playbook already recommends adding a call-quality field back into Google. That field becomes non-optional the day this change ships.

The Google Ads Language Targeting API Fix You Need Before September

The Google Ads Developer Blog is clear on what breaks. Any mutate that adds or updates CampaignCriterion.language on a Search or AI Max for Search campaign will throw an OPERATION_NOT_PERMITTED_FOR_CONTEXT error after the rollout. Read requests still return the old criteria, they just no longer influence targeting. Performance Max campaigns will not throw an error because those language rows still apply on non-Search channels.

If your team has any of the following, block time this week to patch it:

• A campaign builder script that copies template settings into new client accounts
• A bulk uploader that syncs language criteria from a spreadsheet into Google Ads
• A nightly job like the one described in our nightly Google Ads anomaly workflow that mutates campaigns based on rules
• Any custom app pushing changes through the Google Ads API

The fix is small. Stop sending language criteria when creating or updating Search campaigns after the migration date. Leave existing criteria in place because Google says removing them is not required, and doing a mass delete generates its own noise in the change history. If your PPC team ships prompts to LLMs to write campaign scaffolding, add a rule to your system prompt library that removes any generated language line for Search campaigns.

Your 5-Step Audit Before Rollout

Here is the pre-rollout audit we are running across Elevarus client accounts. Block ninety minutes on your calendar and walk your top five accounts through it.

Step 1: Inventory Search and AI Max campaigns by declared language. Export the Campaigns view with the language column visible. Flag every campaign where the declared language does not match the ad copy or the landing page. Those are the campaigns most likely to shift behavior in September.

Step 2: Sample search terms by language. Pull the last 30 days of search terms and count how often the query language matches your target. If mismatched queries already exceed 3 percent of spend, expect that share to grow after rollout. Add negative keywords now.

Step 3: Check your PMax Search slice. PMax will follow the Search rule. Review the asset group creative and landing pages. If they are English-only, keep them English-only. If they are multilingual, split assets by language now before Google’s AI decides for you.

Step 4: Patch your API surface. Search your codebase for language_code, CampaignCriterion.language, and any hardcoded language ID lists. Wrap the writes with a date check that skips them after the September 1, 2026 rollout starts.

Step 5: Update your reporting. Add a segment for query language to every Search performance dashboard. If your call tracker captures caller language, tie it back. This turns the coming change from a mystery into a measurable trend.

What Google Ads Language Targeting Removal Means for Account Structure

Google says you do not need to restructure, and that guidance is right for most accounts. There are still two exceptions worth flagging.

First, if your account uses language purely as a routing shortcut, the shortcut breaks. Some agencies used a separate Spanish campaign to route lower-value leads to a lighter follow-up sequence. Under the new rules, both campaigns become eligible to serve against the same query, and Google’s AI picks the ad group by relevance, not by your routing intent. Rebuild that routing at the CRM layer instead of at the campaign layer.

Second, if you run policy-sensitive verticals, the removal narrows your control. Financial services, legal, and healthcare advertisers already spend real time on policy reviews. Cross-language serving means an ad reviewed in English may now be scored against a query in another language, and disapproval risk rises. Keep language-specific creatives in language-specific ad groups. Do not merge them just because Google removed the setting.

The removal also stacks on top of the July 2026 terms changes and the 37-month data retention rule. Together they show a clear direction. Google keeps trimming manual account levers and asks you to trust its models. Your job is to protect signal quality on the way in and pull data out on your own schedule.

The rollout begins in late September and ramps across October. Between now and then, walk your team through this 60-day checklist at your next paid media stand-up.

Week 1: Communicate the change to clients. Send a plain-language note that language targeting is going away for Search, that Google will handle it with AI, and that you have a plan. This is the single biggest complaint driver if a client hears it from a competitor first.

Week 2: Patch every automation that mutates language on Search campaigns. Have engineering merge the patch and log a test in the sandbox. Confirm the sandbox surfaces the ContextError so your monitoring catches it.

Week 3: Sweep PMax placement audits and confirm the Search slice of every PMax campaign matches your creative language. Move mismatched assets into a dedicated asset group.

Week 4: Update your dashboards. Add query language segments. Add call-language flags if you use call tracking. Load a baseline for October so you can measure impact.

Weeks 5 through 8: Watch weekly. If mismatched queries jump above 5 percent of spend in any Search campaign, add negatives that week. Do not wait for a monthly review. Attribution changes fast under a shift like this.

Where Elevarus Comes In

We help lead generation and services businesses turn platform changes into operator systems. Google removing google ads language targeting is a good example of a quiet policy shift with real budget impact. It is not a crisis, but the accounts that ignore this google ads language targeting update will bleed budget by Q4. The accounts that run a real audit before September will keep their CPL steady and their sales team happy.

If you want a second set of eyes on your account before the rollout, or a template audit built for your team to run, book a free consultation. We will walk through your Search and PMax structure, flag the campaigns most at risk, and share the exact patch we push into API code.

Let’s Grow!