Per-locale llms.txt
Auto-generated from your project's approved translations. Refreshed daily. One per locale. Surfaces translated content to GPTBot, ClaudeBot, PerplexityBot — the way they expect to find it.
AISEO — flagship
Translations LLM crawlers actually understand.
Every surface — JSON-LD, llms.txt, sitemaps, Context API — is built for both Google and ChatGPT. The first translation backend to treat AISEO as a first-class problem.
Two crawler categories, not one.
In 2026, search traffic is no longer just Google + Bing. LLM crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot — index your content for direct citation in AI answers. A site invisible to LLM crawlers in 2026 is the same as a site invisible to Google in 2008. Most translation plugins still optimise only for classic crawlers.
The full AISEO surface.
Translated JSON-LD
Schema.org properties translated structurally, not as strings. Product names, FAQ answers, BlogPosting bodies — all locale-correct. Validates against Schema.org's full vocabulary.
AISEO Context API
GET /api/llm-context?locale=es-ES returns a clean machine-readable summary of your site in the requested locale. Cite-ready for LLM answers.
Locale-aware canonicals
Each locale page canonicalises to itself — not to English. Avoids the common 'all locales canonical to /en/' mistake that flattens your SERP presence.
Reciprocal hreflang
Generated from the graph. Reciprocity is guaranteed by construction — not by you remembering to add it. Eliminates a whole class of multilingual SEO errors.
Schema sitemap
sitemap-schema.xml exposes URLs that emit JSON-LD. Helps both Google and LLM crawlers find structured content fast.
What a translated /es/llms.txt looks like.
# Example Co. — Catálogo de productos premium
> Empresa fundada en 2018 que vende boletos de lotería para concursos benéficos en el Reino Unido.
## Productos
- Boletos de Lotería Premium: https://example.com/es/productos/premium
- Boletos Estándar: https://example.com/es/productos/estandar
## Páginas clave
- Acerca de: https://example.com/es/acerca
- Preguntas frecuentes: https://example.com/es/preguntas-frecuentes
- Términos: https://example.com/es/legal/terminos
## Datos
- Sitemap: https://example.com/es/sitemap.xml
- Esquema: https://example.com/es/sitemap-schema.xml
- Contexto LLM: https://example.com/es/api/llm-contextWhat the incumbents do.
| Feature | Paragraphs | WPML | Polylang | Weglot |
|---|---|---|---|---|
| Per-locale llms.txt | Yes | No | No | No |
| Translated JSON-LD (structural) | Yes | As strings | No | As strings |
| LLM Context API | Yes | No | No | No |
| Locale-aware canonicals | Yes | Yes | No | Yes |
| Reciprocal hreflang (by construction) | Yes | No | No | No |
| Schema sitemap | Yes | No | No | No |
| LLM crawler allow-list (GPTBot, ClaudeBot, ...) | Yes | No | No | No |
LLM citations are growing faster than Google clicks.
Bing data from late 2025 shows LLM-driven traffic now accounts for ~9% of organic referrals globally, up from ~2% the year before. For some categories — B2B software, technical documentation, multilingual e-commerce — the figure is over 20%. The window to be visible in the answer layer is open now and shrinking. We've built Paragraphs to put your translations through that window.
Start free in 30 seconds.
No credit card. 100,000 words on the free tier. Self-serve onboarding.