## **📋 Overview**

If you've updated an article in Search Atlas but your GoHighLevel CMS Connector keeps publishing an older version, even after repeated manual syncs, this guide will help you fix it. In most cases, the problem comes from cached content, an unsaved draft, or a connection that needs to be refreshed. The steps below walk you through the most common causes and how to resolve them.

## **🤔 Why This Happens**

The CMS Connector syncs the version of your article that it last recognized as "final." When the latest version isn't pulling through, it's usually because of one of these reasons:

- The newest changes were not saved or published inside Search Atlas before syncing.
- Cached content on the GoHighLevel side is still serving the previous version.
- The connector's authorization token has expired or the connection has drifted.
- The article is mapped to the wrong page or post in GoHighLevel.
- The sync completed, but the GoHighLevel page cache hasn't refreshed yet.

## ✅ Before You Start

Confirm the following so your sync has the correct content to pull:

- You are editing the same article that is mapped to the connector.
- Your most recent edits are **saved and published** in Search Atlas, not left in draft.
- You have admin access to both your Search Atlas account and your GoHighLevel sub-account.

## **🛠️ Step-by-Step Fix**

### **1️⃣ Step 1: Confirm the latest version is published in Search Atlas**

1. Open the article in Search Atlas.
2. Check the version history or last-edited timestamp to confirm your changes are present.
3. Click **Save** and then **Publish**. A draft that is saved but not published will not sync.

### **2️⃣ Step 2: Verify the connector mapping**

1. Go to **Avatar → Settings → CMS Connectors** and open your GoHighLevel CMS Connector.
2. Confirm the article is mapped to the correct GoHighLevel page or blog post.
3. If the mapping points to a different or duplicate page, update it to the correct destination.

### **3️⃣ Step 3: Run a fresh manual sync**

1. From the connector screen, select the article.
2. Click **Sync** and wait for the status to change to **Completed**.
3. Do not start a new sync until the current one finishes, as overlapping syncs can re-queue the older version.

### **4️⃣ Step 4: Clear the GoHighLevel cache**

Even after a successful sync, GoHighLevel may continue serving a cached page.

1. Open the page in GoHighLevel and republish it.
2. View the live page in a private or incognito browser window to bypass your local cache.
3. If you use a CDN or third-party cache, clear it as well.

### **5️⃣ Step 5: Reconnect the integration**

If the latest version still isn't appearing, the connection may need to be refreshed.

1. In **Avatar → Settings → CMS Connectors**, disconnect the GoHighLevel CMS Connector.
2. Reconnect and re-authorize access to your GoHighLevel sub-account.
3. Re-map the article and run the sync again.

## **🚨 Still Seeing the Old Version?**

If you've completed all the steps and the connector is still pulling an outdated article, contact our support team and include the details below to speed up resolution:

- The article name and its URL in Search Atlas.
- The GoHighLevel page or post URL where the old version appears.
- The date and time of your most recent edit and your most recent sync attempt.
- A screenshot of the connector's sync status.

## **💡 Quick Tips to Prevent Sync Issues**

- Always publish your changes in Search Atlas before syncing.
- Wait for each sync to finish before starting another.
- Refresh the live page in a private browser window to confirm the update.
- Re-authorize the connector periodically if you change GoHighLevel passwords or permissions.