đ What this article covers
Some customers see WordPress content fail to sync or publish even after the paid CMS connection is set up. Platform fixes for this path are released to all accounts automatically. You do not need a separate patch. This article shows how to confirm the connection, retry a publish, and tell a working sync from a site-side block.
â Confirm the latest fix is active
Search Atlas applies CMS sync updates on our side. After an update, the next successful sync is the confirmation that the fix is active for your site. A ticket that is still open does not mean the product feature is turned off.
- Open Settings and select CMS Connectors. Your connected sites are listed there by domain, and each shows its platform and connection state. The WordPress site, post type, status, author, and categories you publish with are saved as the project's publish preset in Brand Vault.
- In CMS Connectors, find your domain and confirm the WordPress row shows Connected with a recent update time. If it shows Disconnected, Not connected, Needs your input, or Has issues, the sync will not run until you reconnect or resolve that state.
- Run a fresh sync from the WordPress sync dialog or the article's CMS publish action, and choose Publish if you want the content live. Then open the post in WordPress admin and confirm the title, body, and meta description updated. If the status you sent was Draft, the post exists only as a draft and will not appear on the public site.
- If the status is connected and a new sync succeeds, the current fix is already live on your account.
đ Retry a failed sync or publish
- In Search Atlas, disconnect is not required first. Use the sync or publish action again on the same project.
- Wait until the job finishes. Do not start a second sync while the first one is still running.
- In WordPress, confirm you are looking at the same site and the same page or post, including the correct language or staging URL.
- Refresh the WordPress editor. Cached admin screens can hide a publish that already landed.
- Publish or update one small test change, sync again, and compare that single change before retrying a large batch.
đ ī¸ Fix common WordPress blockers
If sync still fails after a platform update, the block is often on the site, not an unfixed product bug.
- Permissions: Search Atlas connects with the MetaSync plugin API key, so publishing does not depend on the linked WordPress user being able to edit or publish. That user is the post author. Only users with the administrator, editor, or author role appear as author choices, and a role filter in the plugin that matches nobody falls back to all users so the connection is not dropped.
- Security plugins: Firewalls, login locks, or REST API blocks can reject the connection. Allow the Search Atlas connection and retry.
- Permalinks and REST API: Search Atlas reaches your site through the WordPress REST API at the URL you connected, so that address must be publicly reachable and not blocked by a firewall or security plugin. Pretty permalinks are recommended â the MetaSync plugin shows a warning in WordPress when permalinks are set to Plain â but plain permalinks still work, and posts then use the ?p=ID address.
- Staging versus live: A connection saved for a staging domain will not update the live site. Reconnect the URL you want to publish to.
- Plugin or theme conflicts: A recent WordPress, plugin, or theme update can break the API user. Test with security plugins paused briefly, then turn them back on.
đ What to send if it still fails
Include the project name, the exact site URL, the page that failed, the date and time of the last sync, and the on-screen error text. Also note any WordPress or security plugin you changed in the last week. Screenshots of the connection status and the WordPress editor help us match your case to the current fix without another long wait.
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.