Short answer: Google is removing campaign-level language targeting from Search and AI Max for Search campaigns in late September 2026. Search matching will rely primarily on the language of the ad and landing page, together with user language preferences. Performance Max becomes a split case: the campaign language setting will stop controlling ads on Google Search, but it will continue to guide delivery on YouTube, Display, Discover and Gmail.
This is not a reason to delete every language setting today. Existing Search language criteria may still appear in Google Ads API queries, and Google says removing them is optional because they will simply stop applying. The urgent work is operational: audit multilingual ads and landing pages, stop writing obsolete Search language criteria through the API, and make sure Performance Max teams understand which channels still use the setting. Google published the change on August 13, 2026 and describes it as effective in late September 2026.
What is Google Ads language targeting?
Google Ads language targeting is a campaign setting that has historically let advertisers specify the languages used to help determine who can receive ads. The September 2026 change removes that campaign-level control from Search and AI Max for Search, while retaining a guided role for the setting on Performance Max channels outside Google Search. Language matching still happens; the controlling signals and channel rules change.
What changes in September 2026?
| Campaign or channel | Late-September behavior | What the advertiser should do |
|---|---|---|
| Search | Campaign-level language targeting is removed. Matching uses the language of ads, landing pages and user language preferences. | Separate languages clearly in creative and landing-page paths; stop relying on the old setting as a hard filter. |
| AI Max for Search | The same campaign-level language removal applies. | Review AI Max creative and URL expansion paths by intended language. |
| Performance Max on Google Search | The campaign language setting is no longer used for Search inventory. | Apply the Search-language audit to PMax assets and landing pages that can serve on Search. |
| PMax on YouTube, Display, Discover and Gmail | The selected campaign language continues to guide who sees your ads. | Retain and review the setting for these channels; do not assume the Search change removes it everywhere. |
| Google Ads API for Search | Existing language criteria remain queryable, but add/update mutations can fail. | Remove obsolete write operations and handle the documented context error. |
| Google Ads API for PMax | No equivalent mutation error is expected because the language setting still matters on non-Search channels. | Keep PMax logic separate from Search logic. |
The key distinction is setting removal versus language removal. Google is not making all Search ads language-neutral. It is changing the signal used to match an ad to a user. For a broader view of how these controls fit with automated targeting, see DMT’s AI Max, Performance Max and Smart Bidding guide.
Why multilingual advertisers should care
Under the old mental model, teams could treat the campaign language selection as the first line of control and then reuse creative or landing-page structures more loosely. That becomes riskier for Search. If the ad and page are the primary language signals, unclear language architecture can create an avoidable mismatch between the query, the ad promise and the destination.
Consider an advertiser serving English and Hindi campaigns in India. A language setting alone will no longer do the work for Search. The account needs language-consistent ad copy, final URLs and page content. A mixed-language page may still be useful to people, but it should be a deliberate user-experience decision rather than an accidental result of one template serving every campaign.
- Creative teams need a reliable inventory of approved copy by language.
- Landing-page teams need clear page-language ownership, correct final URLs and consistent conversion paths.
- Paid-media teams need to distinguish Search behavior from PMax non-Search behavior.
- Developers need to stop adding or updating obsolete Search language criteria.
- Analysts need to annotate the rollout and watch language-level mix without inventing a causal performance story.
This is also a reminder that generative advertising systems do not remove the need for human information architecture. DMT’s explainer on generative AI in advertising covers the wider governance problem: automation can create more variants, but it cannot decide your intended audience, legal boundaries or quality threshold for you.
The Google Ads API change
The API behavior is unusually concrete. Google says existing language criteria will still be returned in queries even when they are no longer used for Search targeting. A reporting job can therefore see a criterion that no longer controls delivery. That is a classic migration trap: presence in a read response does not mean the setting remains effective.
For Search campaigns, attempts to add or update CampaignCriterion.language will return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. Google recommends that new Search campaign workflows stop including language criteria. Existing criteria may be removed for cleanliness, but removal is not required because they will not apply.
A safe migration pattern for API teams
- Inventory every job, script, template and third-party tool that writes campaign language criteria.
- Branch by campaign type. Search and AI Max for Search should not share the same language-write logic as Performance Max.
- Stop adding the field for new Search campaign creates and updates before the rollout.
- Keep read compatibility so old criteria do not break reports or reconciliation jobs.
- Treat the documented context error as a migration signal, not a transient error to retry indefinitely.
- Test in a non-production account or a bounded campaign workflow before shipping the code change across all accounts.
- Record the rollout date in change logs and dashboards so later movement is not falsely attributed to an unrelated optimization.
Google’s adjacent August 12 announcement also says campaign-level Broad Match and standalone Automatically Created Assets will migrate progressively to AI Max during September. That is a separate migration with its own defaults and API fields. Coordinate the work, but do not collapse both changes into one switch.
A seven-part account audit before late September
1. Map campaigns to intended languages
Create a simple account-level map: campaign, campaign type, intended language, ad-group language, landing-page language, final URL and owner. Do not use the existing Google Ads language setting as the only source of truth. The purpose of the map is to reveal where the intended experience and the actual assets disagree.
2. Separate Search from PMax channel behavior
A single sentence such as “Google removed language targeting” is incomplete. For PMax, the setting stops applying on Google Search but continues to guide YouTube, Display, Discover and Gmail. Build the audit around that channel split. If a PMax campaign serves several languages, verify that its assets and destinations make sense both on Search and across the visual channels.
3. Check ad-language consistency
Review headlines, descriptions, sitelinks, callouts, business names and automatically created text for unintended language mixing. Brand terms, product names and borrowed English terms can be valid inside another language; the test is whether a real user receives a coherent promise, not whether every token belongs to one dictionary.
4. Verify landing-page language and final URLs
Confirm that each ad group or asset group points to the intended page version. Check visible copy, form labels, validation messages, confirmation pages and consent text. If final URL expansion is enabled, review which pages Google may select and exclude routes that would create an inconsistent language journey.
5. Review conversion measurement by language
Use stable naming or URL dimensions to compare conversion paths by intended language. Avoid declaring the rollout a success or failure from a short window: geography, device, query mix, auction conditions and creative changes can move simultaneously. DMT’s 2026 AI and digital-marketing overview explains why measurement design has to accompany automation, not follow it.
6. Update scripts, templates and QA rules
Search repositories and workflow tools for language-criterion writes, not just visible Google Ads scripts. Bulk-upload templates, account-creation forms, internal APIs and vendor integrations may all encode the old field. Add a test that fails when a Search create/update operation still includes the obsolete language mutation after the migration date.
7. Define rollout monitoring before changing bids
Record a baseline for spend, impressions, conversions, actual CPA or ROAS, search terms and language-specific landing-page traffic. Monitor the rollout, but do not react to every daily fluctuation. If the same account is also affected by Google’s August target-bidding change, use DMT’s target CPA and ROAS review checklist to keep the two interventions separate.
What not to do
- Do not delete PMax language settings indiscriminately. They still guide delivery on non-Search channels.
- Do not assume a queryable API criterion is still active. Google explicitly says legacy language criteria can remain visible after they stop applying.
- Do not retry the documented Search mutation error forever. Remove the obsolete write path.
- Do not mix languages accidentally and call it localization. Make the ad-to-page journey deliberate.
- Do not promise a performance lift. Google’s announcement defines behavior, not a benchmark or guaranteed outcome.
- Do not attribute every September change to language matching. AI Max migrations, bidding changes and ordinary auction variation may overlap.
What remains unknown
Google gives a late-September effective window but does not say in the announcement that every account will switch at the same moment. It does not publish a performance benchmark for the change, specify a required deletion date for old criteria or document every user-interface transition. Those are unknowns, not gaps to fill with assumptions.
The safest operating stance is to make the code and content changes that Google explicitly recommends, preserve observable baselines, and verify actual account behavior during the rollout. If Google adds account-level notices, UI documentation or a more precise schedule, this article should be refreshed rather than treated as timeless.
Frequently asked questions
Is Google Ads removing language targeting completely?
No. Campaign-level language targeting is being removed for Search and AI Max for Search. In Performance Max, it will no longer be used for Google Search inventory but will continue to guide delivery on YouTube, Display, Discover and Gmail.
Do I need to delete existing Search language criteria?
Google says removal is optional. Existing criteria may remain queryable even though they no longer apply to Search targeting. The essential change is to stop adding or updating them in Search campaign API workflows.
What signals will Search use instead?
Google says Search will primarily use ad and landing-page language, alongside user language preferences. That makes creative and destination-language consistency an important operational control.
Will Performance Max API mutations fail too?
Google says there will be no equivalent error for Performance Max because campaign language targeting can still be used on its non-Search channels. Do not reuse the Search migration rule blindly.
The practical takeaway
The late-September change shifts Search language control away from a campaign checkbox and toward the language evidence in the ad and landing page. For marketers, that raises the value of clean localization architecture. For developers, it creates a specific API migration. For PMax teams, it demands channel-level thinking rather than one universal rule. That channel-aware discipline is also part of DMT’s broader digital marketing strategy for 2026.
Audit intended language, creative, destinations and write operations now; preserve PMax language settings where non-Search delivery still needs them; and measure the rollout without claiming a result Google has not promised. That is the smallest defensible response to the official announcement.
Author and editorial method
Tayeeb Khan writes Digital Marketer Tayeeb’s practitioner-led coverage of paid media, SEO and AI-enabled marketing. This article was checked on August 15, 2026 against Google’s official Ads Developer Blog, a freshly authenticated DMT WordPress inventory and an intent-sensitive duplicate review. Confirmed product behavior is separated from editorial recommendations and unknown rollout details. No social post, third-party benchmark or unverified performance claim was used as proof.
