🔍 Overview

Some users experience errors when connecting the OTTO WordPress plugin to Search Atlas or when publishing and syncing content. Common symptoms include a persistent "API key could not be verified" warning, a 500 Internal Server Error during authentication, or articles failing to publish with an error shown in the Search Atlas dashboard. These issues are typically caused by backend authentication conflicts or plugin configuration problems that can often be resolved by following the steps below.

🛠️ Step 1 — Clear All Caches

Cached data is one of the most common causes of plugin authentication failures. Before anything else:

1. Clear your WordPress site cache completely, including any caching plugins (such as WP Rocket, W3 Total Cache, or LiteSpeed Cache).
2. Clear your browser cache and perform a hard refresh (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac).
3. If you use a CDN (such as Cloudflare), purge the CDN cache as well.

🔄 Step 2 — Reinstall and Reauthenticate the Plugin

If clearing the cache does not resolve the issue, reinstall the OTTO WordPress plugin and reconnect it to your Search Atlas account:

1. In your WordPress admin panel, deactivate and delete the existing OTTO plugin.
2. Download the latest version of the plugin from Search Atlas and reinstall it.
3. Generate a fresh API key from your Search Atlas account settings and enter it in the plugin's authentication field.
4. Save your settings and test the connection again.

Important: If you previously generated an API key using the V2 key generation flow, generate a new key and use that instead, as older keys may no longer authenticate correctly with the plugin.

⚙️ Step 3 — Redeploy the OTTO Task

If authentication succeeds but content still fails to sync or publish, try redeploying your OTTO task. Navigate to Left sidebar → OTTO SEO → Overview and trigger a new scan or redeploy for the affected site. This refreshes the connection between OTTO and your WordPress installation.

📊 Step 4 — Verify Your Plugin Version

Running an outdated version of the OTTO WordPress plugin can cause authentication and sync failures. Confirm that you are using the latest available version. If an update is available in your WordPress dashboard, apply it before retesting.

🚨 When These Steps Do Not Work

The authentication and sync errors described in this article have, in some cases, been caused by backend issues on the Search Atlas side. Engineering teams have previously deployed fixes for:

• API key validation failures returning a 400 INVALID_ARGUMENT error that blocks WordPress publishing.
• The WordPress connector appearing grayed out or returning a wp_client_error on sync even after a successful reconnect.
• 500 Internal Server Error responses during plugin authentication.

If you have completed all the steps above and the issue persists, this may indicate a backend problem that requires engineering investigation. In that case, do not continue retrying — escalate promptly so the team can identify and resolve the root cause.

💬 Contact Support

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.

To help the team investigate quickly, have the following ready before you reach out:

• A screen recording (such as a Jam recording) showing the error you are experiencing.
• The exact error message displayed in Search Atlas or WordPress.
• Your WordPress site URL and the plugin version you have installed.