🔍 What Is the 'None Response' Error?
When you attempt to publish an article directly to WordPress from Search Atlas, you may see an error message that reads None Response. This means Search Atlas sent the publish request to your WordPress site but received no valid reply in return. The connection was either blocked, timed out, or rejected before it could complete.
This is almost always caused by a configuration issue on your WordPress site rather than a problem with Search Atlas itself.
⚙️ Common Causes of This Error
- REST API is disabled: Search Atlas uses the WordPress REST API to publish content. If a plugin or server setting has disabled it, all publish requests will fail.
- Incorrect API credentials: An invalid username, password, or Application Password will cause the connection to be rejected silently.
- Security plugins blocking requests: Plugins like Wordfence, iThemes Security, or Cloudflare WAF rules can block external API calls from Search Atlas.
- SSL certificate issues: An expired or misconfigured SSL certificate on your WordPress domain can prevent a secure connection from being established.
- Server timeout or resource limits: Shared hosting environments with low memory or execution time limits may drop the request before a response is sent.
🚀 Step-by-Step Resolution
- Verify your WordPress connection settings. In Search Atlas, go to the top-right avatar → Settings → Integrations / CMS Connectors and confirm that the WordPress site URL, username, and Application Password are all entered correctly. The URL must be a valid domain URL (for example, https://example.com).
- Confirm the REST API is active. Open a new browser tab and navigate to yoursite.com/wp-json/wp/v2/posts. If you see a JSON response with post data, the REST API is working. If you see an error or blank page, the REST API is disabled and needs to be re-enabled in your WordPress settings or by deactivating the plugin that is blocking it.
- Regenerate your Application Password. In your WordPress dashboard, go to Users → Profile, scroll to the Application Passwords section, delete the existing entry for Search Atlas, and create a new one. Copy the new password immediately and update it in Search Atlas.
- Temporarily disable security plugins. Deactivate plugins such as Wordfence, All In One WP Security, or similar tools one at a time. Attempt to publish again after each deactivation to identify which plugin is blocking the request. Once identified, add Search Atlas IP addresses to the plugin's allowlist or whitelist.
- Check your SSL certificate. Visit whatsmycertificate.com or a similar tool and enter your domain to confirm the SSL certificate is valid and not expired. An invalid certificate will cause secure API calls to fail silently.
- Contact your hosting provider. If none of the above steps resolve the issue, ask your hosting provider to confirm that outbound REST API requests are permitted and that execution time and memory limits are sufficient to handle publishing requests.
💡 Tips to Prevent This Error in Future
- Use a dedicated Application Password for Search Atlas rather than your main account password.
- Avoid using security plugins that blanket-block all REST API requests unless you can configure per-application exceptions.
- Keep your WordPress core, plugins, and themes updated to reduce conflicts that can affect API behavior.
- Test your WordPress connection inside Search Atlas after any major site update or hosting migration.
📊 Challenge Access Eligibility
Some Search Atlas features, including certain publishing challenges or content campaigns, require your WordPress integration to be fully verified and active before you can participate. If you are seeing a message indicating you are not eligible for a challenge, the most likely reason is that your WordPress connection has not been successfully established or has recently disconnected due to one of the errors described above.
To restore eligibility, resolve the None Response error using the steps above, then re-verify your WordPress connection inside Search Atlas. Once the connection returns a successful status, challenge access should be restored automatically within a few minutes.
🆘 Still Need Help?
If you have followed all of the steps above and the error persists, 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.