Check custom-code access.
Webflow provides custom code at site and page level, subject to the site or workspace’s access. Check that the person making the change can use the relevant settings.
The site-level Footer code area places code before the closing body tag. Page-level code applies only to that page. Use the official instructions for the current interface and publish after saving.
Source references
Decide where visitors should see the assistant.
A shared installation is useful when the same assistant should appear across a company’s public site. A smaller pilot can focus on one high-value service or information page before the rollout expands.
The pages displaying the widget and the pages indexed as knowledge are separate decisions. Review the source list in Sairo rather than assuming that placement on a page automatically adds all of its content to the knowledge base.
Add the generated snippet.
Verify the website in Sairo and copy its installation snippet. For a site-wide setup, open Site settings, choose Custom code, and add the snippet to Footer code. Save and publish the site to the intended domain.
Keep the existing scripts intact and install Sairo once. Do not wrap the snippet in another HTML document or add a second copy at page level when it is already loaded globally.
<script src="https://sairo.app/widget.js" data-site="YOUR_PUBLIC_SITE_KEY" async></script>Source references
Review the content, including CMS-generated pages.
Test an important collection page as well as the homepage. Confirm that the published information is readable to the crawler and that old collection items are not supplying outdated prices or conditions.
If separate client sites use the same Webflow design, they still need their own Sairo site keys and source boundaries. Duplicating a website template should not duplicate a production client’s assistant identity.
Example pilot
An agency can start on a service page, test questions about that service, review the resulting conversations, and expand the placement after the client approves the answers and follow-up process.
Check the visitor experience after publishing.
Open the public domain and navigate between the pages in your chosen scope. Check for a single launcher, correct branding, useful keyboard focus, and a working response. Inspect mobile navigation and any fixed page elements alongside the widget.
If the launcher appears but the answer is poor, check indexed knowledge before moving the script. If no launcher appears, check the deployed code, loading request, browser errors, and consent or security controls.