## **🔍 Overview**

Some customers find that when they try to publish an article from Content Genius directly to WordPress, the **Create** button keeps spinning and resets without publishing anything. This guide explains the most common causes and the steps you can take to resolve the issue.



## **⚙️ Common Causes**

- **Stale generation loop:** Content Genius can occasionally get stuck in a background status-polling loop, preventing new publish actions from completing.
- **Article stuck at Step 1:** If article generation did not fully complete, the article may be in an incomplete state that blocks export.
- **Incorrect WordPress connection:** The platform may be referencing an outdated or misconfigured WordPress CMS connector, causing publish requests to fail silently.
- **Syncing the original draft instead of your edits:** A known issue can cause the export to send the original AI-generated draft rather than your latest saved version, which may also interrupt the publish flow.

## **✅ Step-by-Step Fixes**

1. **Refresh and check article status.** Go to **Left sidebar → Content** and open the Content Genius listing table. If the article shows a loading or generating status, wait two to three minutes and refresh the page. If it remains stuck, continue to the next step.
2. **Save your edits before exporting.** Open the article in the editor. Make sure all your changes are saved — look for a confirmation that the latest version is stored. Do not attempt to publish immediately after making edits without saving first.
3. **Re-open the article and retry the Create button.** Close the article, return to the Content Genius listing table, reopen the article, and click **Create** again. A fresh session often clears the loop.
4. **Verify your WordPress CMS connector.** Navigate to **Account Menu (avatar) → Settings → CMS Connectors** and confirm that your WordPress site is connected correctly. If you see more than one connection for the same site, remove the duplicate and keep only the active one. Do not add a new connection if one already exists — the platform should detect and use the existing connector automatically.
5. **Check your WordPress site permissions.** In your WordPress admin panel, confirm that the user account connected to Search Atlas has the **Administrator** role. Author or Editor accounts cannot connect the plugin, and insufficient permissions can silently block publishing.
6. **Try publishing a different article.** If the issue affects only one article, it may be in a corrupted state. Try creating a new article and publishing that one to confirm your connection is working. Then retry the original article.
7. **Clear browser cache or switch browsers.** Occasionally a cached session causes button states to freeze. Clear your cache or open Search Atlas in a different browser and attempt the publish again.

## **🚫 What to Avoid**

- **Do not click the Create button repeatedly.** Multiple rapid clicks can create duplicate publish requests and worsen the loop.
- **Do not disconnect and reconnect your WordPress site unnecessarily.** If a valid CMS connector already exists, adding a new one can cause conflicts.
- **Do not navigate away mid-generation.** If an article is still generating (Step 1 progress visible), leaving the page can interrupt the process and leave the article in a stuck state.

## **💡 Tips to Prevent This Issue**

- Always wait for article generation to fully complete before opening the editor or attempting to publish.
- Save your edits explicitly before clicking **Create** to ensure the latest version is exported to WordPress.
- Keep only one active CMS connector per WordPress site under **Account Menu (avatar) → Settings → CMS Connectors**.
- Use a supported modern browser such as Chrome or Firefox, kept up to date.

## **🆘 Still Need Help?**

If you have followed all the steps above and the Create button is still stuck, our team can investigate your specific account and article state. 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.