Even when your sitemaps show a Success status in Google Search Console (GSC) and have been submitted for weeks, that data may not immediately appear in the sitemap section of Search Atlas. This is a known sync behaviour and does not mean your sitemaps are broken.
Here is what causes the delay and what you can do about it:
Search Atlas pulls sitemap data from GSC via the API on a scheduled basis. This means:
Data displayed in Search Atlas reflects a snapshot from a previous sync cycle, not real-time GSC data.
Dates shown may appear stale because sitemap data is not refreshed in real time.
A sitemap showing Success in GSC does not guarantee that the indexing data has been processed and delivered to Search Atlas yet.
This is expected behaviour during the current product cycle.
If you notice that Google Ads data is not appearing in Search Atlas or seems out of date, the most common causes are:
Stale account sync: The platform may be displaying data from a previous sync without clearly indicating that a newer sync failed or is pending.
Manual changes not reflecting: Updates made directly in Google Ads (outside of Search Atlas) may take time to appear after a sync cycle completes.
Confirm that your Google Search Console connection is active and that your sitemap status shows Success in GSC.
Check whether updates made directly in Google Ads are reflected — if not, the sync cycle may still be in progress.
Note the specific ads, campaigns, or sitemaps affected and the approximate time the issue started.
Because there is no confirmed self-serve refresh option for sync issues of this type, escalate to the support team with the following information ready: your project or domain name, the affected ads or sitemap URLs, and the approximate time you first noticed the missing data.
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.