Check the code-injection feature first.
Squarespace currently documents code injection for Core, Plus, Advanced, and some legacy plans. Confirm access on the actual subscription rather than assuming every site can add JavaScript.
The Footer injection field places code before the page’s closing body tag. Squarespace also notes that checkout pages do not support this code, and that scripts can be disabled in the editing preview.
Source references
Prepare the website’s knowledge.
Verify the published origin in Sairo and inspect the source list. For a portfolio or service business, confirm that the crawl has readable service descriptions and contact details rather than relying on image captions alone.
Decide who reviews enquiries and unanswered questions. A simple public website can still need a clear human process when a visitor asks for a custom quote or unpublished availability.
Put the snippet in the Footer field.
Open the Code Injection panel, preserve any existing entries, and add the site’s Sairo snippet to Footer. Save the change and inspect the public website.
Use one installation point. If you are piloting only selected pages, have the site maintainer choose the correct page scope and check it explicitly rather than combining overlapping global and page entries.
<script src="https://sairo.app/widget.js" data-site="YOUR_PUBLIC_SITE_KEY" async></script>Source references
Review the experience outside the editor.
Open the published domain as a visitor and navigate between the intended pages. If the widget is absent only in the editor, check the editor’s script setting before assuming the installation has failed.
Test the launcher beside appointment links, newsletter forms, sticky navigation, and consent controls. Ask a supported question, then an unsupported one, and inspect the conversation in Sairo.
Example for a professional portfolio
The assistant can explain the published process and invite a visitor to share a project enquiry. It should not confirm a project start date unless the available sources actually establish it.
Keep the site and assistant aligned.
Review the installation after a redesign or navigation change. A working script may still need a layout check if a new fixed button occupies the same part of the screen.
When services, contact details, or policies change, update the source website and the relevant confirmed facts or saved answers, then refresh and retest. Placement and answer accuracy are separate maintenance tasks.