🔍 Overview
Some users have reported that the Sync to CMS toggle returns a Something went wrong error, and OTTO SEO optimizations — such as alt text changes or meta title updates — do not appear on their WordPress site even after reinstalling the plugin or re-authenticating their connection.
This article explains the known cause, what you can check on your end, and how to get this resolved quickly if the issue persists.
⚙️ What Causes This Issue
This behaviour has been traced to a software bug on the Search Atlas side that can prevent the Sync to CMS feature from pushing OTTO optimizations to WordPress correctly. The bug affects the sync process itself — not your WordPress plugin installation or authentication credentials. In confirmed cases, the engineering team identified and deployed a fix that fully resolved the problem.
Because this is a platform-side issue, there are no local troubleshooting steps that will repair it on their own. However, there are a few things worth verifying before escalating, to rule out common configuration gaps.
✅ What to Check First
Before contacting support, run through the following checks to confirm your setup is correct:
- SearchAtlas WordPress plugin (MetaSync) is installed and active: Sync to CMS is available exclusively for websites connected through the SearchAtlas WordPress plugin (MetaSync). If your site uses the Cloudflare or Pixel installation method, the Sync to CMS option will not appear in your project. Confirm the plugin is installed and active on your site.
- Your project is connected via the WordPress plugin: Sync to CMS only applies to WordPress plugin projects. If your project is not connected through the SearchAtlas WordPress plugin, the sync cannot proceed.
- Re-authenticate if prompted: If your WordPress connection was recently changed or expired, re-authenticate the connection from within your project settings. A successful re-authentication should be confirmed before testing the sync again.
- Test the sync again after re-authentication: After confirming the above, attempt to use the Sync to CMS toggle again. If the error persists, the issue is likely on the platform side.
⚠️ Important Limitations to Know
The Sync to CMS feature has several built-in limitations that are worth keeping in mind:
- WordPress plugin projects only: Sync to CMS is available only for websites connected through the SearchAtlas WordPress plugin (MetaSync). Sites using the Cloudflare or Pixel installation method do not have access to this feature.
- Heading changes and Link corrections do not sync: Heading changes and Link corrections (Issues with Links) are not synced. These optimizations modify the page body content, which SEO plugins such as Yoast SEO, Rank Math, and AIOSEO do not provide equivalent fields for — so there is nothing to synchronize.
- Heading and Link changes are editor-dependent: These content changes are supported only on posts and pages using the Gutenberg or Classic Editor. They are intentionally skipped on page builders such as Elementor, Divi, WPBakery, Beaver Builder, Oxygen, and Brizy, because those builders store content outside the standard WordPress post body.
- All other optimization types sync regardless of editor: Meta title, meta description, focus keyword/keyphrase, Open Graph title and description, Twitter title and description, schema/structured data, canonical URL, and image alt text all sync regardless of which editor or page builder is used. Image alt text updates are written to the WordPress Media Library.
🛠️ If the Error Persists
If you have confirmed your SearchAtlas WordPress plugin is active, your project is properly connected via the WordPress plugin, and the Something went wrong error still appears after attempting to sync, this indicates a platform-side issue that requires the engineering team to investigate.
This type of issue cannot be resolved through self-service steps alone. In confirmed cases, our team has been able to identify the root cause, deploy a targeted fix, and fully restore sync functionality for the affected project.
To get this escalated quickly, contact our support team directly so they can log the issue and engage the relevant engineers on your behalf.
💬 Contact Support
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, it helps to include the following details to speed up the investigation:
- The domain or project name affected
- The exact error message you are seeing
- Whether re-authentication was attempted and whether it completed successfully
- Which specific OTTO optimizations are not syncing (e.g. alt text, meta descriptions)