Google’s November Creative Drop includes AI campaign translation, with the announcement listed on November 5, 2026. It is a timely reason to review how a local business prepares a second-language campaign. Faster translation still leaves decisions about the offer, destination, service area and response to an enquiry.
For a business serving English- and Persian-speaking customers in York Region or the GTA, I would plan the whole journey before creating more ads. The checklist below is my proposed working method, based on current official documentation. It is not a hands-on test of the translation beta or a claim about campaign performance.
Verify language support before choosing the workflow
The announcement describes translation across 15 languages. The linked help guide has a narrower published target list, including French (Canada), and does not list Persian. Those pages do not establish Persian translation availability; check the actual account and supported campaign format before planning around the beta.
Separately, Google’s general language table lists Persian for ads language targeting, with format-specific restrictions. Advertising in a language and receiving AI translation for that language are different capabilities. If the required translation path is unavailable, prepare and review the copy manually rather than treating the announcement as account-level confirmation.
Write down what you have verified: campaign type, source language, target language and the route used to prepare the assets. Keep unresolved availability questions visible. This small record prevents a team from promising a launch based on a feature that someone has only seen in a release announcement.
Keep the offer consistent while adapting the wording
Start with one approved offer brief: the service, who it is useful for, the area covered, relevant conditions and the next action. Then write each language version for a person reading it naturally. A literal translation can preserve individual words while making the message awkward or changing what the customer expects.
Ask a fluent reviewer to check meaning, tone and the action being requested. Give that reviewer the brief as well as the source copy. They should be able to identify a promise that appeared only in translation, an unclear qualification or a service term that local customers would phrase differently.
Keep brand names, phone numbers, dates and factual conditions traceable across versions. Treat translated text inside images as a separate asset to review. Record the approved wording and its version so later changes to the offer reach both languages, including sitelinks and supporting creative.
Match the destination and the response to the ad
Open the exact destination for each proposed ad on a phone. Check whether the headline answers the same need, the service conditions agree and the next action is understandable in that language. A translated headline does little for someone who reaches a page they cannot comfortably use.
For Persian, review right-to-left reading order, font loading, mixed phone numbers and English brand names. Test form labels, validation messages and the confirmation state as part of the same experience. The language of a menu is only one part of making the page usable.
Also decide who can answer an enquiry in each language and what happens when that person is unavailable. Keep the customer’s explicitly stated communication preference where it helps the handoff; do not infer identity or language preference from a name. A campaign is ready when its response process can support the promise made in the ad.
Review language, location and budget as separate decisions
Google’s language guidance describes Search changes starting in September 2026, including moving away from a campaign-level language setting, while other Performance Max channels retain language settings. It also describes multilingual users receiving ads in a language different from their query. Inspect the current campaign controls rather than assuming one universal language-filter setup.
Language does not define a service boundary. Google distinguishes location presence from presence or interest. Choose the geographic approach that fits the actual service model, then review where enquiries come from. An English or Persian message does not by itself establish that the person can be served in the area you cover.
For supported localisation-tool copies, Google says bids and budgets are copied without currency conversion. Review the new campaign’s spending scope independently. Decide how the two language versions fit the total approved budget, who may change it and which observation would justify a review. A copied number is not a considered budget decision.
Run a bilingual preflight with a small, explicit example
Consider a hypothetical roofing business that can answer customers in English and Persian and serves a defined part of York Region. This is an illustrative planning example, not a client campaign or a claim about local search volume. Its chosen objective is an enquiry containing enough information for a useful follow-up.
Prepare a message about the same genuine service in each language and connect it to the appropriate page. Use approved previews and test destination URLs to review the journey. Keep test submissions clearly identified so the team does not confuse quality checks with customer demand.
Give each issue an owner and a correction before launch. A readable Persian page with an English-only error message still needs work; a correct form with no available responder has a different gap. Review both versions against the same acceptance questions rather than approving the second language because the first one looks complete.
- Does each message lead to the intended language and service page?
- Are the offer and geographic limits consistent across both versions?
- Can the form be completed and its errors understood on mobile?
- Does the intended recipient receive a clearly identified test enquiry?
- Can the responder continue in the customer’s requested language?
Review useful outcomes before expanding the campaign
Define the counting rules before comparing language versions. Separate a form event from a received enquiry, then record whether the enquiry fits the service and can be followed up. Keep the same date basis and definitions across the comparison. A small number of observations can suggest questions without establishing which language performs better.
Use the early review to find friction: wrong destinations, misunderstood conditions, requests outside the service area or a handoff that loses context. A difference in lead counts can reflect delivery, budget or the counting method. Investigate the cause before rewriting the message or shifting spend.
Expand when the team can explain the journey and verify the operational result. AI-assisted translation may help prepare material where supported, but it does not replace a clear offer, a usable destination or an accountable response. Keep those decisions visible as campaigns and tools change.
- Use matched dates and a shared enquiry definition.
- Record service fit and response ownership separately from clicks.
- Keep uncertain observations distinct from proven causes.
- Review corrections before increasing the production or spending scope.
Key takeaways
- Verify translation-tool support separately from advertising-language support.
- Adapt the wording while preserving one truthful offer.
- Review the landing page, form and human response in each language.
- Choose geography and budget deliberately rather than inheriting them.
- Compare qualified enquiries with matched definitions before scaling.
Sources & further reading
- Google Ads announcement index: Creative Drop #2, listed November 5, 2026
- Google Ads: November Creative Drop #2 announcement
- Google Ads Help: AI campaign localisation for Search campaigns (beta)
- Google Ads Help: available interface and targeting languages
- Google Ads Help: language targeting and September 2026 changes
- Google Ads Help: preventing clicks outside targeted locations
Official Google pages checked November 14, 2026. The announcement index dates Creative Drop #2 to November 5; its article displays November 2026. The supporting help pages show no visible publication date. The announcement’s 15-language description and the narrower help-page list are reported as observed, not resolved into an assumed rollout. Persian AI translation availability, account eligibility and completed language-setting rollout were not verified in a live account. These same-vendor sources are not independent performance evidence. The checklist and roofing example are original analysis; no beta test, local demand estimate or campaign outcome is claimed.
Farshad Ghobadvand