Google's Ads Product Liaison Ginny Marvin announced on LinkedIn on August 14, 2026 that campaign-level language targeting is being removed from Search campaigns and AI Max for Search campaigns, rolling out in late September 2026. For accounts running Ukraine-targeted campaigns that mix Ukrainian and Russian ad groups, or Ukrainian and English for companies selling to international buyers, this removes the setting that used to route each language to the right audience automatically.
Google first put a date on this back in late 2025, then pushed it back twice. The August 14 announcement is the third and, based on how it was framed, the final one - advertisers who deprioritized the first two warnings now have a narrower window to review account structure before the setting disappears.
What the System Uses Once the Setting Is Gone
Google's replacement mechanism reads the language of your ad creative, the language of your landing page, and existing signals about what language the searcher understands - browser settings, account language, and the language of the search query. It favors serving the ad and landing page combination that matches the query language. There is no manual override once the campaign-level setting is removed for Search and AI Max for Search campaigns.
A campaign that keeps Ukrainian and any other language fully separate, with matching landing pages for each, continues functioning the way it does today because Google reads that separation from the assets themselves. A campaign mixing languages inside one structure, using the language setting to route traffic, loses that routing mechanism at the campaign level.
Why This Deserves Attention for Ukraine-Targeted Accounts
Many Ukraine-facing accounts run multilingual structures because search behavior in the market spans more than one language, and advertisers historically built one campaign with language targeting handling the split rather than separate campaigns per language from the start. That structure worked as long as the manual setting existed to enforce it.
Google holds roughly 90% search share in Ukraine, and advertisers running lean 2026 budgets feel the cost of a language mismatch more directly than accounts in markets with larger average spend. If a mixed-language campaign starts showing the wrong-language ad to a portion of searchers after the rollout, the resulting drop in click-through rate and conversion rate shows up in a constrained budget faster than it would in an account with more room to absorb variance.
The Performance Max Distinction Worth Understanding
Performance Max campaigns handle this differently than standard Search campaigns. Language settings no longer apply to the Google Search results served through Performance Max - creative and landing page matching takes over there, same as in Search campaigns. Language settings continue to guide delivery on YouTube, Display, Discover, and Gmail placements within the same Performance Max campaign. Shopping ads inside Performance Max are unaffected entirely, which matters for Ukraine-based e-commerce advertisers who rely on that placement type.
No New Language Exclusion Capability
This change does not solve a gap advertisers have raised before: excluding a specific language from targeting is still not supported. The new signal-based matching can favor showing ads that match a query's language, but it cannot enforce blocking ads from a particular language segment - that limitation carries over unchanged.
API Impact for Accounts Using Automated Management
Accounts or agencies managing Ukraine-targeted campaigns through the Google Ads API, including bulk campaign setup tools or automated bid management connected to campaign settings, need to review that code specifically. Starting with the late September 2026 rollout, API calls attempting to set or read language criteria for Search campaigns will return an error. For teams running lean, often without dedicated engineering support, catching this before the rollout avoids losing time to a broken script during a period when every hour of campaign management matters.
A Checklist for Ukraine-Market Accounts Before Late September
- List every active Search and AI Max for Search campaign that currently uses language targeting under campaign settings.
- Check whether languages are already separated into distinct campaigns with matching landing pages, or mixed inside a single campaign relying on the language setting.
- Where languages are mixed, weigh whether splitting into separate campaigns before late September is worth the setup time given your budget size and how much precise language control matters to performance.
- Review landing pages for language consistency with the ad copy pointing to them - a mismatch here becomes a more likely cause of wasted spend once the manual setting is gone.
- Check any API scripts, bulk upload tools, or third-party platforms connected to the account for language criteria calls on Search campaigns, and remove that code before the rollout.
- Confirm Performance Max campaigns separately for Search placement behavior versus YouTube, Display, Discover, and Gmail placement behavior, since the two follow different rules within the same campaign.
For accounts already running fully separate campaigns per language, this is a short confirmation exercise rather than a restructuring project - the existing setup already gives Google the signal it needs.
Part of a Larger Shift Away from Manual Controls
This removal follows the same direction as the AI Max auto-upgrade rollout, which converts eligible Search campaigns to AI Max automatically based on existing account settings rather than a deliberate advertiser choice. Both changes reduce the manual levers advertisers have over Search campaign delivery. For Ukraine-targeted accounts already managing broader AI Max search term matching on tighter budgets, keeping negative keyword and brand exclusion lists tight matters even more once language matching also becomes signal-based instead of setting-based.
Building a habit of reviewing which manual controls remain in the account, on a recurring basis rather than only when Google announces a change, puts lean-budget accounts in a better position for whatever comes next in this same pattern.
FAQ
Does the removal apply the same way to Ukraine-targeted accounts as everywhere else?
Yes, the rollout is global with no market-specific exemption. What differs is exposure - accounts mixing multiple languages inside single campaigns have more to check than accounts already structured with separate campaigns per language.
Why does this matter more for accounts running lean 2026 budgets?
A language mismatch after the rollout can lower click-through and conversion rates on affected traffic. On a constrained budget, that drop is proportionally more visible and shows up in performance data faster than it would for an account with a larger cushion.
Does the Performance Max exception change anything for Ukraine-based e-commerce advertisers?
Shopping ads inside Performance Max are unaffected by this change entirely, which matters for e-commerce accounts relying on that placement. The Search placement within the same Performance Max campaign follows the new signal-matching rule, while YouTube, Display, Discover, and Gmail keep using language settings.
What is the single most time-sensitive item on this checklist?
Checking API scripts and bulk management tools for language criteria calls on Search campaigns. For accounts without dedicated engineering support, discovering a broken script after the rollout costs more time than removing the code proactively.
