Search Atlas Help Center

⚡ OTTO WordPress Installation and 'Not Found' Fix

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

Overview

This article covers how to install OTTO on your WordPress site, create and configure a Topical Map, generate articles from it, and resolve the "OTTO not found" error that can appear even after your API key appears to have synced and the UUID field is populated.

Installing OTTO on WordPress

  1. Log in to your Search Atlas account and navigate to the OTTO section.
  2. Copy your API key from the Search Atlas dashboard.
  3. In your WordPress admin panel, go to Plugins → Add New → Upload Plugin, upload the plugin .zip provided by Search Atlas, then install and activate it.
  4. In your WordPress admin panel, go to Search Atlas → Settings and paste your API key into the Search Atlas API Key field.
  5. Save your settings and confirm that the UUID field is populated — this indicates a successful connection between your WordPress site and your Search Atlas account.

Setting Up a Topical Map and Generating Articles

  1. In Search Atlas, navigate to the Topical Maps tool and create a new map for your target topic or domain.
  2. Review the suggested topic clusters and select the articles you want to generate.
  3. Assign the Topical Map to your connected WordPress site within the OTTO settings.
  4. Initiate article generation and monitor progress from your Search Atlas dashboard.

Resolving the 'OTTO Not Found' Error

If you see the "OTTO not found" error after the API key sync appears successful and the UUID field is populated, work through the following steps in order:

  1. Confirm the plugin is fully activated: In WordPress, go to Plugins → Installed Plugins and verify the OTTO plugin shows as "Active" — installed but not activated will still show a UUID without establishing a live connection.
  2. Check for plugin conflicts: Temporarily deactivate other plugins one at a time to identify whether a third-party plugin is interfering with the OTTO connection. Security, caching, and firewall plugins are common sources of conflict.
  3. Verify REST API accessibility: OTTO relies on the WordPress REST API. If a security plugin or server-level rule is blocking REST API requests, the connection will fail. Check with your hosting provider or temporarily disable REST API restrictions to test.
  4. Clear all caches: Clear your WordPress cache plugin, server-side cache, and any CDN cache, then retry the connection.
  5. Re-enter your API key: Copy a fresh API key from your Search Atlas account, re-paste it into the OTTO plugin settings, save, and confirm the UUID repopulates.

When to Escalate

If you have worked through all of the steps above and the error persists, please have the following ready when you contact support so the issue can be resolved as quickly as possible:

  • Your Search Atlas account email or project name
  • The WordPress site URL where OTTO is installed
  • A description of which step is failing and what you have already tried
  • The exact error message (e.g., "OTTO not found") and any error codes displayed
  • A screenshot of your OTTO plugin settings page showing the API key and UUID fields
  • The names and versions of any other active WordPress plugins
  • The timestamp of when the issue first occurred

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.