WordPress Multisite chatbot
SleekAI adds an AI chatbot for WordPress Multisite 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.
Generic chatbots collapse on multisite
If you run a WordPress multisite network, you already know that most third-party chatbot widgets ship as if every install were a single site. Network admins end up either disabling the widget per subsite or rebuilding the integration from scratch with custom JavaScript.
Each subsite gets its own chatbot configuration, its own display conditions, and its own model key if you want, while the plugin code lives at the network level. The bot on the marketing subsite reads wp_1_posts, the bot on the docs subsite reads wp_2_posts, and the conversations log into per-blog tables so nothing leaks across subsites.
That subsite isolation matters for regulated networks like university departments, agency white-label setups, and franchise WordPress installs where each location runs as its own subsite. Generic bots cannot enforce that boundary, which is why most network admins block them entirely.
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 a multisite chatbot earns its keep
Universities and departments
Each department runs its own subsite with its own catalog. The bot on the engineering subsite answers about engineering courses without ever touching humanities data.
Franchise and multi-location
Each franchisee subsite has its own hours, menu, and promotions. The local bot reads only local postmeta, so visitors get accurate location-specific answers.
Repeat questions
Answer the questions visitors ask every day from the pages and posts where you already answer them.
How the multisite chatbot fits together
Network-activate SleekAI
Install once on the network, activate from the network admin.
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.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Why multisite-aware chat matters
WordPress multisite powers a long tail of high-value setups: universities with one subsite per department, franchise chains with one subsite per location, agencies hosting dozens of small business clients on a single install. In all of these the boundary between subsites is the whole point.
Mixing data across subsites is not a feature, it is a leak. SleekAI was built with multisite as a first class deployment target. Multisite without this kind of awareness is one bad widget away from a support fire.
Frequently asked questions
How do display conditions work across subsites?
Display conditions are stored per subsite in the chatbot record, and they support all the usual targets: post type, taxonomy term, user role and logged-in state. The active subsite is implicit, so a condition on subsite A never fires on subsite B.
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.
Can I run more than one chatbot?
Yes. Each chatbot has its own instruction, data, display conditions and styling, so different sections of a site can get different bots.
Are conversations stored?
Only if you turn on logging for that chatbot. SleekAI then stores each visitor message and each completed reply, which you read and delete on the chatbot’s Logs page, and a retention period can delete old logs.
Does it handle large amounts of content?
Query results can be synced to OpenAI file search on a schedule, so the chatbot finds the relevant entries instead of sending everything with each request, and a retrieval priority per query or post type ranks what it finds. This needs an OpenAI key and model.
Related pages
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