AI chatbot for multilingual sites
SleekAI adds an AI chatbot for Translated Sites to your WordPress site. It answers from the content you choose, such as posts, pages, custom post types, post meta, taxonomies and user data, with your own OpenAI, Anthropic, Google, or OpenRouter key.
Most chatbots break on translated WordPress
Most chatbots break on translated WordPress because they ignore the active language. The widget loads, picks up the original-language content, and quotes English documentation at a Spanish reader.
Features
Answers from your data
Map post titles, content, post meta, taxonomies or a WP_Query into the instruction, and the bot answers from what your site actually publishes.
Your model, your key
Use OpenAI, Anthropic, Google, OpenRouter or a compatible endpoint with your own API key. The provider bills you directly.
Shown where it fits
Display conditions scope each chatbot by post type, taxonomy term, post template, user role or logged-in state.
Where multilingual chatbots matter
Repeat questions
Answer the questions visitors ask every day from the pages and posts where you already answer them.
The next step
Put your booking page, contact form or pricing page in the instruction so the bot links visitors there when they are ready.
Logged-in visitors
With user and user meta data in the context, a logged-in visitor can ask about details stored on their own account.
One install, every language, no compromises
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Pick a model
Store your OpenAI, Anthropic, Google or OpenRouter key once in the shared AI settings, or add a compatible endpoint, and choose the chatbot’s model.
Review and refine
Turn on logs, read what visitors ask and tighten the instruction or the page behind it.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Why locale-aware AI is the line between launch and abandonment
Multilingual sites that bolt on a generic chatbot tend to launch loud and quietly disable the bot in non-default locales within a quarter. The reason is always the same: replies in the wrong language, citations from the wrong translation, no QA tooling per locale, and a support team that can’t review what they can’t filter.
Each of those failures compounds with international customers who already feel like second-class citizens of an English-first product. The cost angle matters too: one license covers every language on the same WordPress install, so adding a sixth locale doesn’t add a per-seat charge.
Frequently asked questions
Will the AI translate on the fly?
It can, but you get better quality by giving it the human translation as context whenever available. AI translation is fine for casual chat replies, but for policy or pricing language – where exact wording matters – the bot should quote the human translation verbatim. The system prompt is the right place to enforce that distinction.
Can I use a different model per language?
Yes. You might use GPT-4 for German formal contexts, Claude for nuanced French, and a cheaper model for casual locales where the cost-quality tradeoff is different. The configuration is per-bot, so changes don’t affect other languages.
Does it cost more for translated sites?
No – one license covers every language on the same WordPress install. The only variable cost is API usage, which scales with traffic but not with the number of locales. That’s why locale-aware AI economics work in WordPress where they don’t on per-seat SaaS chat tools that charge per language or per region.
What happens if a translation is missing for a piece of content?
The bot can fall back to the default-language version with a system-prompt rule that tells it to translate the gist on the fly, or refuse and link to the existing language version. Most teams choose the second option for policy content – where exact wording matters – and the first for casual content where a translated approximation is acceptable.
Which AI providers does it support?
OpenAI, Anthropic, Google and OpenRouter, plus custom OpenAI-compatible endpoints. You bring your own API key and the provider bills you directly.
Where does the chatbot get its answers?
From the WordPress data you map into its instruction: post titles and content, post meta, ACF and Meta Box fields, taxonomies, terms, users and user meta, or a WP_Query. Values resolve on every request.
Can it act on a visitor’s behalf?
No. A chatbot answers questions.
Can I control where the chatbot appears?
Yes. Display conditions cover post type, post, post status, post template, taxonomy, term, user role, logged-in state and WordPress conditional tags such as front page, archive, search and 404.
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack