🔍 Understand the UUID warning
OTTO uses a unique identifier, or UUID, to connect your website’s Cloudflare setup to the correct Search Atlas project. A “wrong UUID” message does not always mean the UUID shown in your website header is incorrect.
Depending on the installation method, the UUID may be stored in a Cloudflare Worker, environment variable, route, or configuration field. It may not appear directly in the page source or header code that you inspect in your browser.
🧭 Check the installation location
- Open AI SEO → OTTO SEO from the left sidebar.
- Open the relevant OTTO installation or project settings.
- Copy the UUID displayed by Search Atlas. Compare the complete value, including every letter, number, and hyphen.
- In Cloudflare, open the account and zone connected to the website.
- Check the OTTO Worker, its environment variables, routes, and any associated configuration for the same UUID.
Do not compare the UUID only with visible header code. The browser may show a loader or script while the actual UUID is passed through the Worker configuration.
⚙️ Verify Cloudflare configuration
- Confirm that you are viewing the correct Cloudflare account and website zone.
- Check that the Worker is deployed and assigned to the intended route.
- Confirm that the route matches the live domain and does not point to a staging or alternate hostname.
- Review Worker variables and replace any outdated UUID with the current value from Search Atlas.
- Save the configuration and redeploy the Worker after making changes.
- Check that Cloudflare is not blocking the Worker because of account, zone, security, or plan restrictions.
🧪 Test the connection
- Open the live website in a private browser window.
- Test the exact domain and URL where OTTO is installed.
- Use the browser’s developer tools to check the Network and Console tabs for failed Worker requests or connection errors.
- Return to AI SEO → OTTO SEO and run the available scan or connection check.
If the UUID matches but the warning remains, avoid repeatedly creating new Cloudflare tokens or changing unrelated settings. Repeated token creation does not correct a UUID that is being read from a different Worker setting or route.
🚧 Know the current limitation
OTTO Pixel’s Cloudflare Worker setup can sometimes show a generic connection error even when token permissions appear correct. In these cases, the available message may not identify whether the issue is caused by the Search Atlas integration or a Cloudflare-side restriction.
Without a specific backend error or a confirmed account or zone configuration issue, the warning cannot always be diagnosed from the visible header code alone. Record the affected domain, Cloudflare account and zone, Worker name, route, and the exact error message before requesting help.
💬 Get help with unresolved errors
If the UUID matches in Search Atlas and Cloudflare, the Worker is deployed on the correct route, and the connection still fails, further investigation may be required. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be instantly connected with a member of our team.