π What a failed publish means
MetaSync enables Search Atlas to publish articles to WordPress through the connected plugin. If publishing reports a failure, check WordPress for an existing post or draft before retrying. Signing back into Search Atlas does not necessarily repair the WordPress publishing connection. Source: metasync/public/class-metasync-rest-api.php:1705β1707; customer-frontend/src/modules/content-assistant/shared/components/cms/CMSModal.tsx:289β295.
β Confirm you are still connected
Check the connection before you try the same article again.
- Open the project or site that owns the article.
- In Search Atlas, open Settings β CMS Connectors, then locate your websiteβs WordPress connection. Source:
customer-frontend/src/modules/settings/v1/components/settings-page/navigation/index.tsx:46β49. - Confirm the saved address matches your live site, including https and the correct domain.
- Look for an active or connected status. Missing, expired, or error status means the site is not fully connected.
- If you manage several sites, confirm the article belongs to the property you intend to update.
Signing in to the plugin only proves that login worked. Publishing also needs an active link between that WordPress site and Search Atlas.
π οΈ Check WordPress before retrying
- Plugin: In WordPress, confirm the Search Atlas or MetaSync plugin is installed and active.
- Permissions: The linked WordPress user must be allowed to create and publish posts.
- Site address: Confirm that the WordPress connection points to the correct WordPress installation and a reachable publishing address. Use the installationβs canonical address, including any required subdirectory. Do not assume a www/non-www difference alone causes the failure; headless sites may use a different WordPress backend address from their public website. Source:
content-assistant/app/ca/models.py:24523β24532,36499β36509. - Permalinks: Open WordPress permalink settings and save them once so site routes refresh.
- Blockers: Security plugins, a firewall, a CDN, or host rules can stop the publish request. Your host may need to allow Search Atlas.
π Publish one test article
- In Settings β CMS Connectors, locate the affected WordPress connection and use Sync to check it. If Reconnect is available, follow that flow to restore access. For a plugin-based connection, verify the pluginβs connection in WordPress. Do not delete the connector as a routine troubleshooting step. Source:
customer-frontend/src/modules/settings/v1/components/settings-page/components/cms-connectors-list/index.tsx:280β285,522β529. - Select one short draft instead of a batch of articles.
- Publish that draft and wait until the status finishes.
- Open the post on your website and confirm the title and content arrived.
If the test post appears, publish the original article again. If it fails, copy the full error shown in Search Atlas before you retry.
β οΈ Common causes after re-authentication
- Old link: The plugin was signed in again, but Search Atlas still uses a previous site connection.
- Wrong site: The link points to staging, an old domain, or the wrong www version.
- Limited user: The WordPress user can log in but cannot publish posts.
- Blocked request: A security tool or host rule stops MetaSync from delivering the article.
- Plugin conflict: Another publishing or security plugin interferes with the connection.
π¬ What to send if it still fails
If the status shows connected, the plugin is active, and one test article still fails, contact support with the site address, article name, attempt time, and the complete error text.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.