🧩 The Root Cause: Two Separate Steps, One Common Mistake
When you edit a service description inside Search Atlas using the MCP (Managed Content Pipeline) workflow, that change is saved to Search Atlas only. It does not automatically appear on your Google Business Profile. If you stop at the save step, Google's background sync will eventually re-read the live state of your GBP and overwrite your Search Atlas draft with the older version still published on Google. This is the mechanism behind the reversion you are seeing—it is not a bug, and toggling Data Lock or waiting will not resolve it.
📋 How the MCP Workflow Actually Works
The MCP workflow has three distinct stages, and all three must be completed for a change to survive Google's background sync:
- MCP Save — Your edited service description is stored inside Search Atlas as a draft. Google has not received anything yet.
- UI Deployment — You explicitly push the draft from Search Atlas to Google Business Profile using the Deploy action in the platform interface. This is the step most users miss.
- Google Acceptance and Sync Lock — Google receives and accepts the update. Once the change is live on GBP, Search Atlas background sync reads that accepted state and preserves it going forward.
Skipping Step 2 means the change never reaches Google. The next background sync then pulls the old live GBP content back into Search Atlas, making it appear as though your edit was erased.
🔍 Why Google Background Sync Causes Overwriting
Search Atlas runs periodic background syncs with Google Business Profile to keep location data consistent. During each sync, the platform reads the current live state of your GBP listing. If your service description has not been deployed to Google yet, the live GBP state still contains the old text. The sync then writes that old text back into Search Atlas, overwriting your undeployed draft. This is expected behavior designed to prevent stale or conflicting data—but it requires that your changes reach Google before the next sync cycle runs.
✅ The Correct Workflow: Step-by-Step
- Open the relevant location in Search Atlas and navigate to the Services section.
- Edit your service description and click Save in the MCP editor. Your draft is now stored in Search Atlas.
- Do not close the panel. Locate the Deploy button and click it to push the change to your Google Business Profile. This step is mandatory.
- Wait for the deployment confirmation. Search Atlas will display a success status once Google has accepted the update.
- After Google acceptance, background sync will read the new live GBP state and preserve your description on both platforms.
⚠️ Common Mistakes That Trigger Reversion
- Saving without deploying: Clicking Save in the MCP editor is not the same as deploying. Both actions are required.
- Deploying and immediately closing: If you close before the deployment confirmation appears, the push may not have completed. Always wait for the success status.
- Expecting Data Lock to substitute for deployment: Data Lock prevents incoming sync from overwriting a field only after a successful deployment has been confirmed. It does not protect an undeployed draft.
- Making multiple edits across sessions: Each new MCP save session creates a new draft. If earlier drafts were never deployed, the sync cycle may have already overwritten them before your latest session.
🛡️ How Data Lock Fits Into This Workflow
Data Lock is a useful tool, but it works after deployment, not instead of it. Once you have successfully deployed a service description and Google has accepted it, enabling Data Lock on that field tells Search Atlas to hold that value and prevent future syncs from overwriting it with changes made directly on GBP. If you enable Data Lock on an undeployed draft, the protection applies to a value that Google has never received, which will not prevent reversion.
🚀 Quick Reference: MCP Save vs. UI Deploy
- MCP Save: Stores your edit in Search Atlas. Google is not notified. Draft is vulnerable to sync overwrite.
- UI Deploy: Sends your edit to Google Business Profile. Required for the change to become live. Sync will then preserve the accepted value.
Always complete both steps in sequence. A saved draft that has not been deployed will not survive the next background sync cycle.
💬 Need More Help?
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.