Get the instructions from the correct site.
Open the website’s installation page in your Sairo workspace. Check the published origin and copy the values shown for that site. Each website has its own verification token.
The public site key used by the widget, the ownership verification token, and an AI provider API key have different purposes. Use the verification value from the installation page; never substitute a provider credential.
Option one: publish the TXT record.
Create a TXT record at one of the DNS names shown in Sairo. The instructions offer the domain’s base name or the _sairo label under it, with a value beginning sairo-site-verification= followed by the site’s token.
DNS dashboards differ in whether the name field expects a short label or a complete hostname. Check the resulting fully qualified name so the domain is not accidentally appended twice. Add a separate record rather than replacing unrelated mail or verification records.
Type: TXT
Name: _sairo.example.com
Value: sairo-site-verification=YOUR_VERIFICATION_TOKENOption two: publish the verification file.
Create the text file at /.well-known/sairo-verify.txt on the exact website origin shown in Sairo. Its contents should be the token supplied by the installation page. The checker expects a successful response containing that value, with surrounding whitespace ignored.
Open the file URL and inspect the response. A branded error page, a homepage rewrite, or a login screen at that path does not prove ownership, even if the browser shows a page successfully.
https://example.com/.well-known/sairo-verify.txt
File contents:
YOUR_VERIFICATION_TOKENRun the check and then request a refresh.
After publishing one of the proofs, return to the installation page and choose Check verification. Sairo checks the file and DNS methods and records the result.
Successful verification permits production crawling; it does not mean all pages have already been indexed. Request a website refresh and inspect the resulting crawl and source list. The workspace must be active and its allowances must support the work.
Get your assistant live. Verify, install, and test your first website assistant.
Before you start: Start with a workspace and a website already added. The workspace, visitors and figures shown are fictional examples.
Read the transcript
- Your website. Ready to help.
Already created your workspace and added your website? Let's get your Sairo assistant live.
- Open Get started
Open Get started in the sidebar. Your setup checklist keeps verification, indexing, installation, and testing in one place.
- Verify ownership
Add the supplied verification file to your website, or use the DNS record. Then select Check verification. Ownership must be verified before indexing.
- Index your pages
Select Refresh website content. Sairo reads the verified website and prepares its knowledge. The next step appears when indexing finishes.
- Copy. Add. Publish.
Copy your unique snippet. Add it before the closing body tag, or in your website builder's global custom-code area. Publish, then confirm that you've added it.
- Ask a real question
Open your website and select Ask a question. Try something visitors actually ask, such as: Do you offer free inspections? Then send it.
- Check the answer
Read the answer and its source. In this example, the reply confirms free residential inspections in Franklin County. Test your own important questions too.
- Your first answer, ready for visitors.
Your assistant is ready for a first conversation. Next, keep its answers accurate with confirmed knowledge.
Match a failed check to its likely cause.
For DNS, confirm the published name, the complete token, and whether the change is visible beyond the provider’s dashboard. DNS changes can take time to become visible, so avoid repeatedly replacing a correct record.
For a file, confirm the exact path, hostname, response status, and contents. Check whether the host redirects the path or serves an HTML fallback. If an agency or host controls the website, send the exact Sairo instructions to that maintainer.
| Mistake | Correction |
|---|---|
| Using the widget’s public site key | Copy the separate ownership token from the installation page. |
| Appending the DNS domain twice | Check the full published record name. |
| Publishing a token for another site | Reopen the intended website’s instructions. |
| A verification path shows the homepage | Serve the actual text file at the exact path. |
| Assuming verification completes indexing | Request a refresh and review the crawl separately. |
Revisit the setup when the domain changes.
A new domain can affect website identity, the allowed browser origin, the script’s placement, and ownership verification. Ask an authorised administrator to review the complete site configuration.
Keep a record of who controls the domain and the website deployment. This makes later maintenance easier without treating access to a CMS editor as proof of every related administrative permission.