🔍 Overview
When connecting the Search Atlas MetaSync plugin to your WordPress site, you may encounter an authentication timeout — typically after 60 seconds — regardless of whether you use the One-Click connection or manual API key entry method. In some cases, you may also see a 500 error or the message "The API key could not be verified." This article walks you through the most effective troubleshooting steps to restore the connection.
⚠️ What Causes This Issue?
Authentication timeouts and API key errors during MetaSync setup are usually caused by one or more of the following:
- A corrupted or invalidated API key stored in your WordPress database
- A server-side timeout on your WordPress host that cuts the connection before authentication completes
- A plugin conflict or caching layer interfering with the authentication request
- An outdated version of the MetaSync plugin that does not send authentication headers correctly
- A firewall or security plugin blocking outbound requests from your WordPress site to Search Atlas servers
🛠️ Step-by-Step Troubleshooting
Work through the steps below in order. Most customers resolve the issue by completing steps 1 through 4.
- Update the MetaSync plugin to the latest version. In your WordPress dashboard, go to Plugins → Installed Plugins, find Search Atlas MetaSync, and click Update if an update is available. Older plugin versions may not send the correct authentication headers required by the Search Atlas API.
- Regenerate your API key in Search Atlas. Log in to your Search Atlas dashboard, navigate to Settings → API Keys, and generate a new API key. Do not reuse the old key — copy the new one immediately and keep it ready for the next step.
- Disconnect and reconnect the plugin manually. In your WordPress admin panel, go to the MetaSync plugin settings and disconnect any existing connection. Select the manual entry method and paste your newly generated API key. Save the settings and wait up to 90 seconds for the handshake to complete.
- Clear all caches before retrying. Clear your WordPress object cache, page cache, and any CDN cache (e.g., Cloudflare, WP Rocket, W3 Total Cache). A stale cache can cause the authentication request to fail silently.
- Temporarily disable security and firewall plugins. Plugins such as Wordfence, iThemes Security, or All In One WP Security may block outbound API requests. Disable them one at a time, then retry the connection after each deactivation to identify the culprit. Re-enable them once the connection is established.
- Check your hosting provider's outbound request limits. Some managed WordPress hosts (e.g., WP Engine, Kinsta, Flywheel) restrict or throttle outbound HTTP requests. Contact your host and ask them to whitelist outbound connections to api.searchatlas.com. Also ask them to confirm that your PHP execution timeout is set to at least 120 seconds.
- Switch to the One-Click connection method if manual entry failed, or vice versa. If manual entry timed out, try the One-Click SSO flow from your Search Atlas dashboard under Account Menu → Settings → CMS Connectors. If One-Click failed first, switch to manual entry with your regenerated key.
✅ How to Confirm the Connection Is Working
After completing the steps above, verify that MetaSync is connected successfully:
- In your WordPress admin panel, the MetaSync plugin status should show Connected with your Search Atlas account name displayed.
- In your Search Atlas dashboard under Account Menu → Settings → CMS Connectors, your WordPress site should appear as an active, linked property.
- Run a test sync from the MetaSync plugin settings page and confirm that data flows to your Search Atlas account without errors.
🚫 Common Mistakes to Avoid
- Do not reuse a previously generated API key after a failed authentication attempt. Once an error occurs, always regenerate a fresh key.
- Do not attempt multiple connection methods simultaneously. Complete one method fully — including clearing caches — before trying the other.
- Do not skip the cache-clearing step. This is one of the most overlooked causes of repeated authentication failures.
💬 Still Need Help?
If you have followed all the steps above and the MetaSync plugin still cannot authenticate, our team can investigate your specific account and server configuration. 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 ready to speed up the investigation:
- Your WordPress site URL
- The exact error message displayed (screenshot if possible)
- Your WordPress version and MetaSync plugin version
- Your hosting provider name
- A list of active security or caching plugins
Additional Notes
API key type mismatch: The MetaSync plugin currently requires a v1 API key. Using a v2 API key may cause verification to fail. Log in to Search Atlas, go to Settings > API Keys, and generate or copy a v1 key instead.