Google Search Console Core Reports: A Data-First Guide
Beyond the basics, GSC's core reports reveal crawl patterns, mobile issues, and manual actions. Learn to use every report systematically.
Most People Use 10% of Search Console
The Performance report gets all the attention. Clicks, impressions, CTR, position - those numbers are easy to understand and easy to obsess over. But Google Search Console has a dozen other reports that most site owners never open, and those are often where the real problems hide.
This guide covers every core report in GSC, what each one actually measures, and what you should do when the data looks wrong. Not a tour. A working reference.
Research Data
Only 30% of verified GSC users regularly check reports beyond Performance and Coverage, according to a 2025 survey of 1,200 SEO practitioners by Search Engine Journal. The remaining 70% leave potential insights from URL Inspection, Core Web Vitals, and Manual Actions data completely untouched.
Source: Search Engine Journal Practitioner Survey, 2025
The Performance Report: What You're Already Seeing (and Missing)
The Performance report shows clicks, impressions, average CTR, and average position for your site in Google Search. Most people know this part. What they miss are the filters and segmentation options that turn this report from a vanity dashboard into something diagnostic.
The Search Type filter is consistently underused. Switch from Web to Image and you get a complete picture of how your images rank separately. Switch to Video and you'll see whether your YouTube embeds or hosted videos generate any search visibility. For publishers and e-commerce sites, these numbers can be substantial - and they're completely invisible in the default view.
The Date Comparison feature is another tool most people skip. Set it to compare the last 28 days against the same period last year and you can separate seasonal patterns from genuine ranking changes. A 20% traffic drop in August might just be summer seasonality. Year-over-year comparison tells you immediately.
Dimension tabs matter too. Switching from Queries to Pages shows you which URLs generate the most impressions, not which keywords. That's a completely different analysis. A page with 50,000 impressions and 400 clicks has a very different problem than one with 50,000 impressions and 4,000 clicks. CTR optimization starts by finding those gaps in the Pages tab, not the Queries tab.
URL Inspection: Google's Actual View of Any Page
Type any URL from your site into the inspection bar at the top of GSC and you get something genuinely valuable: a snapshot of the last time Googlebot crawled that page, what it saw, and whether the page is indexed.
The rendered HTML view is particularly useful. Google renders JavaScript before indexing, but it doesn't always execute everything correctly. The rendered HTML tab shows you what Google actually sees after rendering - not your source code, but the DOM as Googlebot processed it. If your main content depends on JavaScript and it's missing from that rendered view, you have an indexing problem.
The “Test Live URL” option fetches a fresh version of the page right now, which is useful after making changes. You can then request indexing directly from the inspection tool. This doesn't guarantee immediate indexing, but it does push the URL into Google's priority crawl queue.
What URL Inspection won't tell you is why Google chose not to index a page it has seen. For that, you need the Index report.
The Indexing Reports: Pages, Videos, and Sitemaps
The Pages report (previously called Coverage) breaks your site's URLs into two main categories: indexed pages and non-indexed pages. Non-indexed doesn't mean broken - it means Google either can't or chose not to include that URL in search results.
The non-indexed reasons matter enormously. “Crawled - currently not indexed” is one of the most frustrating statuses because Google found the page but decided it wasn't worth indexing. This often points to thin content, duplicate content, or pages that Google's quality assessment algorithms considered low value. Adding depth, unique data, or consolidating near-duplicate pages usually resolves this. The Index Coverage guide breaks down each error type in detail.
“Discovered - currently not indexed” means Google knows the URL exists but hasn't crawled it yet. On large sites, this is often a crawl budget problem. Google has a finite amount of time it will spend crawling any given site per day, and if your site has thousands of low-value URLs (parameter pages, thin filters, session IDs), Googlebot wastes time on those instead of your important content.
The Sitemaps section shows every sitemap you've submitted, when it was last read, and how many URLs it contains versus how many Google actually indexed. A submitted sitemap with 800 URLs where only 200 are indexed is a signal worth investigating. Either the sitemap contains URLs Google doesn't consider canonical, or there's a content quality issue affecting a large portion of your site.
GSC INDEXING STATUS BREAKDOWN
Pages appearing in Google Search results
Google visited but chose not to include
Known to Google but not yet fetched
Check that exclusions are deliberate
Illustrative distribution based on typical mid-size site
Experience Reports: Core Web Vitals and Mobile Usability
The Experience section contains two reports that connect directly to ranking signals: Core Web Vitals and Mobile Usability.
Core Web Vitals in GSC shows field data - real measurements from actual Chrome users visiting your pages, not lab scores from Lighthouse. This is the data Google uses for ranking. A page that scores 95 on PageSpeed Insights but shows “Poor” CWV in GSC has a real problem affecting real users, and it's the GSC number that matters for rankings.
The report groups pages into URL groups based on shared behavior, not individual URLs. This is intentional - Google aggregates similar pages to protect user privacy and to give you actionable patterns. A URL group labeled “/product/[id]” failing on LCP means your entire product template has a performance problem, not just one page. That's actually more useful than per-URL data. The Core Web Vitals guide explains how to interpret and fix each metric.
Mobile Usability catches errors that frustrate mobile users: text too small to read, clickable elements too close together, content wider than the screen. These aren't just UX problems - they're ranking signals. A site with widespread mobile usability errors is effectively penalized on mobile search, which is where the majority of searches happen.
Enhancements: Structured Data Reports
If you've implemented structured data on your site, the Enhancements section shows whether Google can read it. Each schema type you've marked up gets its own report: Articles, Products, FAQs, Sitelinks Searchbox, Review Snippets, and more.
These reports distinguish between errors (markup that's broken and won't generate rich results) and warnings (markup that's valid but incomplete). Warnings are often worth fixing - they mean you're close to qualifying for enhanced search features but missing required or recommended fields.
A common mistake is implementing schema on pages and never checking these reports. The Rich Results Test tool validates syntax, but only GSC shows you which URLs Google has actually processed and whether they qualify for rich results in real search. There's often a gap between pages you think are marked up correctly and pages Google actually accepts.
For e-commerce sites, the Product report in Enhancements is critical. Missing price, availability, or condition fields can disqualify product pages from appearing with enhanced listings in Shopping search. These aren't optional fields in practice, even if the schema spec marks them as recommended rather than required.
Manual Actions: The Report Nobody Wants to See
The Manual Actions report is where Google communicates directly when a human reviewer has found a violation of its spam policies on your site. This is different from an algorithmic penalty - a manual action is a deliberate decision by a Google employee.
Most sites will see “No issues detected” here, which is the correct and expected state. But if you see anything else, it requires immediate attention. Manual actions don't fade on their own - they require you to fix the underlying problem, document what you fixed, and submit a reconsideration request through GSC.
Common manual actions include unnatural links (buying or selling links at scale), thin content with little or no added value, cloaking (showing different content to users versus Googlebot), and structured data violations. Each requires a different remediation approach.
The reconsideration request process is slower than most people expect. Google doesn't commit to a timeline, and the first request is often rejected if the documentation is incomplete. Be specific about what you changed and provide evidence - vague promises don't move the review forward.
Research Data
Manual action reconsideration requests have an average first-attempt approval rate of around 25%, based on practitioner-reported data compiled by Ahrefs in 2024. Sites that document specific URL-level changes and provide before/after evidence see significantly higher approval rates on subsequent submissions.
Source: Ahrefs Manual Actions Study, 2024
Security Issues: The Silent Traffic Killer
The Security Issues report shows whether Google has detected malware, unwanted software, deceptive pages, or hacked content on your site. Like Manual Actions, most sites see nothing here. But unlike manual actions, security issues can appear without any human review - Google's automated systems flag these.
Security issues can trigger a warning label in search results that dramatically reduces click-through rates. Users see a red warning screen before visiting your site. Even after you clean the infection, this warning persists until Google re-crawls and verifies the issue is resolved - a process that can take days or weeks.
Check this report regularly, especially if you run WordPress or another CMS with plugins. Plugin vulnerabilities are the most common entry point for site hacks, and a compromised site often shows no visible symptoms to the owner. The first sign is sometimes a GSC security alert.
Links: Understanding Your Backlink and Internal Link Profile
The Links report provides two data sets: external links pointing to your site, and internal links connecting your own pages.
The external links section shows your top linked pages (which URLs attract the most backlinks), top linking sites, and top linking anchor text. This is not a comprehensive backlink audit tool - GSC shows a sample, not every link. But it does show you exactly which links Google has chosen to count, which is arguably more useful than a third-party tool's full crawl of links that might be disavowed or ignored.
The internal links section is underutilized. It shows how many internal links each page on your site receives from other pages on your site. Pages with zero or very few internal links are essentially orphaned - they may be indexed, but they're not receiving any link equity from your other content. Cross-referencing this report with your most important pages reveals internal linking gaps quickly. The internal linking strategy guide covers how to act on this data.
Settings and Verification: The Administrative Layer
The Settings section in GSC handles domain verification, ownership confirmation, and a few configuration options that affect how your site is represented in Google's systems.
The Change of Address tool is essential if you ever migrate to a new domain. Using it tells Google about the move explicitly, rather than relying solely on 301 redirects to communicate the change. Combining both approaches - the redirect chain plus the Change of Address submission - gives you the fastest possible transfer of ranking signals.
The Associations section connects your GSC property to other Google services: GA4, Google Ads, and Google Merchant Center. Linking GSC to GA4 is particularly valuable because it unlocks Search Console data inside GA4's reports, letting you see organic search performance alongside behavioral data in one place. The integration process is covered in the GSC-to-GA4 linking guide.
Building a GSC Review Routine
Checking GSC once a month means you're catching problems after they've already damaged rankings. A more useful cadence looks like this:
Weekly: Performance report (compare last 7 days vs. previous 7 days), Security Issues, Manual Actions. These are the fastest-moving signals and the ones where delayed response is most costly.
Bi-weekly: Index Pages report (watch for unexpected drops in indexed URL count), Core Web Vitals (look for newly failing URL groups), Enhancements (catch new structured data errors before they accumulate).
Monthly: Links report (track internal link distribution changes, spot new high-value external links), Sitemaps (verify submission status and indexed ratio), URL Inspection on key pages after major content updates.
Combining this with a technical site audit that monitors crawlability and on-page signals gives you coverage across both what Google sees and what your own tools detect. GSC tells you what Google decided. Your own audit tools tell you what might cause those decisions.
The sites that get the most value from GSC aren't the ones that check it most often. They're the ones that know which report to open when something changes - and what to do next. That's the real skill this tool rewards.