There are two ways to add a WordPress AI chatbot: install a chatbot plugin, or paste one script tag from a hosted chatbot into your site's footer. A plugin is quicker to find in the dashboard; a script tag adds nothing to your plugin list. This guide compares both, then walks through the snippet method step by step.
Key takeaways
- Decide first where the chatbot lives: inside WordPress (a self-contained plugin with your own AI key) or as a hosted service (a plugin or a script tag that loads it).
- Rylvo has no WordPress plugin. You paste one
<script>tag, most easily with the free WPCode plugin, and that is the whole install. - Train the assistant on your public pages and posts; the crawler follows your links and then fills in from your sitemap.
- Test answers in a separate Test copy before the script goes on the live site. Changes reach visitors only when you release them.
This post is the WordPress chapter of our guide to adding an AI chatbot to any website. Prices were checked on November 17, 2026.
The short answer
If you want the chatbot to run entirely inside WordPress, install a self-contained AI plugin and give it an API key from an AI provider. You manage the prompts, the key, the bill and the updates.
If you want a hosted assistant with its own dashboard, testing and lead inbox, create it on the service first, then put it on WordPress with the service's plugin or by pasting its embed script. With Rylvo it is the script: install WPCode, paste the tag, save. No code to write unless you want page-specific rules.
Plugin vs snippet: the trade-offs
Both end with a chat launcher in the corner. The difference is what you maintain afterwards.
| Chatbot plugin | Pasted script tag | |
|---|---|---|
| Install | Search, install, activate, connect an account or key | Copy one tag, paste it into a footer setting |
| Updates | You update the plugin; a stale plugin can break on a new WordPress release | The service updates the script it serves; nothing to update in WordPress |
| Where settings live | Often in WordPress admin | In the service's dashboard |
| Lock-in | Settings and chat history may sit in your database or the vendor's | Removing the tag removes the chatbot; history stays with the service |
| Page weight | Depends on the plugin; some load assets on every page | One async script; what it downloads depends on the vendor |
| Works on other sites | Only WordPress | Any site that accepts custom code |
Two points from that table are worth checking on any plugin before you install it. First, the "Last updated" date and the "Tested up to" line on its wordpress.org page: the Chatbase plugin listing, for example, was last updated in March 2025, is marked "tested up to" WordPress 6.7.11, and warns that it has not been tested with the latest three major WordPress releases (as of November 2026). Second, whether the plugin is the chatbot or only a connector to a hosted one. Many are connectors, which means you pay the service either way.
WordPress AI chatbot options compared
No ranking: these are different kinds of tool. Facts and prices are from each vendor's own page, checked on November 17, 2026.
| Option | What it is | How AI is paid for | Starts at | Who it suits |
|---|---|---|---|---|
| AI Engine (Meow Apps) | A free plugin that runs chatbots inside WordPress; a Pro version adds features. 90,000+ active installs | You bring a key from OpenAI, Anthropic, Google, Mistral or another provider and pay them directly | Free plugin; AI provider usage is billed by the provider | Site owners comfortable managing an AI key, prompts and plugin updates |
| Tidio | A plugin that connects WordPress to Tidio's hosted live chat and Lyro AI agent | The pricing page says the first 50 Lyro conversations are free (lifetime); after that you buy a Lyro AI Agent add-on with a monthly conversation limit, or move to a plan that bills AI conversations by usage | Free plan; Starter $24.17/mo; Lyro AI Agent add-on from $32.50/mo for 50 conversations | Shops that want live chat and an inbox first, with AI added on |
| Chatbase | A plugin that embeds a chatbot you built on Chatbase, by its chatbot ID | Flat monthly plans with a monthly message-credit allowance (pricing) | Basic $120/mo billed yearly ($150 billed monthly) with 4,000 message credits; extra credits $40 per 1,000 | Teams already using Chatbase |
| Rylvo | No plugin. A hosted assistant you paste in with one script tag | Every paid plan includes AI replies; your own provider key is optional | Free plan; Starter $10/mo (details below) | Small businesses that want the assistant tested before launch, leads captured and answers traceable |
Choosing between hosted platforms rather than plugins? The Chatbase alternative page goes deeper.
What Rylvo costs on WordPress
The WordPress side costs nothing: the snippet needs no paid plugin. The assistant's cost is the Rylvo plan:
| Plan | Price | Agents | AI replies included per month |
|---|---|---|---|
| Free | $0 | 1 | None after the trial; it takes messages instead |
| Starter | $10/month | 1 | About 650 |
| Lite | $40/month | 3 | About 1,300 |
| Pro | $100/month | 25 | About 2,650 |
Starter's $10 is an early price, kept for your first 12 monthly billing cycles; new buyers pay $19 from 31 Jan 2027 or after the first 100 Starter customers, whichever comes first. Extra replies come in packs of 1,000 for $5. A stronger model uses more replies per answer. The "Powered by Rylvo" badge shows on Free only. Every new workspace starts with a 7-day Pro trial with no card, plus 7 more days the first time a customer talks to your assistant. Full details are on pricing, and the wider cost picture is in how much an AI chatbot costs.
The snippet way, step by step
Before you touch WordPress, build the assistant. In Rylvo you paste your website address, review what it found, and get an agent built from your site in Test. It has no test cases yet, so the checklist below is your job. Then open the website channel's Install page and copy the snippet. It looks like this:
<script
src="https://rylvo.com/widget.js"
data-bot-id="YOUR_BOT_ID"
data-widget-token="rwt_..."
async
></script>
data-bot-id names the assistant and data-widget-token is a public site token, scoped to that assistant and to the websites you allow. It is safe to put in page source. Everything the chat looks like (colors, greeting, launcher position) comes from the dashboard, so you will not need to edit this tag again.
On the same Install page, check Allowed websites. When the list is not empty, the widget answers only on those sites. example.com and www.example.com count as the same site, and *.example.com covers subdomains. If you will try it on a staging copy first, add that address too.
With the free WPCode plugin
This is the method the Rylvo dashboard suggests, and a good default for most sites. WPCode (formerly "Insert Headers and Footers") is free and has 3+ million active installs as of November 2026.
- In WordPress admin, go to Plugins → Add New, search for WPCode, then install and activate it.
- Open Code Snippets → Header & Footer.
- Paste the Rylvo snippet into the Footer box.
- Save.
- Open your site in a private window and look for the launcher in the corner. Send a question.
The footer is the right place: the script is async, so it never holds up the rest of the page, and putting it before the closing </body> tag is what the Install page asks for. Because the snippet is stored by WPCode, not in your theme, it survives a theme update or a theme switch.
In a block theme footer, with no plugin
If you would rather not add a plugin, a block theme lets you put the tag straight into the footer:
- Go to Appearance → Editor and open the Footer template part.
- Add a Custom HTML block at the end of the footer and paste the snippet.
- Save.
Two caveats. WordPress only keeps a <script> in that block for users with the unfiltered_html capability: on a single site that is Administrators and Editors (though only Administrators can open the Site Editor), and on Multisite only Super Admins (WordPress roles and capabilities). And the snippet belongs to that theme: switch themes and the chatbot disappears.
A developer can do the same from a child theme, which is safer than editing a parent theme because, as the WordPress child theme handbook puts it, changes to a parent theme disappear the next time it updates:
// In your child theme's functions.php
add_action( 'wp_footer', function () {
?>
<script src="https://rylvo.com/widget.js"
data-bot-id="YOUR_BOT_ID"
data-widget-token="rwt_..."
async></script>
<?php
} );
Only on some pages
You may want the assistant on your pricing and contact pages but not on the blog. Three ways, from simplest to most precise:
- WPCode conditional logic. Skip the Header & Footer box and create a snippet instead: Code Snippets → Add Snippet → Add Custom Snippet, choose the HTML Snippet type, paste the tag, set the location to a site-wide footer, turn on Enable Logic under Smart Conditional Logic and add a Page URL rule such as Contains
/pricing. Page URL, Post type and Type of page rules are in the free plugin; choosing pages by title with the Post/Page picker needs WPCode Pro. Remove the tag from the Header & Footer box first, or it will load everywhere. - A Custom HTML block on the page itself. Paste the snippet at the bottom of just the pages that need it. The same
unfiltered_htmlcaveat applies. - A conditional in the child theme. Wrap the
wp_footercallback in a WordPress conditional tag:
add_action( 'wp_footer', function () {
if ( ! is_page( array( 'pricing', 'contact' ) ) && ! is_front_page() ) {
return;
}
?>
<script src="https://rylvo.com/widget.js"
data-bot-id="YOUR_BOT_ID"
data-widget-token="rwt_..."
async></script>
<?php
} );
To put the chat inside a page instead of a floating button, for example on a support page, tick Show the chat inside the page on the Install page: it adds data-mode="embedded" and data-target="#rylvo-chat" to the tag. Then place an empty <div id="rylvo-chat" style="height:560px"></div> where the chat should appear.
Logged-in customers and WooCommerce
If visitors log in (a WooCommerce shop or a members area), you can tell the assistant who they are so it does not ask for details it already has. The widget's identify() call fills the agent's fields named name, email, phone and company, and any other field of the agent by key inside a fields object:
add_action( 'wp_footer', function () {
if ( ! is_user_logged_in() ) {
return;
}
$user = wp_get_current_user();
$details = array(
'name' => $user->display_name,
'email' => $user->user_email,
);
?>
<script>
window.addEventListener('load', function () {
if (window.RylvoWidget) {
RylvoWidget.identify(<?php echo wp_json_encode( $details ); ?>);
}
});
</script>
<?php
}, 100 );
The assistant treats these details as what the page reported, not as verified facts, and uses them only to decide what to ask. They stay in memory for that page view; they are not written to a cookie, local storage or a URL.
For order questions, the assistant needs a tool, not a page. Rylvo connectors turn an HTTP endpoint into a tool the agent can call, so a developer can expose order status from the WooCommerce REST API behind an endpoint that checks the order number and email. Without that, the assistant answers from your shipping and returns pages and hands order-specific questions to a person. The ecommerce page covers what shops usually set up.
Train it on your WordPress content
The assistant is only as good as what it has read. For a WordPress site, the website itself is the main source:
- Links first, then your sitemap. Rylvo's web crawler starts at the address you give it, follows links on the same site, and respects robots.txt. When it runs out of links it fills the rest of its page budget from the sitemaps robots.txt declares (or
/sitemap.xml), up to 500 listed URLs. A crawl reads 50 pages by default, so list your key pages (services, pricing, FAQ, contact) as separate sources instead of relying on discovery alone. Since WordPress 5.5, core publishes a sitemap index at/wp-sitemap.xmland lists it in the virtual robots.txt (WordPress core announcement). It is not there if "Discourage search engines from indexing this site" is ticked, and Yoast SEO replaces it with its own sitemap. Open/robots.txton your site and check that it has aSitemap:line. - Pick pages, not the whole archive. Service pages, pricing, FAQs, shipping and returns, opening hours and contact details answer most questions. Five years of blog posts mostly add noise and outdated offers. Start narrow and add sections when the traces show a gap.
- Add what is not on the site. Upload price lists, menus or policy documents as PDF, Word, PowerPoint, Excel, CSV, text, Markdown, HTML or JSON. The knowledge base page covers the other sources.
- Keep it fresh. When you publish or change a page, re-sync the source by hand or set it to re-sync on a schedule, so the assistant does not quote last season's prices.
Test it before going live
The common failure is not technical: the launcher works, the answers are wrong, and a customer notices first.
Rylvo keeps a Test copy and a Production copy of every assistant in separate environments. The script on your WordPress site talks to Production. Edits you make in Test reach visitors only when you release them, and you can roll back to an earlier release.
Before you paste the snippet, run through this checklist in Test:
- Ask the 10 questions customers ask most, in the words they use. Check each answer against the page it came from.
- Ask about something you do not offer. The assistant should say so, not invent it.
- Ask for a discount, a guarantee or a delivery date you cannot promise.
- Leave your contact details as a visitor and confirm the lead arrives where you expect.
- Save the questions that matter as test cases so you can re-run them after every change. Starter includes 10 test cases per agent and Lite 50.
- Open the site on a phone and check the launcher does not cover a cookie banner or a "Buy" button.
On Pro, Edge Cases also checks real replies, files each kind of failure once, and helps you fix it in Test and replay the case to confirm the fix; it is part of the 7-day Pro trial. The full pre-launch method is in how to test an AI chatbot before launch.
If the launcher does not appear
| Symptom | Likely cause | Fix |
|---|---|---|
| No launcher at all | A page cache is serving the old page | Clear your caching plugin's and host's cache |
| No launcher, only on optimized pages | A performance plugin delays or combines JavaScript | Exclude widget.js from delay and combine settings |
| Launcher shows, answers are refused | The site is not in Allowed websites | Add the domain (and any staging domain) on the Install page |
| Snippet vanished after a theme change | It lived in the theme's footer | Move it to WPCode |
When a plugin fits better
Choose a self-contained plugin if you want the chatbot entirely inside WordPress, are comfortable managing an AI provider's key and bill, and do not need a separate dashboard for testing or leads. Choose a hosted assistant if you want the model, crawler and updates run for you, with testing and releases in one place. Rylvo is the second kind.
Frequently asked questions
Which AI chatbot plugin should I use for WordPress?
It depends on where you want the chatbot to live. If you want everything inside WordPress and are happy to manage your own AI provider key, a self-contained plugin such as AI Engine fits. If you want a hosted service with an inbox, testing and lead capture, use that service's plugin or paste its script tag. Compare who maintains it, how AI usage is billed and how you test answers before visitors see them.
Can I add a chatbot to WordPress without a plugin?
Yes. A hosted chatbot is one script tag. On a block theme an administrator can paste it into a Custom HTML block in the Footer template part, or a developer can print it from a child theme with the wp_footer hook. Many sites use the free WPCode plugin because it keeps the snippet safe across theme changes.
Is a WordPress chatbot free?
Some plugins are free to install, but the AI behind them is not: you pay either an AI provider directly or the chatbot service. Rylvo has a Free plan for 1 agent, and new workspaces get a 7-day Pro trial. After the trial Free has no AI replies and takes messages instead. Paid plans start at $10 a month and include AI replies.
Will an AI chatbot slow down my WordPress site?
Rylvo's loader is one async script, so it does not block the page, and in the default floating mode the chat app itself downloads only when a visitor first opens the panel. The loader still makes one request for your widget settings on page load. To check your own site, run PageSpeed Insights on a page before and after adding the tag. If a performance plugin delays or combines JavaScript, exclude the widget script so the launcher appears on time.
Does it work with WooCommerce?
The widget runs on WooCommerce pages like any other page, and the assistant can answer from your product and policy pages once they are in its knowledge. There is no WooCommerce integration that reads orders by itself. For order status you connect an HTTP endpoint as a tool, for example one built on the WooCommerce REST API.
