Locations
Configure geographic regions and languages for localized AI visibility tracking. Understand how location settings affect AI response capture and analysis.
Overview
AI answer engines do not produce the same response everywhere. The country, region, and language of a user can influence what an AI model says — including which brands it mentions, how it ranks them, and what information it provides.
The Locations configuration lets you define the geographic regions and languages for your AI tracking, ensuring that the responses AEO Optima captures are relevant to the markets you care about.
Why Location Matters for AI Visibility
When a user in Germany asks "What is the best CRM software?" in German, the AI model may produce a very different answer than when a user in the United States asks the same question in English. Differences can include:
- Different brands mentioned — Regional players may appear in one market but not another
- Different rank positions — Your brand might rank first in one country and third in another
- Different sentiment — Market-specific perceptions can influence how the AI describes your brand
- Different recommendations — Pricing, availability, and regulations vary by country, and AI models reflect this
Without location-aware tracking, you only see a single perspective that may not represent your key markets.
Supported Regions and Languages
AEO Optima supports 20+ countries and 16+ languages for localized tracking. Locations are configured as country and language pairs, giving you precise control over the context of each AI query.
Example location pairs:
| Country | Language | Use Case |
|---|---|---|
| United States | English | Primary English-speaking market |
| United Kingdom | English | UK-specific brand perception |
| Germany | German | DACH region coverage |
| France | French | Francophone market |
| Japan | Japanese | East Asian market |
| Brazil | Portuguese | Latin American market |
| India | English | English-speaking Indian market |
| Spain | Spanish | European Spanish market |
| Mexico | Spanish | Latin American Spanish market |
You can add the same country with multiple languages (e.g., Canada in English and Canada in French) to capture bilingual market differences.
Adding Locations
To configure locations for your project:
- Navigate to Settings or use Step 4 of the Setup Wizard
- Open the Locations section
- Select a country from the dropdown
- Select a language for that country
- Click Add
- Repeat for additional locations
Each location you add creates an additional dimension for your snapshot captures. When a snapshot runs, prompts are sent with the appropriate location context for each configured location.
How Locations Affect Snapshots
Each location adds a multiplier to your snapshot captures:
Total calls per snapshot = Prompts x Models x Locations
For example, with 10 prompts, 3 models, and 2 locations, each snapshot produces 60 API calls. Keep this in mind when adding locations to balance coverage with usage.
Recommendations
Tip: If you operate in multiple countries, add your top 2 to 3 markets to see how AI visibility differs across regions. Start with your primary market and one secondary market, then expand as you identify meaningful regional differences.
Single-Market Brands
If your business operates in only one country, a single location is sufficient. Set it to your primary market and language.
Multi-Market Brands
For brands with an international presence, consider adding:
- Your primary market (highest revenue or traffic)
- Your top secondary market (next most important region)
- Any market where you are actively expanding and want to monitor AI perception
Global Brands
For brands with global operations, focus on the top 3 to 5 markets rather than adding every supported location. You can always adjust your location configuration as your monitoring strategy evolves.
Removing a Location
To remove a location, navigate to the Locations section in Settings and delete the entry. Removing a location does not affect historical snapshot data — past captures from that location remain available in your analytics. Only future snapshots stop including the removed location.