Skip to main content
Part of the Architecture and Design Philosophy guide, which indexes every topic. For deployment topology, directory layout and CI/CD, see ARCHITECTURE.md.

​
Internationalization and Search Indexing

World Monitor uses application localization for the dashboard and Pro surfaces, and indexable localized documents for the welcome landing. A ?lang= parameter remains supported as shareable user preference state on /, /dashboard, and /pro: the client loads the requested interface dictionary, updates the rendered document language and direction, and preserves the base page canonical. Query-string locale URLs do not belong in hreflang, robots, or sitemap output. The apex welcome page also ships prerendered landings at /es/, /pt/, /ru/, /fr/, /de/, and /ar/. Those URLs return HTTP 200 HTML with translated visible copy and metadata. There is no Accept-Language redirect: crawlers and direct visits receive the localized document. The locale set lives in shared/indexable-landing-locales.ts. hreflang policy by surface: Every advertised landing page must meet the complete localized-page contract:
  • translated visible main content and metadata;
  • a correct <html lang> declaration;
  • a stable crawlable URL that returns HTTP 200 and remains indexable;
  • a self-referencing canonical;
  • self-referencing and reciprocal hreflang entries across the cluster; and
  • sitemap inclusion for the localized canonical URL, with xhtml:link alternates on the landing cluster.
Genuinely localized pages must not canonicalize back to English. Adding a client translation or a supported locale code does not authorize publishing a new indexable alternate until that locale is added to the landing registry and prerendered.