🛠️ Fix OTTO Connection Stuck in Processing or Crawling

Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 What This Issue Looks Like

After installing the OTTO script on your website and attempting to connect your site, the connection process does not complete. The status remains stuck — either in a processing or crawling state — even after waiting several hours or days. The site never fully activates in OTTO.

⚠️ Why This Happens

In some cases, OTTO's background crawl process can stop silently without returning an error message. The platform appears to be working, but the crawl has actually stalled internally. This is a known issue that has been identified and addressed by the Search Atlas engineering team. However, if your site is currently stuck, the steps below can help you resolve it.

✅ How to Fix It

  1. Remove the OTTO script from your website. Log in to your website's backend and delete the OTTO script that was installed during the connection setup.
  2. Delete the existing OTTO project. In the Search Atlas platform, go to Left sidebar → OTTO SEO → All Sites (SEO Automation) and remove the project associated with your stuck site.
  3. Wait a few minutes before proceeding to allow the system to fully clear the previous connection attempt.
  4. Create a fresh OTTO project. Still in Left sidebar → OTTO SEO → All Sites (SEO Automation), create a new project for your website as if connecting it for the first time.
  5. Reinstall the OTTO script. Follow the setup instructions to install the OTTO script on your site again, using the installation steps provided within the OTTO SEO section of the platform.
  6. Trigger a new connection. Once the script is reinstalled, attempt to connect your site again and monitor the status over the next 15–30 minutes.

📊 After Reconnecting

If the connection completes successfully, your site will move past the processing stage and OTTO will begin its full setup. You can monitor the progress from the OTTO SEO section of the platform.

🚨 If the Issue Persists

The fresh-connection approach resolves this issue in most cases. However, if your site remains stuck after following all the steps above, this may indicate a deeper infrastructure issue that requires engineering intervention — similar to cases where the crawl dies silently and cannot self-recover.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.

When you reach out, please have the following information ready to help the team investigate quickly:

  • Your website URL
  • The date and time you first attempted to connect
  • Confirmation that you have already removed and reinstalled the script
  • A description of the curr