Yes. Polylang and Polylang Pro share the same translation API. SleekAI calls the standard pll_get_post and language detection functions, which behave identically on both editions. Pro features like translated string management and slug translation are picked up automatically because they live in the same data structures Polylang exposes. The integration treats free and Pro as one path.

Yes. Polylang for WooCommerce is supported and translated products feed the bot through the same resolver. A French product page produces a French pre-sale chat grounded in the French product description, price, and stock. Currency and tax behavior are handled by WooCommerce; SleekAI consumes whatever the active product's data shows. There is no separate per-language product import.

Yes. Display conditions filter by Polylang language slug, so you can run a default bot for most languages and a specialized one for a high-value locale. A common pattern is a single global bot plus a Japanese-only bot with a tighter prompt for the Japanese market. Both can coexist on the same site, each only loading on the pages where its display conditions match.

Categories, tags, and custom taxonomies in Polylang each have translated counterparts, and SleekAI reads the version matching the active language. That keeps taxonomy-scoped retrieval correct. A bot bound to a Polylang category will retrieve French articles in the French version of the category and Spanish articles in the Spanish version, without you needing a separate bot per language for category scoping.

Yes. If a translation is missing for a particular post, Polylang's resolver falls back to the source post, and SleekAI uses that. The model is still instructed to reply in the active language, so it translates the source content at generation time. For important pages the right fix is to publish the translation in Polylang; the fallback is a safety net for incidental content gaps, not a replacement for actual translations.

OpenAI, Anthropic, Google, and OpenRouter, with your own key. Most major European languages are well-served by frontier models from any of these providers. Conversation logs record the active language, so you can compare reply quality per locale and switch providers for specific languages if one model handles, say, Spanish noticeably better than another. The flexibility costs nothing; you bring the keys.

Yes. Polylang Pro can translate slugs so URLs reflect the locale. SleekAI consumes whatever URL Polylang produces at render time, so retrieval and citation work correctly even when slugs differ across languages. The bot's links land on the right localized URL, which matters for SEO consistency between the article surface and the chat surface.

Media translations through Polylang Media follow the same resolver pattern. Translated alt text and captions feed the bot's prompt context for the active language, which means image references in chat replies are described in the right language. SleekAI's own AI alt-text feature integrates here too: alt text generated for the source image can be translated through Polylang and picked up automatically by the bot.