For most of the history of search advertising, the expensive part of a new market was the ads. You hired a translator, waited two weeks, then found out half the keywords were words nobody in Lyon types. That friction kept a lot of companies at home. It also, quietly, forced them to think about the rest of the trip before they bought the first click.
Google just removed most of that friction. Since last week, Google Ads accounts have been getting a new entry in the Tools menu called Translation. Pick a Search campaign, pick a language, and Google’s AI builds a translated copy of the whole thing: headlines, descriptions, sitelinks, callouts, keywords, even the text on your images. It can also translate your landing page for anyone who clicks. A market test that used to take a quarter now takes an afternoon.
That is genuinely useful. It also flips the cost structure of going international. The ad is now the cheap part. Everything that happens after the click is exactly as expensive as it was last month, and the tool is built in a way that makes it easy not to notice.
What actually shipped
Search Engine Roundtable reported the menu on October 22, after Google Ads trainer Jyll Saskin Gales spotted it and posted on LinkedIn: “New menu alert in Google Ads: Translation.” The screen itself promises to “Translate your campaigns to reach global customers and boost your conversions.” PPC News Feed confirmed the tool live in the interface on October 23. Google had described it in a help article earlier in the month, and Search Engine Land covered that version as a test on October 2.
The help article is still labeled beta, and it is the best map of what you are getting. The essentials:
- It creates a brand new, independent campaign. Your original campaign is never modified.
- It works on Search campaigns only, and the source campaign must be entirely in English (US). A campaign containing any other language cannot be localized.
- There are ten target languages: Dutch, French, Canadian French, German, Italian, Polish, two kinds of Portuguese and two kinds of Spanish. More are promised by the end of 2026.
- Images with text on them get that text removed by AI, and the translated message is added as extra text assets.
- You can give it plain instructions, such as “Do not translate the brand name” or “Keep the tone formal.”
- The new campaign publishes paused by default.
One line on the page has already aged: “Starting September 2026, the tool will support Performance Max campaigns.” It is late October and the page still lists Search as the only supported type. Treat dates in this article as intentions.
The good part, stated fairly
Before the caveats, credit where it is due. Creating a separate campaign instead of editing the original is the right call. It means you can test a market without touching the account that pays your bills. Publishing paused is the right default. And the instruction field matters more than it looks, because brand names, product names and regulated terms are exactly what machine translation mangles first.
For a lot of companies the honest alternative to this tool was nothing. The Canadian French campaign never got built because nobody owned it. The Spanish campaign for US Hispanic customers stayed on the roadmap for three years. For those teams, a decent machine draft is a real improvement.
The trouble starts at step four.
A landing page that exists only for people who paid
For landing pages, Google offers two routes. One is a find and replace rule that points the new ads at language versions of your site you already have, say from /en to /fr. The other is what Google calls AI translation: you paste a snippet onto your site, and it “dynamically translates the texts on the landing page when a user clicks the ad.” Google says you only need to install it once per account.
Think about what that second route builds. The French page has no address of its own. It is put together in the visitor’s browser, on arrival, for someone who came from an ad. As the German trade site Dr. Web pointed out on October 23, that means the translated version gets no URL, and only ad visitors see it.
Google’s own search documentation explains why that matters. Its guide to multilingual sites says Google “recommends using different URLs for each language version of a page rather than using cookies or browser settings to adjust the content language on the page.” It warns that if you change content dynamically, “Google might not find and crawl all your variations,” because Googlebot usually crawls from the US and sends requests without saying what language it prefers. A second page on locale adaptive content repeats the recommendation: separate locale URLs, marked up with hreflang.
So one part of Google will happily sell you French traffic to a page that another part of Google, by its own rules, will probably never show to a French searcher for free. Every visitor in that market is a visitor you rent. When the budget stops, the market disappears with it. Fine for a two week test. Strange foundation for a country.
The help article also leaves two practical questions open. It does not say what happens when the visitor clicks from the translated landing page to a product page, a cart or a form. And as Dr. Web notes, it does not say whether the translation runs when a visitor declines consent, which matters in markets like Germany where touching the device generally needs permission. You will want answers to both before real money flows.
Budgets and bids from another economy
The second quiet assumption is money. Google’s help article is blunt: “Budgets and bids are copied exactly from your original campaign. The system doesn’t perform currency conversions or exchange rate calculations. For example, a $100 USD budget becomes a $100 USD budget in the localized campaign.”
That reads like a footnote. It is a pricing decision made by default. Your US campaign’s target cost per acquisition reflects US margins, US click prices and US conversion rates. Copy it into Poland or Portugal and you are bidding with someone else’s economics. Maybe you overpay and burn the test budget in four days. Maybe you underbid and conclude the market has no demand when your bids simply never entered the auction.
Prices inside the ad copy are the same problem in smaller type. If your headline says “Plans from $29” or “Free shipping over $50,” the documentation does not say what the translation does with those numbers, or whether the offer is even true in the new market. A translated promise you cannot keep is worse than an English one, because the customer actually understood it.
Reviewing a language you cannot read
Google anticipates that you do not speak Polish. The review screen shows four columns: the original, the translation, a “Translation back” into English, and translation notes. In Google’s words, “You don’t need prior knowledge of the target language to review your new campaign.”
Back translation is a real quality check. But here the same system writes the translation and then translates it back for you. If the model picked a word that is technically correct but sounds like a tax form, the English round trip will look perfectly fine. If a keyword is a literal rendering of your jargon that no local buyer searches for, the back translation will happily confirm the literal meaning. The column catches meaning drift. It does not catch tone, local search habits, or a legal phrase that has a specific meaning in Quebec.
There is one more door worth noticing. Besides the Tools menu and the campaigns table, the help article lists a third way in: applying a localization recommendation in the account’s recommendations panel, which Google says is triggered when it “identifies opportunities to increase performance with localization.” In practice that means the suggestion to enter a new market can come from the platform rather than from your planning cycle. Whoever clears recommendations in your accounts, often an agency or a junior buyer, should know this one is not a routine tidy up.
After the click, nothing changed
Here is the part the tool cannot touch, by design. Your order confirmation emails, your returns policy, your support inbox, your onboarding sequence and your sales team are all exactly where they were, and Google has not said the snippet reaches your cart. It translates a landing page. It does not answer the phone.
The research on this is old but sturdy. In 2020 CSA Research surveyed 8,709 consumers in 29 countries for its “Can’t Read, Won’t Buy” study. It found 76% of online shoppers prefer to buy products with information in their native language, and 40% will never buy from websites in other languages. Two other findings cut both ways. On one side, 65% prefer content in their language even if it is poor quality, which suggests a machine translated landing page beats an English one. On the other, 75% say they are more likely to buy from the same brand again if customer care is in their language.
Put those together and you get a clear picture. A rough translation can win the first click and maybe the first order. Repeat business lives in the parts of the company that never saw the campaign. If your test measures only first purchase cost, it will flatter the market. Scale on that number and your second quarter there will tell you what the first one hid.
Who should use it, and how
Use it if you sell something that ships or downloads across borders already, you get unprompted orders from a market you do not advertise in, and you want to know whether paid search there can work. Use it for US Spanish or Canadian French, where the rest of your operation may already be bilingual.
Be careful if your offer depends on local pricing, local regulation or local delivery promises, or if your product needs a sales conversation. The tool will build the campaign. It just has no idea whether you can serve the customer it finds.
What to do this week
Find out who in your accounts can press the button. The tool sits in the Tools menu and in recommendations. Agree that a new language means a new market decision, owned by someone with budget authority, not a campaign build.
Write a one page post-click ledger before any test. For the target market, list who answers support, what language checkout and order emails are in, whether prices and shipping promises in your ads are true there, and how returns work. Anything marked “English only” is a cost the test will hide.
Reset bids and budgets by hand. Do not launch with copied US targets. Set a fixed test budget and starting bids from that market’s own keyword planner estimates and your margins there.
Pick the landing route on purpose. The snippet is fine for a short test. If the test works, plan real language URLs with hreflang, so the market can earn organic traffic instead of renting all of it. Ask your consent platform owner whether the snippet runs before or after consent, and get Google’s answer in writing for EU markets.
Put a native speaker on the paused campaign. Thirty minutes from a freelancer or a colleague on the headlines, the top keywords and any claim with a number in it. That is the cheapest insurance in this whole process.
Measure the second order, not just the first. Set the test window long enough to see repeat purchase, refund rate and support tickets from the new market, and report them next to cost per acquisition.
The old friction of international search was annoying, but it made you ask whether you were ready before you spent anything. Google has made the asking optional. Ask anyway.
