🔍 Overview
Some users encounter errors when attempting to publish or sync a blog post through the Search Atlas WordPress plugin. Common symptoms include a generic publish failure message, an HTTP 400 error, or a prompt asking for an application password that does not appear in your settings. This article explains what causes these issues and what steps to take.
❓ Do You Need an Application Password?
No. As of plugin version 2.6.10, the Search Atlas WordPress plugin uses its own API key for authentication. You do not need to set up a WordPress application password. If you see guidance elsewhere suggesting this step, it does not apply to the current version of the plugin. You can safely ignore any prompts or instructions related to application passwords.
✅ Step 1: Confirm Your Plugin Is Connected
Before investigating further, verify that your WordPress site is properly connected to Search Atlas:
- Log in to your Search Atlas account.
- Navigate to Account Menu → Settings → CMS Connectors.
- Confirm that your site appears as connected and that the connection status shows no errors.
- If the site is not connected, disconnect and reconnect it to refresh the authentication.
⚙️ Step 2: Check Your Plugin Version
Make sure you are running the latest version of the Search Atlas WordPress plugin. An outdated plugin version can cause compatibility issues with the publishing pipeline.
- Log in to your WordPress admin dashboard.
- Go to Plugins → Installed Plugins.
- Locate the Search Atlas plugin and check the version number.
- If an update is available, apply it immediately and then retry publishing.
🔄 Step 3: Retry Publishing the Article
After confirming the connection and plugin version, attempt to publish or sync your blog post again. In some cases, a temporary failure in the publishing pipeline can resolve itself after a reconnection or plugin update.
- Open your article inside Content Genius by going to Left sidebar → Content → Content Genius.
- Select the article you want to publish.
- Attempt to publish or sync it to your connected WordPress site.
- If the error persists, note the exact error message displayed — this will be important for the support team.
⚠️ When the Error Is a Known Bug
In some cases, a publishing failure is caused by an issue on the Search Atlas side — specifically a pipeline error that prevents the API key from being recognised correctly during the publish request. This is a known bug that the engineering team has actively worked to resolve.
If you have completed all the steps above and the error still occurs, this is likely a platform-level issue rather than a configuration problem on your end. You have not done anything wrong. The most effective next step is to contact our support team so they can investigate your specific account and connected site.
🚫 Common Errors This Article Covers
- Could not publish to WordPress page
- Unable to publish blog post (rest_forbidden error)
- Unable to save content as a draft to a connected WordPress account
- Empty response from the WordPress publish endpoint
- HTTP 400 INVALID_ARGUMENT error related to the publishing pipeline
💬 Contact Support
If you have followed all the steps above and are still unable to publish your blog post, our team can investigate the issue directly on your account. 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 reaching out, please share the following to help us resolve your issue faster:
- The exact error message you are seeing
- Your WordPress site URL
- The version of the Search Atlas WordPress plugin you have installed
- The article title or URL you were trying to publish