Google Ads is changing how language targeting works for Search campaigns. Starting in late September 2026, campaign-level language settings will be removed for Search and AI Max Search. Instead, the language of your ad will inform matching. Ecommerce operators need to audit their ad-to-page journey and assign developer ownership for upcoming API changes to prevent broken workflows.
Managing a catalog of 1,000 or more SKUs across multiple regions requires strict alignment between your product data and your campaign settings. When platform rules change, your internal processes must adapt. Relying on ad language means your copywriters and feed managers must ensure every asset explicitly matches the intended language of the target buyer.
How the September language update changes matching
The announced change is a reason to audit the buyer journey, not an instruction to rebuild every campaign. According to the Google language targeting change, effective late September 2026, Search and AI Max Search campaign language settings are removed. Ad language will inform matching.
Performance Max Search changes similarly. However, other Performance Max channels retain campaign language targeting. This creates a split in how you manage language preferences depending on the specific channel within your Performance Max campaigns.
As of this article's September 19 editorial date, the announced effective period is still ahead. Check account notices and use the time to document where each language version leads. A country and a language are different dimensions: the same market can contain several language preferences.
Ad language informs matching; it does not by itself define the entire audience. Review whether the offer and destination make sense for the intended buyer. A brand name borrowed from another language is not automatically a defect, while untranslated delivery terms may be a genuine obstacle.
API errors and developer ownership
If your team uses the Google Ads API to manage campaigns at catalog scale, you need a developer to own this transition immediately. The upcoming change introduces new rules for API mutations that will break existing automation if left unaddressed.
For Search campaigns, API mutations that add or update language criteria will return an error once the change takes effect. Performance Max does not have this same rule. If your current scripts automatically apply language settings to all new Search campaigns, those scripts will fail in late September.
Consider a hypothetical scenario where your inventory management system automatically generates new Search campaigns for seasonal product drops. If the script includes a command to set the campaign language to English, that language-criteria operation is expected to fail under the announced rule; the effect on other operations depends on the integration's error handling. A failed script can halt your daily campaign creation, leaving high-volume SKUs without coverage during a critical launch window.
Assign a developer to audit your API calls now. They need to distinguish Search campaign operations from Performance Max campaign operations. The retained PMax setting is campaign-level, even though its effect differs by channel. This is an operational requirement, not just a marketing task. Your engineering team must update the codebase to conditionally apply language settings based on the campaign type. Require a test result showing how rejected operations are reported, which remaining work proceeds, and who receives the exception.
Give each language journey one accountable owner
A localized ad can pass copy review while the destination fails the buyer. Treat the journey as a small release, with one person responsible for collecting sign-off from the people who own each step. The copywriter checks the promise; the merchandising team checks the product; the store team checks checkout; customer support confirms what help is actually available.
For a hypothetical store serving French-speaking buyers, the review record might include a French ad, a French product page, an available size, a delivery estimate for the relevant postcode, and support hours that the business can honor. If the return instructions exist only in another language, record that gap before approving more spend. Translation completeness is not the same as service readiness.
Keep platform changes in a separate column. Google's DSA timeline correction moves that migration start to February 2027. It is a different change from September language matching. Separating the two helps reviewers ask the right question instead of treating every issue as a migration problem.
The useful output is a short exception list: affected product or template, market, observed failure, owner and next check. Fix a shared checkout template once where appropriate, then retest representative journeys instead of reviewing thousands of identical pages independently.
Auditing the ad-to-page journey by market
When ad language informs matching, the destination should make the same offer understandable to the buyer. A mismatch wastes spend and frustrates buyers. You must verify the language consistency across the ad, the destination page, the product information, customer service options, and the checkout process.
Consider a hypothetical scenario where a Spanish ad serves to a bilingual user in the United States. The user clicks the ad because the Spanish copy resonates with their search intent. If they land on an English product detail page, the sudden language switch causes friction. Even if the user understands English, the broken promise of the ad reduces the likelihood of a conversion.
To prevent this, propose a market and language quality assurance sample. Pull a list of your top 50 revenue-driving SKUs in each target language. Use available preview tools and the actual destination URLs rather than generating unnecessary paid clicks. Read the product title, the description, and the shipping terms. Add the item to the cart and proceed to checkout. If any step in that journey reverts to a default language, you have a leak in your funnel.
This level of consistency requires tight coordination between your feed, your landing pages, and your campaign creative. For more on maintaining this alignment, review our guide on ad, landing page, and feed messaging consistency. If your checkout provider defaults to English regardless of the landing page language, review the supported localization options and communicate any remaining limitation clearly before expanding spend.
What good looks like
Preparing for the late September language update requires technical and operational checks. A prepared ecommerce team will follow these steps:
- Assign a developer to review API scripts and remove language criteria mutations for Search campaigns before late September.
- Document which Performance Max channels retain campaign language targeting versus those that rely on ad language.
- Pull a sample of destination URLs by market to verify the landing page language matches the ad copy exactly.
- Check your product feed to ensure localized titles and descriptions route to the correct regional campaigns.
- Test the checkout process in each target language to confirm shipping, taxes, and payment terms translate correctly.
- Separate your DSA migration planning for February 2027 from your September 2026 campaign-level broad-match-setting upgrades.
- Establish a monthly review of ad-to-page language consistency for your highest-volume SKUs.