Google documents beta workflow for AI Search campaign localisation

What changed

Google documents a beta workflow for localising English (US) Search campaigns into supported languages. It creates a separate campaign and includes translated assets and keywords, back-translation for review and optional landing-page translation.

Documentation is not a launch announcement

Dario Zannoni surfaced the help documentation, and Search Engine Land reported on it. Neither the existence of the page nor its discovery establishes that the beta launched during this week. The sources also do not prove that every Google Ads account can access it or that all desired languages are supported.

The feature should therefore be described as a documented beta workflow. Eligibility and supported-language access need to be checked in the relevant account before a localisation plan depends on it.

Human review remains necessary

Back-translation can help an English-speaking reviewer understand generated text, but it cannot establish that the target-language wording is natural, culturally appropriate or compliant with market-specific requirements. Copied budgets and bids, currency, translated claims and destination behaviour also require review before activation.

Optional landing-page translation creates a separate customer-journey question. An accurate ad may still lead to inconsistent prices, forms, fulfilment terms or untranslated support content. The evidence documents the option, not the quality or completeness of any generated translation.

A controlled market test

Editorial suggestion: begin with one supported market and appoint a fluent reviewer who understands the product category. Compare the translated campaign with the English-US source across claims, keywords, negatives, budgets, bids, currency and final destinations. Record every deliberate departure from the source campaign.

Test the complete route from search term to conversion and after-sales information. A translated headline should not be approved in isolation if checkout or essential conditions remain unsuitable for the market. Treat the localised campaign as a new operational object with its own approvals and monitoring.

Keep the first test narrow enough to distinguish translation or market-fit problems from broad geographic expansion. Automated localisation may reduce setup work, but the sources provide no performance or translation-quality guarantee.

Why it matters for advertisers

The beta could shorten campaign setup, but localisation errors can affect claims, spending and customer journeys. Fluent market review remains necessary even when translation and back-translation are automated.