Introduction
AI engines answer in the language of the question, and they draw on sources written in that language. A brand that is well known in English answers can be missing from the same question asked in German, Japanese or Arabic. This playbook covers multilingual AI visibility: how to track the questions buyers ask in each language and region, find where you are weakest, and translate and localize the pages that can close the gap.
Who it is for: brands that sell in several languages, international SaaS and ecommerce teams, and agencies running visibility for clients across markets. If you only need the tracking setup, the local and multi-region playbook covers it in short form.
The goal is not to translate everything. It is to find the few markets and pages where a localized answer would change what engines say, and to do those well.
The challenge
Translation alone rarely works. Buyers in each market phrase questions differently, compare you with local competitors and trust local review sites, media and forums. A page translated word for word may answer a question nobody in that market asks, and still be outweighed by the local sources engines prefer.
There is also a budget question. Every language and location you add multiplies your tracked prompts, and each prompt in each location counts once toward your plan’s limit: 50 on Shine, 100 on Signal and 1,000 on Scale. You need a way to choose markets, not track every one.
Finally, teams lose the thread. Results for each market end up in separate sheets, and nobody can say which market is weakest or whether last quarter’s translations helped.
The approach
Track the same topics in every market, written natively, so results compare. Read the markets side by side, then work on the weakest one: local sources first, then localized pages.
- Prompts can be written in 13 languages: English, German, French, Spanish, Turkish, Japanese, Portuguese, Hindi, Korean, Italian, Dutch, Swedish and Arabic.
- Locations cover 18 main regions and about 50 more countries, US states and cities, each with its own results.
- The Locations view on Tracked Prompts compares places by Visibility, Position, Mentions or Citations, with cards for your weakest location, your strongest and the biggest gap between them.
- Citations can be filtered by region, so you can see which local domains engines cite.
- The Translate a page skill in the Chat agent drafts a translation of a page for a native speaker to review.
The aeoora app itself is in English only. The prompts, the answers and your pages can be in any of the 13 languages.
Step by step
- Choose markets by value: list the languages and regions that matter for revenue, and start with two or three. One language can span several regions, such as Spanish in Spain and Mexico, and the answers can differ between them.
- Budget your prompts: multiply prompts by locations before you add them. For example, 20 prompts in four locations use 80 prompt slots, which fits within Signal’s 100. Pause prompts you no longer need, since paused prompts do not count.
- Write native prompts: ask a native speaker how a buyer in that market would phrase the question, or review Prompt Suggestions in that language, up to 25 per refresh. The free AI prompt ideas generator is another starting point. Avoid literal translations of your English prompts.
- Keep topics shared: assign each localized prompt to the same topic as its English counterpart, so you can compare “pricing” or “integrations” across markets.
- Add the locations: open Prompts, go to Tracked Prompts and switch the view to Locations. Choose Add location, pick the places, choose which prompts to track there and check the plan usage shown before you confirm.
- Add local competitors: within your plan’s limit of 5, 10 or 25 per brand, include the rivals that lead in each market, not only your global ones.
- Compare markets: after a week of daily results, open the Locations view and read the weakest-location and biggest-gap cards. Pick one market to work on first.
- Read local citations: in Citations, filter by that region and switch to Third-Party. List the local review sites, media, directories and forums engines cite, and note where competitors appear and you do not.
- Translate and localize key pages: pick the pages engines should cite in that market, often the product, pricing and comparison pages. Run the Translate a page skill, then have a native speaker review terms, examples, prices, currency and units. Finish in the Content Editor and send the page to your CMS.
- Make language versions easy to find: give each language its own URL, link the versions to each other with hreflang annotations, and keep a language switcher in your navigation so crawlers and people can reach every version.
- Earn local sources: work through your list of local third-party sites: get listed, complete your profiles in the local language and ask local customers for reviews.
- Measure by market: send each localization to the Action Center as an action, and compare that market’s results at 7, 14 and 30 days.
Tip: For right-to-left languages such as Arabic, check that your localized pages display correctly, including mixed text with product names and numbers, before you judge the results.
Decide what not to localize
Some markets do fine with English pages, especially in categories where buyers search in English anyway. If a market’s localized prompts already name you and cite your English pages, spend the effort elsewhere. Localize where the Locations view shows a clear gap and the market matters to revenue.
What to measure
- AI Visibility Score per market and per language.
- Mentions, position and sentiment for localized prompts.
- Citations by domain in each region, including local third-party sources.
- Whether your localized pages are cited in their own market.
- Share of voice against local competitors.
- Result checks at 7, 14 and 30 days for each localization action.
Compare markets with the same topics and the same engines. If a market stays weak after localized pages go live, the gap is usually in local sources, so shift effort there before you translate more pages.
Next steps
Read the guides on AI engines, languages and locations, prompts and topics and citations, and see how skills like Translate a page work in Chat skills and Memory. For a shorter setup guide, read the local and multi-region playbook, or brainstorm local questions with the free AI prompt ideas generator. Check prompt limits on pricing, or start a 2-day free trial.


