Search Console Core Web Vitals: "not enough usable data"

What’s actually happening

Open the Core Web Vitals report in Search Console and one or both tabs — Mobile and Desktop — show no URL groups at all, just the 'not enough usable data' notice. The report isn't broken. It's a direct read of Chrome UX Report data for your property, and CrUX hasn't gathered enough real Chrome visits to publish anything. A brand-new property is the usual culprit. So is a site with steady but modest traffic that simply doesn't reach the sampling threshold on, say, mobile.

Common causes

• The property is newly verified and CrUX hasn't accumulated 28 days of qualifying field data yet
• Real Chrome traffic is too low to clear CrUX's anonymity threshold, so no LCP/CLS/INP aggregate gets published
• One device type populates while the other stays empty — desktop often has data while mobile doesn't, or the reverse, depending on your audience
• The verified property doesn't match where traffic actually lands (you verified the domain property but users hit a specific subdomain, or vice versa)
• Most visitors use browsers CrUX doesn't measure, so even healthy traffic produces too few eligible samples

How to fix it

1. Confirm the property covers real trafficMake sure the verified property (domain vs URL-prefix, www vs non-www, http vs https) matches the host your visitors actually load. Cross-check against the Performance report — if pages get clicks but the property barely shows impressions, you're measuring the wrong host.
2. Check both device tabs and CrUX directlySwitch between Mobile and Desktop in the report. If one has data and the other doesn't, it's purely a per-device sample gap. Confirm with the CrUX API at origin level to see exactly which metrics and form factors have samples.
3. Use PageSpeed Insights for individual URLs nowWhile the property-wide report is empty, run key URLs through PageSpeed Insights and rely on the Lighthouse lab score to find and fix LCP, CLS, and INP issues. Don't wait on field data to start optimizing.
4. Grow traffic and wait out the rolling windowThe report fills in once CrUX has enough visits across the trailing 28 days. Get pages indexed and linked, send real users, and re-check in a few weeks — there's no setting that backfills it sooner.