Adding a chatbot to WordPress takes about three minutes. Go to Plugins then Add New Plugin, search your chatbot platform's name, click Install Now and Activate, then paste your chatbot ID into the plugin settings.
The part that takes longer, and the part that decides whether the chatbot is any good, is training it on your content first.
iShort answer
Use the plugin method when the plugin is currently maintained, because it survives theme changes. Use the manual embed when it is not, and check the Last updated field on WordPress.org before you decide. Train the chatbot before you install anything, because an untrained widget on a live site answers nothing. Budget three minutes for the install and about half an hour in total.
Steps 1 and 6 are the ones people skip, and they are the two that decide whether the chatbot is worth having.
Train it first
Point the platform at your site, then add the PDFs and help articles your posts do not cover.
Check the plugin is alive
Read Last updated and Tested up to on WordPress.org before installing anything.
Install and activate
Plugins, then Add New Plugin, search, Install Now, Activate. No code.
Paste the chatbot ID
Copy it from your dashboard into the plugin settings field, then save.
Verify on the front end
Private window, ask a question you know the answer to, check the console.
Set branding and escalation
Match your theme, and decide where a question the bot cannot answer goes.
Before you install anything
Two decisions come first, and both are easier to make now than to undo later.
Train the chatbot before it goes on the site. A widget installed before training answers nothing, and visitors who get a blank answer on day one do not come back to try again. Build and train it on the platform, test it there, then install.
Check the plugin is currently maintained. Open the plugin's page on WordPress.org and read two fields in the right-hand sidebar: Last updated and Tested up to. This takes ten seconds and it decides which of the two methods below you should use.
This matters more than it sounds. Several widely recommended chatbot platforms ship WordPress plugins that have not been touched in over a year, and WordPress.org puts a warning banner on the listing when that happens.
Which plugins are current, and which are not, is ranked on directory data in best chatbot for WordPress website.
Method 1: the plugin, about three minutes
This is the route to use when the plugin is maintained. It needs no code and it survives a theme change.
Step 1: Install the plugin
Log in to your WordPress admin and go to Plugins then Add New Plugin. Search for your chatbot platform by name. Click Install Now, then Activate once it finishes.
If your platform is not in the directory, download its ZIP file and use Plugins then Add New Plugin then Upload Plugin instead.
Step 2: Find the settings
Most connector plugins add their settings under Settings in the admin sidebar. Some add their own top-level menu entry. If you cannot find it, the Plugins list shows a Settings link under the plugin name.
Step 3: Paste your chatbot ID
Copy the chatbot ID or API key from your platform dashboard, paste it into the plugin's field, and save. That is the only configuration most connector plugins need, because the appearance is controlled from the platform rather than from WordPress.
Method 2: the manual embed
Use this when the plugin is stale, when the vendor does not publish one, or when you want direct control over which pages load the widget.
Step 1: Copy the embed snippet
Every hosted chatbot platform gives you a script tag from its dashboard, usually under a heading like Embed, Install, or Share. It is one line and it loads asynchronously.
Step 2: Add it through a code-snippets plugin
Install a snippets plugin such as WPCode, create a new snippet, set its location to site footer, and paste the script in. Save and activate it.
Do not paste the script directly into a theme file. A theme update overwrites it, and you will spend an afternoon working out why the widget disappeared.
Step 3: Restrict it to specific pages if you need to
A snippets plugin lets you set conditional logic, so you can run the widget only on your documentation, only on product pages, or everywhere except checkout. This is the main advantage the manual route has over a connector plugin.
How to train the chatbot on your WordPress content
Pointing a platform at your site URL or sitemap crawls your published pages. That covers your posts and pages, and for many sites it is enough.
It misses everything that is not published as HTML. If your real answers live in PDFs, a help center, or internal documents, a site crawl alone produces a chatbot that confidently knows your blog and nothing else.
Add those sources separately. On SiteGPT that means 12+ source types: your website and sitemaps, file uploads, Google Drive, Notion, Dropbox, OneDrive, SharePoint, Box, GitHub, and YouTube. Help centers from Zendesk, Freshdesk, Intercom, Confluence, and Gitbook connect too.
Two settings are worth getting right while you are here.
Auto-sync. Content changes and a chatbot trained on last quarter's pricing page will quote last quarter's prices. Auto-sync re-reads your sources on a schedule. On SiteGPT that is monthly on Growth and weekly with a daily scan on Scale.
What it does when it does not know. A chatbot that guesses is worse than one that says it cannot help. Grounding the bot in your content is what stops it inventing answers, and setting up escalation gives the visitor somewhere to go when it genuinely cannot answer.
Verify it actually works
Do not check from the tab you have been working in. Open your site in a private window, because a logged-in admin session and a cached browser both hide problems a real visitor would hit.
Then run four checks:
- The bubble appears in the position you set, on a page you expect it on.
- It answers a question you know the answer to. Ask something specific from a page you trained it on, not "hello".
- The console is clean. Open your browser developer tools and check for errors mentioning the widget script.
- Escalation reaches you. Ask to speak to a person and confirm the notification actually arrives.
The fourth is the one people skip, and it is the one that matters when a real customer hits a question the bot cannot answer.
When the widget does not appear
Four causes account for almost every case.
| Scenario | Best pick | Why |
|---|---|---|
| Widget missing for visitors, visible for you | Purge the cache | A caching plugin or CDN is serving a copy of the page from before you added the widget. |
| Nothing appears at all, no console error | Re-copy the chatbot ID | A trailing space or a partial copy is the most common cause, and it fails silently. |
| Appears only after clicking Accept | Nothing, this is correct | Your consent banner is holding third-party scripts until the visitor consents, which is what it is for. |
| Worked, then stopped after a speed plugin | Exclude the widget script | Deferring or combining JavaScript breaks async third-party widgets. Add it to the optimization exclusion list. |
If none of those apply, check that the plugin is actually activated, and that your theme calls wp_footer(). A theme missing that hook stops any footer-injected script from loading, which affects far more than chatbots.
Frequently asked questions
How long does it take to add a chatbot to WordPress?
Installing and connecting the plugin takes about three minutes. Training takes longer and is the part that decides whether the chatbot is useful, usually 10 to 30 minutes depending on how much content you point it at.
Budget half an hour in total for a site you want to launch the same day.
Do I need to know how to code?
No. The plugin method needs no code: install, activate, paste an ID, save. The manual embed needs one script tag pasted into a form field.
Neither route requires editing a theme file, and you should avoid editing theme files because a theme update overwrites direct edits.
How do I add a chatbot to WordPress without a plugin?
Copy the embed snippet from your platform and add it to your site footer using a code-snippets plugin such as WPCode. The snippet is a single script tag that loads asynchronously.
This route is the right one when a vendor's plugin has not been updated recently.
How do I train an AI chatbot on my WordPress content?
Point the platform at your site URL or sitemap and it crawls your published pages. Add PDFs, help center articles, and documents separately if the real answers live there.
On SiteGPT you can also connect Google Drive, Notion, Dropbox, OneDrive, SharePoint, Box, GitHub, and YouTube. Auto-sync re-reads them on a schedule.
Why is my chatbot not showing on my WordPress site?
Purge your cache first, because that is the most common cause. Then re-copy the chatbot ID in case it picked up a trailing space.
Check whether a consent banner is holding the script until the visitor accepts. That behavior is correct. Finally, exclude the widget script from any JavaScript optimization plugin.
Can I add a chatbot to a specific page only?
Yes. Most platforms let you restrict which domains and paths the widget appears on from the dashboard. With the manual embed you control it directly, because a snippets plugin lets you set conditional logic per page.