For Polylang and WPML multilingual sites
Your bot speaks the language your visitor is reading.
For Polylang / WPML sites : locale detection on the widget, schema per translation, content sync tagged by locale, FAQ schema per language. Bundle €39/month with multilingual flag enabled.
Your translations are good. Your bot embarrasses them.
You’ve invested in translating your site into 3-8 languages with Polylang or WPML. SEO is set up by locale, hreflang is correct, your localized content ranks. Then your AI chatbot vendor ships a widget that ignores all that — answers in English regardless, mixes up languages mid-conversation, treats all your translations as one corpus.
And schema.org coverage is split too : you can’t reasonably tag a French page with English-language FAQ JSON-LD. AI search engines (Perplexity FR, ChatGPT FR) need locale-specific structured data to cite you correctly.
Animam ships locale awareness end-to-end : the widget detects pll_current_language (Polylang) or ICL_LANGUAGE_CODE (WPML), tags the visitor session with the locale, the corpus filters by locale before retrieval, and the schema tools attach JSON-LD per translation.
What you actually need from us
Your investment in translation should compound, not get diluted by an English-only bot.
| Feature | How much you care | Why |
|---|---|---|
| Locale-aware visitor widget | ★★★★★ | Detects Polylang / WPML / WP core language, passes to backend. |
| Content sync per locale | ★★★★★ | Each translation indexed separately. Bot retrieves only the matching locale before answering. |
| Schema tools per translation | ★★★★★ | Attach FAQ / Article / Product schema to a specific translation, not a global page. |
| Admin assistant for bulk cross-locale ops | ★★★★ | Audit schema coverage across all locales in one chat turn. |
| MCP server | ★★★ | Useful if you wire your translation tooling (DeepL, Lokalise) as MCP tools. |
| Webhooks | ★★★ | Standard. |
Bundle €39/mo + multilingual flag enabled
Bundle €39/mo — covers the standard need. Enable the multilingual flag in Animam → Settings → Multilingual. The plugin auto-detects Polylang or WPML and starts tagging conversations and corpus by locale.
For multi-tenant agencies running 30+ multilingual client sites, upgrade to Agency €199/mo for sub-account architecture and bulk-locale ops.
Three things you do on day one
1. Enable the multilingual flag
In Animam → Settings → Multilingual toggle the Polylang/WPML detection. The widget now passes locale on every visitor request. Verify by inspecting the network tab on a translated page : you should see locale: fr_FR (or your locale) in the chat call.
2. Re-sync your corpus to tag by locale
In Animam → Settings click “Resync corpus.” Existing posts get re-pushed with their locale tag. New posts auto-sync with locale on save_post.
3. Audit schema coverage cross-locale
Open admin chat. “Audit schema across all locales, return per-locale counts.” You see immediately which language has gaps. Apply schema fixes one locale at a time.
FAQ
Polylang or WPML or both?
Both supported. The plugin auto-detects whichever is active. WP core language fallback if neither.
Will the bot answer in the visitor's language?
Yes — the locale is passed to the LLM as system context, and the corpus retrieval is filtered by locale. The bot answers in the language of the page the visitor is reading.
What if a translation is incomplete (only EN exists for some pages)?
The bot falls back to the canonical (default-language) version when a translation isn’t available, and acknowledges in the response : “I have this in English only, here’s the answer in your language with the source link.”
Can I attach FAQ schema only to the French page, not English?
Yes. wp_set_faq_schema takes a post ID — Polylang / WPML treat each translation as a separate post ID. Attach per ID, target the right translation.
Hreflang?
Polylang / WPML manage hreflang on the SEO side. Animam respects whatever they emit; we don’t override.