Add Sairo to your WordPress website.

WordPress.com limits the code available on different plans. Its documentation allows JavaScript on plugin-enabled sites with the relevant hosting features activated. A free site’s HTML support does not imply that a third-party script can run.

For a self-hosted WordPress installation, check the permissions and code-insertion method supplied by your administrator or host. A page editor that displays code for readers is different from a location that executes a script.

Add the published website origin to the correct Sairo workspace, verify ownership, and review the indexed sources. Prioritise service pages, contact information, and any policies a visitor is likely to ask about.

If an agency manages several WordPress sites, keep each client in the intended project. Copy the snippet from this site’s installation page so the key selects the right assistant.

<script src="https://sairo.app/widget.js" data-site="YOUR_PUBLIC_SITE_KEY" async></script>

Choose an approved header/footer insertion tool, an appropriate shared template location, or a developer-maintained theme integration. WordPress.com documents code blocks and plugin-based approaches according to plan capability.

For Sairo, place the generated snippet near the end of the page body where your chosen method supports it. Record where you installed it. Adding the same snippet through both a theme and an insertion tool can create confusing duplicate loads.

1. Save the existing configuration

   Keep the original code or revision so the change can be undone without affecting other scripts.

2. Add the site-specific snippet

   Retain its source URL, public site key, and async attribute.

3. Publish and clear applicable caches

   Check the visitor-facing page rather than assuming the editor view reflects the installation.

Inspect a service page, a long page, and the narrow-screen layout. Confirm that the launcher does not cover a consent control, sticky call button, or form. Use a keyboard to open the panel, ask a question, and close it.

Ask a question supported by a source, one the site cannot answer, and one requesting a person. Use a contact address your team controls to test lead collection, then verify the record in the correct workspace.

Check whether the published page contains the script, whether its request succeeds, and whether a consent manager or content security policy blocks it. If a performance plugin changes script loading, test that interaction in a controlled preview before changing the visitor experience.

When changing themes or moving hosts, check the insertion point again. The knowledge belongs to the configured Sairo site, but the website still needs to load the matching snippet.