🔍 What This Error Means
When you see the message "We're unable to sync with your WordPress site. Check your configuration or reach out to support", it does not always mean your WordPress setup is misconfigured. In many cases, the issue is caused by a temporary platform-side problem — not something you have done wrong.
Past incidents have been traced to an invalid or expired API key on the Search Atlas side, which blocks the publish-to-WordPress process entirely. Our engineering team has resolved multiple occurrences of this and continues to monitor for recurrences.
✅ Step 1: Confirm Your WordPress Connection Is Healthy
Before assuming a platform issue, verify that your WordPress environment is set up correctly:
- Log in to your WordPress admin dashboard and confirm the MetaSync plugin is installed and active. The current supported version is v2.6.10 or later.
- Check that your WordPress REST API is accessible and not blocked by a security plugin or firewall rule. A rest_forbidden error in your browser console or server logs indicates a permissions or plugin conflict on the WordPress side.
- Confirm that the user account connected to Search Atlas has sufficient permissions to publish posts via the REST API.
🔄 Step 2: Try a Hard Refresh
If your connection looks healthy, perform a hard refresh of the Search Atlas platform in your browser (typically Ctrl + Shift + R on Windows or Cmd + Shift + R on Mac) and attempt the sync again. This rules out a stale browser session as the cause.
📝 Step 3: Retry Publishing From Content Genius
Navigate to Left sidebar → Content → Content Genius and attempt to publish or sync your article again. If the error persists after a hard refresh and the MetaSync plugin is confirmed active, the issue is likely on the platform side rather than your configuration.
⚙️ Step 4: Understand Platform-Side Causes
Several known platform-side issues can trigger this error message:
- Invalid or expired API key — An internal API key used by Search Atlas to communicate with WordPress becomes invalid, blocking all publish requests with a 400 error. This has been the root cause in multiple incidents and is resolved by our engineering team without any action required from you.
- Empty response from WordPress — In some cases, WordPress returns an empty response body, causing a processing error on the Search Atlas side. This is also handled internally.
- Temporary service disruption — Occasionally, a broader platform issue affects multiple users simultaneously. Our team monitors for these and deploys fixes as quickly as possible.
None of these causes require changes to your WordPress site or MetaSync plugin when your configuration is confirmed healthy.
🛠️ Step 5: What To Do If the Error Persists
If you have confirmed that your MetaSync plugin is active and your WordPress permissions are correct, and the sync still fails after retrying:
- Note the exact error message displayed on screen.
- Record the date and time you experienced the failure.
- Check whether other team members on your account are experiencing the same issue — this helps confirm whether it is account-specific or platform-wide.
- Contact our support team using the instructions below so we can investigate your account directly and file an internal ticket if needed.
💡 Key Things To Remember
- A sync failure error does not always mean your WordPress or plugin configuration is broken.
- Hard-refreshing the platform does not resolve platform-side API key issues — only our engineering team can do that.
- The MetaSync plugin must be version v2.6.10 or later for compatibility.
- REST API access must be enabled and not blocked by WordPress security settings.
💬 Still Seeing the Error?
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.