What SuperBot does on WordPress
SuperBot adds a real customer-support AI agent to any WordPress site — WooCommerce stores, business sites, agencies, services. Grounded in your live content, multilingual out of the box, with a human handoff that arrives with full context.
- Works with any theme, any builder (Elementor, Divi, Gutenberg, Beaver Builder).
- Reads your WordPress posts, pages, and WooCommerce products as a single knowledge base.
- Multilingual replies across 35 widget languages — useful for WordPress sites running WPML or Polylang.
- Lead capture routes to WordPress admin email, WP Forms, Gravity Forms, or external CRMs.
Before you install
The quality of the first answers depends on what a visitor can already read on your site, so publish your current shipping, returns, and contact information before training the agent. Have your site URL and one test page ready.
- Use the site that should be connected to this SuperBot workspace, not a staging copy.
- Check that your policy and product pages are written for customers rather than internal staff.
- Decide where escalations should land: the SuperBot inbox, Slack, or your existing support process.
- Copy the exact snippet from your SuperBot dashboard so the site ID routes conversations to the right workspace.
Install SuperBot on WordPress
The SuperBot plugin's settings page, or a snippet added before the closing body tag in your theme's footer template. Purge any caching plugin (and your host's cache) so visitors are served the updated page.
- Sign up for SuperBot free.
- Add your WordPress site URL — SuperBot crawls pages, posts, and any active product catalog.
- Install the SuperBot WordPress plugin, or paste a single snippet into your theme's footer.
- Approve the agent's first cited replies and set handoff rules.
- Publish — SuperBot is live across your WordPress site.
Check that it is live
Open your site in a private window rather than the editor or preview, because most platforms only serve custom code on the published site. The launcher should appear in the lower corner within a second or two.
- Load a real published URL, not an editor preview or a password-protected page.
- Open the launcher and send a question you know the answer to, then confirm the reply cites your own content.
- Check one product or interior page as well as the home page, since templates can differ.
- If you run several languages or store views, check one page in each.
If the widget does not appear
Almost every failed install is one of four things: the change was never published, a cache is still serving the old page, the snippet carries the wrong site ID, or another script is stripping it.
- A caching or optimisation plugin may strip, defer, or combine the script — exclude SuperBot from JS optimisation if the launcher does not appear.
- Editing a parent theme's footer means an update can overwrite it; use the plugin or a child theme.
- Some security plugins block inline scripts for non-admin visitors, so check in a logged-out private window.
- Open your browser console and look for a blocked request to superbotapp.ai, which points at a Content-Security-Policy or an ad blocker.
- Confirm the site ID in the snippet matches the workspace you are looking at in the dashboard.
Train and test before you send traffic
Approve a small, representative set of answers before the widget meets real customers. Test the questions that normally create tickets or stop a purchase, and correct the wording once so every later answer inherits it.
- Start with the ten questions your team answers most often.
- Check that policy answers link to the live page that supports them.
- Add a trained answer for anything the agent gets wrong rather than editing the source page twice.
- Decide what should escalate immediately — refunds, complaints, anything account-specific.