🧭 Overview
The Chrome User Experience (CrUX) report inside the Search Atlas Site Audit displays real-world performance data collected by Google from actual Chrome users visiting your site. Because this data originates from an external Google dataset rather than the crawl engine itself, it follows a different refresh cycle than other audit metrics. Understanding that distinction is the key to resolving most data-freshness issues.
🔍 Why the CrUX Report Does Not Update Immediately After a Recrawl
Running a new site audit recrawl refreshes data that Search Atlas collects directly — such as broken links, indexability signals, and on-page elements. The Chrome User Experience report is different:
- External data source: CrUX data is sourced from Google's public CrUX dataset, which Google updates on a rolling 28-day window, published once per month (typically in the first week of each month). Search Atlas cannot force Google to release new data ahead of that schedule.
- Recrawl scope: A site audit recrawl instructs the Search Atlas crawler to re-examine your site's pages. It does not trigger a new pull from the Google CrUX dataset unless the dataset itself has been refreshed since your last audit.
- Cached dataset: If the Google CrUX dataset has not been updated since your previous audit, the report will display the same figures regardless of how many recrawls you run.
- Insufficient real-world traffic: Google only includes URLs in the CrUX dataset that receive a minimum threshold of Chrome user visits. Pages with low traffic may show no CrUX data at all, or data may appear intermittently.
⚠️ Common Scenarios and What They Mean
- Recrawl completed but CrUX scores are identical: The Google dataset has not released a new monthly update yet. Wait until the dataset refreshes and then run a new audit.
- Some pages show CrUX data and others do not: Pages without data likely fall below Google's minimum traffic threshold. This is a Google-side limitation and cannot be changed from within Search Atlas.
- Scores changed in Google Search Console but not in Search Atlas: Google Search Console can display more granular or provisional data. The CrUX dataset used by Search Atlas reflects the full monthly aggregation, which may lag by a few days after Google publishes it.
- CrUX data shows for the domain but not individual URLs: Google aggregates CrUX at both the origin (domain) level and the URL level. If a specific URL lacks sufficient traffic data, only origin-level data will appear.
✅ Step-by-Step Troubleshooting
- Confirm the Google CrUX dataset has been updated. Check the Google CrUX release schedule — updates are typically published in the first week of each calendar month. If you ran your recrawl before the latest release, no new CrUX data will be available yet.
- Run a fresh recrawl after the dataset releases. Navigate to Left sidebar → OTTO SEO → Site Audit → All Audits, open your project audit, and trigger a new recrawl. The report will then pull the most recently available CrUX data.
- Check the audit timestamp. Inside your audit, confirm the date the CrUX data was last fetched. If it predates the most recent Google CrUX release, a new recrawl will resolve the discrepancy.
- Verify your site has sufficient Chrome traffic. If pages consistently show no CrUX data, cross-reference your Google Search Console → Core Web Vitals report. If data is absent there too, the pages likely do not meet Google's minimum traffic threshold.
- Review the Page Explorer for individual URL data. Navigate to Left sidebar → OTTO SEO → Site Audit → Page Explorer to inspect CrUX availability at the individual page level. This helps identify which URLs are included in the dataset and which are not.
- Check Crawl Monitoring for any crawl errors. Navigate to Left sidebar → OTTO SEO → Crawl Monitoring to confirm the recrawl completed without errors. An interrupted crawl may result in incomplete data across all report sections, including CrUX.
📋 What to Expect Going Forward
- CrUX data inside Search Atlas refreshes once per month, aligned with Google's public dataset release cycle.
- After Google releases a new dataset, run a fresh recrawl to pull the updated figures into your audit report.
- Improvements you make to Core Web Vitals will take at least one full 28-day collection window before they appear in CrUX scores.
- Origin-level CrUX data is available for most sites with any meaningful traffic, but URL-level data requires higher individual page traffic volumes.
💬 Still Need 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.