Home 🤖 OTTO SEO 🔍 Fix OTTO Not Connected on Static HTML

🔍 Fix OTTO Not Connected on Static HTML

Last updated on Oct 29, 2026

🔍 Why OTTO still shows not connected

OTTO only shows as connected after it can load its script on the live public page for the domain in your project. Pasting the script into a local index.html file is not enough if that file is not the page visitors (and OTTO) actually open.

A not-connected status usually means the script is missing from the served HTML, blocked before it runs, or present on a different URL than the one being checked.

📄 Place the script on the page that is served

  1. In Search Atlas, open your OTTO project and copy the install script exactly as shown. Do not rewrite or shorten it.
  2. Open the HTML file that your host serves for the site root. On many static sites that file is index.html, but your host may use another file or a build output folder.
  3. Paste the script inside the head of that file, before the closing head tag. Keep it on its own so it is easy to find later.
  4. Save, then publish or deploy the site. Editing a copy on your computer does not update the live site until you upload or redeploy.
  5. Open the exact domain from your OTTO project in a browser, including the correct www or non-www version and https.

If your site is generated from a template or build step, add the script to the source template and rebuild. Putting it only in a local preview file will not connect OTTO.

🛠️ What to look for in Inspect

On the live homepage, right-click the page and choose Inspect (or View Page Source). Check these items in order:

  • Elements or Page Source: Search for the OTTO script. You should see the same script tag you copied, inside the head of the HTML that the browser received. If it is missing, the live file was not updated.
  • Network: Reload the page, filter by the script name or by JS, and find the OTTO script request. A successful load shows status 200. Status 404 means the address is wrong or the file was changed. (blocked) or a failed request means a browser extension, firewall, or content rule stopped it.
  • Console: Look for red errors that mention the OTTO script, a blocked request, or a content-security-policy violation. Those errors explain why the tag is present but OTTO still stays disconnected.
  • Correct page: Confirm the address bar matches the domain in OTTO. A script on index.html for one domain will not connect a project set to another domain or to a page you have not published.

View Page Source shows the HTML from the server. The Elements panel can also show changes made by other scripts. If the tag is only in Elements and not in Page Source, another tool injected it after load, which is not a reliable install.

⚙️ Common reasons a static site stays disconnected

  • The script was saved locally but never uploaded to the host or redeployed from your static-site builder.
  • You edited index.html in the project folder, while the host serves a built copy from a dist, public, or build folder.
  • The tag sits in the body, is commented out, or was split across lines so the browser cannot read it.
  • An old cached copy is still being served. Hard-refresh the page, then purge your host or CDN cache and check again in a private window.
  • An ad blocker or privacy extension blocks the script. Test in a private window with extensions off.
  • A content security policy on the host allows only approved script sources, so the browser refuses the OTTO file.
  • The project domain uses www and the live site does not, or the opposite. Match the domain exactly.

✅ Confirm the connection

  1. Reload the live homepage after the deploy and cache clear.
  2. In Inspect, confirm the script is in the served head and its network request returns 200 with no console error.
  3. Return to OTTO and refresh the installation or connection status.
  4. Wait a short time and check again. Posting and other OTTO actions stay unavailable until the status shows connected.

Once the script loads on the live domain, content actions that were blocked by the not-connected state can run. If posting still fails after the status is connected, note the exact page URL and the error on screen before you contact support.

💬 Get help in the platform

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.