📋 Overview
When you push or repost content from Search Atlas to your WordPress site, you may occasionally see an "unexpected_error" message during the sync. When this happens, your changes are not saved to the live page, even though the edit looks complete on your end.
This error almost always points to a connection or permissions issue between Search Atlas and WordPress. The good news: it is usually quick to fix. This guide walks you through the most common causes and how to resolve each one.
🔍 Common Causes
- The WordPress connection (integration) has expired or been disconnected.
- The connected user account no longer has permission to edit or publish the page.
- A WordPress security plugin or firewall is blocking the request.
- The page or post was deleted, moved to a draft, or had its URL changed in WordPress.
- A temporary server timeout caused by very large content or slow hosting.
⚡ Quick Fixes to Try First
- Wait one to two minutes and retry the sync. Many "unexpected_error" messages are temporary timeouts.
- If you just triggered a sync from the Search Atlas dashboard (Left sidebar → Content → Content Genius (What are we writing today?) — using the CMS SYNC column), you may instead see a "Request Throttled — Please make another request after 5 minute(s)" notice. This is a normal cooldown — wait the full five minutes before trying again.
- Confirm the page still exists in WordPress and is published (not in Draft or Trash).
- Make a small edit again in Search Atlas and resync to confirm the issue repeats.
If the error continues, work through the steps below.
🔌 Step 1: Reconnect Your WordPress Integration
An expired connection is the most frequent cause of this error.
- In Search Atlas, go to Settings > Integrations (or the WordPress connection panel for your project).
- Locate your WordPress site and select Disconnect.
- Select Connect and sign in to WordPress again, approving the requested permissions.
- Return to your content and retry the sync.
🔑 Step 2: Check User Permissions in WordPress
The WordPress account used for the connection must be allowed to edit and publish content.
- Log in to your WordPress admin dashboard.
- Go to Users and open the account connected to Search Atlas.
- Confirm the role is Administrator or Editor. Author and Contributor roles often cannot update published pages.
- If the role was recently changed, update it, then reconnect the integration (see Step 1).
🛡️ Step 3: Review Security Plugins and Firewalls
Security tools can block automated updates from outside services.
- Check whether you use plugins such as Wordfence, Sucuri, iThemes Security, or a Cloudflare firewall.
- Temporarily disable the plugin, or add Search Atlas to its allowlist.
- Retry the sync. If it succeeds, ask your developer to permanently allowlist Search Atlas so you can re-enable full protection.
🔗 REST API Access
Search Atlas updates content through the WordPress REST API. If a plugin or hosting setting disables the REST API, syncs will fail. Confirm the REST API is enabled, or ask your host to enable it.
📄 Step 4: Confirm the Page Still Matches
If the page was renamed, moved, or its URL (slug) changed in WordPress after you first connected it, the sync can no longer find it.
- Open the page in WordPress and copy its current URL.
- Compare it to the URL shown in Search Atlas.
- If they differ, reconnect or re-import the page in Search Atlas so it points to the correct destination.
🐢 Step 5: Handle Large or Slow Pages
Very large pages, or sites on slower hosting, can time out mid-sync.
- Try syncing during off-peak hours.
- Split unusually large updates into smaller edits where possible.
- Ask your host whether PHP timeout or memory limits can be increased.
💬 Related Sync Messages
Not every failed sync returns "unexpected_error." If you see one of the messages below, use the matching guidance.
"Article is still being generated. Please wait until generation is complete before publishing"
Normally this means the article is not finished generating yet — reopen it and wait until the status shows complete, then sync again. If the message keeps appearing on an article that has already finished generating, this is a known issue our engineering team is actively working on. Contact support with the affected article link so we can publish it for you while the fix is rolled out.
Bulk Sync Fails but Individual Sync Works
If syncing several articles at once with Bulk Sync to WordPress fails while syncing a single article succeeds, sync the affected articles one at a time as a workaround, and let support know the bulk action failed.
🆘 Still Seeing the Error?
If you have completed the steps above and the sync still fails, contact our support team and include the details below so we can investigate quickly:
- The URL of the page you are trying to update.
- The exact date and time of your most recent failed attempt.
- A screenshot of the "unexpected_error" message.
- The name of any security plugin or firewall on your site.
- The WordPress user role connected to Search Atlas.
With this information, our team can pinpoint the cause and get your content syncing again.