What SuperBot does on Custom Website
Have a hand-built site (Next.js, Astro, Hugo, plain HTML)? SuperBot is a single drop-in snippet that adds a real AI customer-support agent without imposing any framework opinions — just one line, no SDK, no build step.
- Framework-agnostic: works with Next.js, Remix, Astro, Hugo, Eleventy, plain HTML, anything.
- No SDK, no npm package, no build-step changes. Just one async <script> tag.
- Grounded in your real content through public URL fetches and pasted text.
- Custom or removable badge branding on Starter and Pro keeps your design fully yours.
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 Custom Website
Immediately before the closing </body> tag of your base HTML template or layout.
- Sign up for SuperBot free.
- Add your site URL — SuperBot crawls your pages and policy content.
- Paste one snippet (a <script> tag) into your HTML <head> or just before </body>.
- Approve the first cited replies, set handoff rules, customize the widget.
- Deploy — SuperBot is live across every page.
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 strict Content-Security-Policy needs script-src and connect-src entries for superbotapp.ai.
- Single-page apps should include the snippet in the shell template so it survives client-side navigation.
- If your framework hydrates late, keep the snippet in the HTML rather than injecting it after hydration.
- 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.