Embedding the Simple Agent Widget: A Script-Tag Checklist for Website Owners
Adding an AI agent to your site should not require a server migration or a developer ticket. Simple Agent is designed to be a script tag chatbot: you paste one <script> tag into your site, and the widget appears for visitors. No backend changes, no API calls to wire up, and no theme files to rewrite.
This checklist walks through a safe, repeatable website widget setup from placement to quality checks.
Choosing the right place for the script tag in your site layout
Where you put the script matters more than how long it is. The Simple Agent widget script is currently measured at 18.56 KiB gzip, so it is small, but you still want it to load without blocking the rest of your page.
Best practice placement:
- Add the script just before the closing
</body>tag. - Keep it in the main site template or footer file so it loads on every page that uses the template.
- If your platform lets you inject code into the footer, use that instead of editing individual pages.
Loading behavior:
- Use the
asyncattribute so the script downloads in parallel and does not pause HTML parsing. - Avoid placing it in the
<head>unless your platform gives you no other option. Even a small script in the head can delay first paint. - Only add the script once per page. Duplicate tags can cause the widget to initialize twice or create conflicting event listeners.
Single page versus site-wide:
- For a multi-page site, place the tag in the shared footer so the chat widget is available everywhere.
- For a landing page or a specific support page, paste the tag only into that page’s HTML or page template.
- If you run a single-page application, the verified behavior is the same standard script-tag install, but you should confirm the widget re-initializes correctly after client-side route changes. General guidance is to load the script after the route has mounted, then test navigation between views.
Platform-specific note for WordPress:
If you use WordPress, the verified approach is to paste the script into a Custom HTML widget, a footer-code injection area, or a trusted code-management plugin. Simple Agent does not ship a dedicated WordPress plugin, so the script tag is the supported installation method. You can find platform notes on the WordPress setup page.
Configuring page-level visibility and when the widget should appear
The Simple Agent widget appears on every page that includes the script. That makes visibility easy to control: include the tag where you want it, and leave it out where you do not.
Page-level control:
- Add the script to your global footer if the agent should be available everywhere.
- Add it to a specific page template if it should only appear on pricing, support, or documentation pages.
- Do not rely on CSS alone to hide the widget on unwanted pages. Hiding it with
display: nonemay stop it from rendering, but the script can still load and initialize, which wastes a request and can affect your plan usage.
When the widget appears:
- By default, the widget renders as soon as the script loads and the DOM is ready.
- If your site delays third-party scripts for performance or cookie-consent reasons, place the Simple Agent script in the same consent tier you would use for analytics or support tools.
- Test on mobile viewports. The widget is responsive, but you should confirm it does not cover critical buttons or navigation on small screens.
Verifying that the widget loads, renders, and shows your agent branding
After you save the script, open the page in a browser and look for the chat bubble or launcher. If it does not appear, work through these checks.
Visual verification:
- The widget should load within a normal page render cycle. Because the script is only 18.56 KiB gzip, it should not cause a noticeable delay on a typical connection.
- Check that the launcher color, header text, avatar, and welcome message match your agent settings. If you see generic branding, the script may be pointing to the wrong agent ID.
- Open the chat panel and confirm it does not break your page layout, especially on pages with fixed headers or full-width banners.
Browser console checks:
- Open Developer Tools and look for JavaScript errors tied to the Simple Agent script.
- In the Network tab, confirm the script returns a
200status and that no content blocker is intercepting it. - Resize the browser and check that the widget repositions correctly.
Branding and source audit:
To audit your actual branding and sources, you must view your own configured agent on your own site. See the Simple Agent plans.
Checking plan allowances and what to monitor as visitor traffic grows
One of the honest differences with Simple Agent is predictable plan allowances rather than per-response credits. You know what your plan includes, so you are not guessing how many credits a long conversation consumed.
What to monitor:
- Conversation volume over a week or month, depending on your billing cycle.
- The number of pages or sites where the widget is installed, if your plan has scope limits.
- Any spike in traffic after a campaign, product launch, or support announcement.
How to stay ahead of limits:
- Check your dashboard regularly against your plan allowance.
- If you are approaching the limit, upgrade before you hit the cap so visitors do not see an interrupted experience.
- Avoid installing the script on staging or internal pages that receive public traffic unless you want those visits counted.
For a clear view of what each plan includes, visit the pricing page.
Running test conversations to confirm answer quality before going live
A working widget is not enough. You also need to trust the answers it gives. Before you announce the agent to customers, run a short conversation audit.
Start with your top questions:
- Ask the three questions your support team answers most often.
- Ask a question that only appears deep in your documentation.
- Ask something ambiguous to see how the agent handles clarification.
Check for source citations:
When the agent retrieves source material from your knowledge base, Simple Agent shows chunk-level source citations that point to the specific section the answer came from. If you ask a detailed question and see those citations, you can be confident your content is being used correctly. If the answer has no citation, it may be relying on general behavior or missing the right document.
Test on your own content:
To confirm answer quality for your business, install the widget on a private or staging page connected to your configured agent. See the Simple Agent plans.
Invite a second reviewer:
Have a teammate or a non-technical colleague run the same questions. They will spot confusing phrasing or answers that assume too much domain knowledge.
Ready to embed your AI agent?
A script tag is the only install step. Place it at the bottom of your pages, confirm the widget loads and matches your brand, monitor your plan as traffic grows, and run a short conversation audit before you go live.
When you are ready, pick a plan on the pricing page and get your embed code.
Ready to build your AI agent?
Guided setup in 90 seconds. One flat price, published monthly volume.
Create my agent