Train the chatbot on your site without a crawler
SleekAI adds an AI chatbot for Site-Trained Chatbot 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.
Answers from your own WordPress content
Every site-trained chatbot vendor uses the same playbook. They take your sitemap, hand it to a headless browser, render each page, parse the HTML, and try to guess which parts are the real content and which parts are the header, footer, sidebar, cookie banner, and chat widget.
The guess works for some pages and fails for others, especially on builder-heavy sites where the markup is dense and the content lives inside several layers of containers. Once it fails, the bot is happily training on your nav menu.
SleekAI does not need to guess because it reads the database. A post is its post_content field. A category page is its term and the posts tagged with it. The plugin sees the same fields your theme reads when rendering, so the bot trains on the real source rather than the rendered output.
This also means no separate crawler infrastructure, no robots.txt edits, no whitelisting of vendor IPs, no waiting for a daily crawl to pick up an edit. A new product appears in the index the moment it is published. A taxonomy change is reflected immediately.
The site does not need to be public for the bot to train on it because the bot does not fetch over HTTP. It reads the database that already powers the front end, which is the only source of truth that matters.
Features
Database-direct training
No crawler, no rendering, no scraping. The bot trains on the same data your theme reads at request time.
Scoped training
Choose exactly which post types, meta fields, and taxonomies to include. Exclude noisy auto-generated archives or low-quality content from the index without making them harder to find through normal search.
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.
Where site training is the right shape
Mid-sized content sites
Hundreds or thousands of posts across multiple categories.
E-commerce product catalogs
Hundreds of products with titles, descriptions, and structured meta. The bot trains on product fields directly so attribute questions land on actual data, not on whatever the description happened to mention.
Course and member portals
Members-only content does not need a public URL.
How site training works without a crawler
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
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.
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Scope per bot
Multibot lets you run multiple bots on the same site with different training scopes. A marketing bot reads pages and case studies, a help bot reads docs, an internal bot reads private CPTs. Same data, different lenses.
Why site training without a crawler is the right default
As soon as the chatbot lives inside the CMS, the question changes. Reading the database is faster, fresher, more accurate, and avoids an entire class of integration problems. It is also more honest about what the bot is training on. A database-direct read sees the product’s title, description, and price fields.
Frequently asked questions
Why no crawler?
SleekAI is a WordPress plugin, so it has direct access to the same tables your theme reads.
Can I exclude specific posts or sections?
Yes. The Variables tab lets you exclude posts by ID, exclude posts in a given taxonomy term, or set a meta flag like sleek_exclude_from_chat. Common exclusions are auto-generated archives, ancient changelog entries, and pages that only exist for SEO redirects.
Does it work on staging without a public URL?
Yes. Because there is no crawler, SleekAI does not need to fetch your URLs. As long as the database is populated, the bot can train on staging content. This is useful for previewing how a bot will behave on new content before that content goes live in production.
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.
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.
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