# Multilingual AEO: Localized Pages and Discovery

> Canonical source: [Multilingual AEO: Localized Pages and Discovery](https://www.answer.cloud/pages/multilingual-aeo-hreflang-localized-hubs-and-llms-txt-per-locale-hosted/)

Publish reviewed localized content and use language annotations without promising visibility from a locale guide alone.

Give each important localized version a clear URL and reviewed content. Translate meaning, examples, units, and policies rather than only individual words.

## Choose an architecture

Language folders or locale subdomains can both work. Keep the chosen URLs stable, avoid mixing unrelated languages on one page, and make navigation between versions clear.

## Use language annotations correctly

Google documents supported language and regional annotations in its [localized-versions guide](https://developers.google.com/search/docs/specialty/international/localized-versions). Check reciprocal alternates and canonical relationships for your actual pages. These search annotations do not establish a universal behavior for every AI provider.

## Maintain discovery resources

A sitemap can list the localized pages. The [llms.txt proposal](https://llmstxt.org/) permits content guides scoped to a host or path, but publishing one does not prove a measured visibility improvement for a language. On answer.cloud, use the platform publishing workflow for generated resources.

Test representative questions in each important language and have a fluent reviewer check facts and terminology. See [multilingual chat](https://www.answer.cloud/pages/what-languages-does-answer-cloud-chat-support-hosted/).