🔍 Overview
After deploying changes to your Google Business Profile (GBP) through Search Atlas, you may notice that updates do not appear on your live listing — even after receiving a success message and waiting 24 hours or more. This article explains why this happens and walks you through the steps to resolve it.
⚠️ Why Changes May Not Appear
There are several reasons a deployment can appear successful inside Search Atlas but fail to update on Google's side:
- Google propagation delay: Most changes take up to 24–72 hours to appear on Google, even when deployed correctly.
- Invalid or deprecated attribute values: If a field contains a value Google no longer supports (for example, a deprecated social media enum), Google silently rejects the update — even though Search Atlas returns a success message.
- Pending state on Google's side: Certain field types, such as business hours or specific attributes, can enter a pending review state on Google and may take longer to go live.
- Invalid argument errors: A deploy containing an unsupported value in any single field can cause the entire deployment to fail, leaving all other changes unapplied.
- Service area updates: Service area changes are particularly prone to silent failures where Google accepts the request but does not apply the update to the live listing.
🛠️ Steps to Troubleshoot
- Wait the full propagation window. Allow at least 72 hours before concluding that a change has not applied. Google's review and propagation process varies by field type and location.
- Check your live listing directly. Open Google Maps or Search and manually verify whether the specific field you updated has changed. Do not rely solely on the preview inside Search Atlas.
- Review each changed field individually. If a batch deployment ("Deploy all changes") failed, try deploying each field one at a time. This helps identify which specific field is causing the rejection.
- Remove or correct problematic attributes. If you recently added social media links, phone number types, or custom attributes, check whether those values are still supported by Google. Remove any that may be outdated and redeploy.
- Check for yellow badge persistence. A yellow badge on a field inside Search Atlas may indicate the change is still pending or was not fully confirmed by Google, even if the deploy appeared successful. Try redeploying that specific field.
- Refresh your GBP connection. Navigate to your GBP settings inside Search Atlas and confirm your Google account connection is active and authorised. A lapsed OAuth token can cause silent failures.
📋 Common Scenarios and Fixes
- Hours not updating: Business hour changes can enter a Google-side pending state. Wait 72 hours and check again. If still not applied, remove the hours entry and redeploy.
- "Deploy all changes" fails entirely: This is often caused by one invalid field blocking the entire batch. Deploy fields individually to isolate the issue, then correct and redeploy the problematic field.
- Service areas show success but don't update: Service area changes are known to occasionally fail silently. Try removing the service area entries, saving, then re-adding and redeploying them.
- Social or action links not saving: Google periodically deprecates supported link types. Remove any link that uses an older format (such as Facebook Messenger) and redeploy the remaining changes.
✅ What a Successful Deployment Looks Like
A change is fully applied when:
- The field in Search Atlas shows no yellow pending badge.
- The update is visible on your live Google Business Profile on Google Maps or Search.
- The change has been live for at least 24 hours without reverting.
If the field still shows a pending badge after 72 hours, the deployment has likely encountered a silent rejection from Google and should be redeployed after reviewing the field value.
💬 Still Need Help?
If you have followed the steps above and your changes are still not appearing on your live listing, our team can investigate the specific deployment logs for your location. 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.