You open Google Search Console expecting the usual graph, the clicks, the impressions, the queries you've come to check on every Monday morning. Instead you're staring at a flat line, a blank table, or a cheerful "No data available." Your site is live. People are visiting. And yet the one dashboard that's supposed to tell you how Google sees you has gone silent.
It's an unsettling feeling, because Search Console is where you find out whether your SEO work is paying off. When it stops reporting, you're flying blind. The good news: almost every cause of missing GSC data is mundane, fixable, and falls into one of a handful of buckets. This guide walks through each one, from the trivial to the serious, so you can figure out which is yours and get your numbers back.
First, rule out the boring explanations
Before assuming something is broken, check the explanations that account for the majority of "no data" panics. They're unglamorous, but they're usually the answer.
The data delay
Search Console is not real-time. Performance data typically lags by two to three days, and some reports take longer to populate. If you're looking at today or yesterday, an empty tail on the graph is completely normal. Set the date range to the last 28 days and look at whether the older days have data. If they do, you're just looking too early.
A brand-new property
If you only just added and verified your site in Search Console, there's nothing to show yet. Google starts collecting data from the moment of verification, it does not backfill history from before you added the property. A new property can take a few days to begin showing performance data and longer to populate the Indexing and Experience reports. Patience is the fix here.
The wrong date range or filters
It sounds obvious, but it's astonishingly common: a date range set to a single empty day, a filter left on from last session restricting results to one page or one country with no traffic, or a comparison view that's confusing you. Clear all filters, widen the date range, and see if the data reappears.
You're looking at the wrong property
Many sites have multiple properties registered: http:// and https:// versions, www and non-www, plus a Domain property. Traffic might be flowing into one while you're staring at another. If you have a URL-prefix property showing nothing, check whether a Domain property exists and holds the data instead.
Verification and access problems
If the boring explanations don't apply, the next thing to check is whether Google still trusts that you own the site.
Verification has lapsed
Search Console requires ongoing proof of ownership. If your verification was done via an HTML file, a meta tag, a DNS record, or a Google Analytics/Tag Manager connection, and that method was later removed, your verification breaks. This happens constantly during redesigns and migrations: someone strips out a meta tag they didn't recognize, or a new theme overwrites the verification file. Once verification lapses, data collection and access stop.
Check the Settings > Ownership verification section to confirm your method is still valid. Re-verifying with a second method as backup is good insurance.
The verification method got disturbed by a site change
The single most frequent trigger is a launch or migration. A meta verification tag lives in your <head>, and any deploy that rebuilds your templates can quietly drop it. This is the same category of silent, launch-day damage that produces broken links and stray placeholder text, the kind of thing covered in our guide to auditing your website before a launch. The fix is to restore the verification token and confirm it in Search Console.
Crawling and indexing problems
This is the serious bucket. If Google genuinely can't crawl or index your pages, there will be no performance data because there's nothing in the index to generate impressions.
Your site is blocked by robots.txt
A misconfigured robots.txt file can tell Google to stay out of your entire site. The classic culprit is a Disallow: / rule shipped from a staging environment to production. If Google can't crawl your pages, they can't accumulate impressions or clicks, and your Performance report stays empty. Visit https://yourdomain.com/robots.txt and confirm you don't see a site-wide disallow.
A stray noindex tag
If your pages carry a noindex meta robots tag or X-Robots-Tag header, again, often left over from a staging build, Google will drop them from the index. No indexed pages means no search data. The Page Indexing report will show pages excluded by noindex if this is the cause.
Pages aren't indexed yet
Use the URL Inspection tool on a few key pages. If it reports "URL is not on Google," your pages haven't been indexed, which explains the silence. For a new or recently restructured site, indexing can take days to weeks. Submitting your sitemap and requesting indexing on priority pages speeds it along.
The site genuinely gets no search traffic
This is the hardest one to hear, but it's real: if your site is brand new, very small, or targets terms no one searches, it may simply have zero impressions to report. "No data" in this case isn't a bug, it's an accurate reflection that the site isn't appearing in search yet. The fix isn't in Search Console; it's in publishing crawlable, indexable content that answers real queries, with the meta tags and structure that help Google understand it. Missing or weak meta descriptions and titles won't stop indexing, but they do affect how often people click once you do appear.
Data discrepancies and partial gaps
Sometimes the data isn't fully missing, it's lower than expected, missing from one report but not another, or different from what Google Analytics tells you. A few common reasons:
- Anonymized queries. Search Console hides search terms that very few people use to protect privacy, so the query table never accounts for 100% of your clicks.
- GSC and Analytics measure different things. Search Console counts impressions and clicks from Google Search; Analytics counts on-site sessions across all sources. They will never match exactly, and that's expected.
- Report-specific delays. The Performance report updates faster than Indexing, Experience, or Enhancement reports. One being empty while another has data is often just timing.
- Property type differences. Domain properties aggregate all subdomains and protocols; URL-prefix properties only cover an exact match. The same site can look very different across the two.
A quick diagnostic checklist
When the data's missing, work through this in order and you'll almost always land on the cause:
- Widen the date range to the last 28 days and clear every filter.
- Confirm you're viewing the correct property (Domain vs. URL-prefix, www vs. non-www).
- Check that ownership verification is still valid under Settings.
- Open
robots.txtand confirm there's no site-wideDisallow: /. - Run a few pages through URL Inspection to confirm they're indexed and free of
noindex. - Submit or re-check your sitemap.
- If the property is brand new, wait several days and check again.
Where Steterly fits in
Most of the reasons Search Console goes quiet share a theme: something on your site changed, broke, or was misconfigured without anyone noticing. A verification tag dropped during a deploy. A noindex left in from staging. A robots.txt rule that locks crawlers out. None of these announce themselves, the site looks perfectly fine to a human visitor while Google is being turned away in the background.
Steterly is a whole-site quality scanner that surfaces exactly that kind of invisible decay. It crawls your site the way a search engine would and flags the things that quietly cost you visibility and trust: broken links, missing or broken images, typos, outdated copyright years, leftover placeholder text, missing meta titles and descriptions, and Core Web Vitals issues. Run it after a launch or migration and you catch the template-level breakage that also tends to take your Search Console verification and indexing down with it.
You can start with a free scan of up to 50 pages, no credit card required. Create a free account, run a scan, and get a clear, prioritized report of what needs attention, so the next time Search Console goes quiet, you can rule out a broken site in minutes instead of days.
Frequently asked questions
How long does Google Search Console take to show data?
For a brand-new verified property, performance data usually begins appearing within a few days, and Indexing and Experience reports can take longer. For an existing property, remember that data lags by two to three days, so the most recent days on the graph will often look empty even when everything is working normally.
Why is my Search Console performance report empty but the site is live?
The most common causes are a date range or filter hiding the data, viewing the wrong property, lapsed ownership verification, or the site being blocked from crawling or indexing by a robots.txt rule or a noindex tag. Work through those in order and you will usually find the cause quickly.
Does adding a site to Search Console show historical data?
No. Google only starts collecting data from the moment you verify the property and does not backfill anything from before that point. If you just added your site, the absence of older data is expected and not a sign that anything is broken.
Can robots.txt or noindex cause missing Search Console data?
Yes. If your robots.txt blocks Google from crawling your pages or a noindex tag removes them from the index, those pages cannot accumulate impressions or clicks, so the Performance report stays empty. Check robots.txt for a site-wide disallow and use URL Inspection to confirm key pages are indexed.
Why doesn't Search Console match Google Analytics?
They measure different things. Search Console counts impressions and clicks from Google Search only, while Analytics counts on-site sessions from all traffic sources. They also use different time zones and processing windows, so the two will never match exactly, and a gap between them is completely normal.
Why did my Search Console data suddenly stop after a redesign?
Redesigns and migrations frequently strip out the verification token from your site templates or introduce a stray noindex or robots.txt block. Any of these will interrupt data collection. Re-check ownership verification under Settings and confirm your pages are still crawlable and indexable.