If you're getting a timeout error while installing the Search Atlas WordPress plugin behind Cloudflare, this guide walks you through the working fix.

🚨 The Problem

A user attempting to install the Search Atlas plugin experienced a timeout error, even though the server was behind Cloudflare, external calls were allowed, no IP restrictions were configured, all other WordPress plugins were disabled, and cache had been cleared. Despite standard troubleshooting, the timeout persisted.

🧠 Why This Happens

When your WordPress server is behind Cloudflare (or another CDN, WAF, or security layer), automated API calls during plugin setup may fail because the inbound callback the plugin relies on to complete authentication gets silently blocked — by a Cloudflare WAF rule, "I'm under attack" mode, an IP allowlist, or a "coming soon" page. Even with no explicit IP restrictions visible to you, the automated setup can still fail silently this way.

✅ The Working Solution: Manual Plugin Connection

Instead of relying on automatic setup, manually connect the plugin using your API credentials.

Step 1 — Open the Search Atlas Plugin in WordPress. In your WordPress dashboard, go to WordPress Admin → Search Atlas Plugin → Settings.

Step 2 — Paste Your API Key. In the API Key field, paste your assigned API key and save.

Step 3 — Add the OTTO Pixel UUID. Below the API Key field, paste the provided UUID into the OTTO Pixel UUID field and save.

Step 4 — Purge All Caches. This is critical: clear your WordPress cache, server cache, Cloudflare cache, and any object caching layers, then wait 30–60 seconds.

Step 5 — Click Sync. After clearing cache, click Sync Plugin. If successful, the plugin will connect and your dashboard will load normally.

🔑 Where to Find Your UUID and API Key in Search Atlas

Your UUID is embedded inside your OTTO Pixel script. Navigate to Left Sidebar → OTTO SEO → All Sites, select your project, then open its Installation Guide → Custom Installation. Under Step 1: Copy Your Pixel Script, you'll see a script block with your OTTO pixel — inside the script tag, look for a data-uuid attribute set to a value such as 87a7de3c-6f0e-4269-8518-df74976bb97c. That value is your UUID. It's unique per project, used to identify your OTTO installation, and automatically generated.

Your API Key is located in account-level settings. Navigate to Top Right → Click your Profile Name → Settings → API Keys. You'll see a section titled Search Atlas API Key with a long alphanumeric key. That is your API Key. It's account-level (not project-specific), used for integrations and external connections, and sensitive — do not share it publicly.

⚠️ Important Difference

The UUID is found in the OTTO Installation Guide, is project-specific, and is used for pixel installation — it appears inside a script tag. The API Key is found in Account Settings, is account-level, and is used for API integrations — it's listed under the API Keys panel.

🎉 Expected Result

You should now see your Search Atlas dashboard, confirm the plugin shows as connected, and no longer receive timeout errors.

🛠 If It Still Doesn't Work

Check PHP memory limits, max_execution_time, firewall or WAF rules, and CDN request timeout settings. If needed, escalate to support with a short screen recording, server environment details, and hosting provider information.

If you're running WordPress behind Cloudflare or another CDN and seeing timeouts, manual setup is the fastest resolution path.

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.