15 min read · Technical SEO · Last updated July 2026
Quick answer: Most SEOs use GSC for four things: checking impressions, monitoring index coverage, viewing top keywords, and submitting sitemaps. The platform contains at least a dozen more data sources that are materially more actionable — including the Discover report, News performance, the Links report, Core Web Vitals with CrUX segmentation, the URL Inspection API for programmatic auditing, and the Search Analytics API for data that the UI never shows you.
Introduction
Google Search Console is the most underused free tool in SEO. Not because practitioners avoid it — everyone checks it — but because most use it reactively. Coverage errors appear, you investigate. A keyword drops, you glance at impressions. That is not using GSC. That is monitoring it.
Practitioners who generate meaningful results use GSC as a proactive analysis tool. They build workflows around it. They pull data the UI buries. They use the API to correlate GSC signals with deployment events. They set up filters and comparisons that surface opportunities the default view hides.
This post unpacks the GSC features that separate monitoring from mastery:
– The Discover and News reports and how to interpret their signals
– What the Links report tells you that backlink tools miss
– Core Web Vitals in GSC — what the field data means and how to use it
– URL Inspection tool advanced use cases
– The URL Inspection API for programmatic access
– GSC data filters and comparisons that generate actionable insights
– Search Analytics API use cases with working example queries
Table of Contents
- The Performance report — filters and comparisons you are not using
- Discover and News performance reports
- The Links report — what it reveals and how to action it
- Core Web Vitals in GSC — understanding field data
- URL Inspection tool advanced use cases
- URL Inspection API — programmatic auditing
- Index Coverage deep-dive
- GSC workflows that generate consistent wins
- FAQ
1. The Performance Report — Filters and Comparisons You Are Not Using
The default Performance view shows 28-day data for Search. Most practitioners leave it exactly there. The hidden value is in filtering combinations and comparison modes.
Filter combinations that surface actionable data:
CTR by position band: Add filter “Position > X” to see all keywords where you rank in positions 2–5. These are your highest-leverage CTR improvement opportunities — you are getting impressions but not clicks because your title tag or meta description is underperforming versus competitors. Sort by impressions. The top results are your priority optimisation list.
Queries containing brand terms vs. non-brand: Add a “Query does not contain [brand name]” filter to see your non-brand organic performance. This gives you a clean picture of SEO performance independent of brand demand. Many sites have 60–70% of clicks coming from branded queries — non-brand performance is what your SEO strategy actually controls.
Page-type analysis via URL filter: Filter by URL containing /blog/ to see blog content performance only, then filter by /product/ to see product page performance. Compare CTR between content types. If product pages have dramatically lower CTR at the same average position, your product page title/meta templates need work.
Device comparison: The Device dimension (in the Dimensions dropdown) lets you compare mobile vs. desktop vs. tablet performance. Sites that rank significantly lower on mobile than desktop typically have mobile usability issues — check the Mobile Usability report and Core Web Vitals mobile data in parallel.
Date comparison for ranking change analysis: Use the “Compare” feature to compare the last 28 days to the previous 28 days. Sort by click difference (descending). Pages with large click drops that do not show equivalent impression drops indicate CTR problems (you are still ranking but people stopped clicking). Pages with large impression drops indicate ranking drops — different problem requiring different solutions.
2. Discover and News Performance Reports
Google Discover Report
Google Discover (the feed that appears on Android devices and the Google app) is a traffic source that many content sites ignore — often because they do not know GSC shows Discover performance data separately.
Find it: Performance → Type → Discover (if your site has sufficient Discover traffic, this tab appears).
What the Discover report tells you:
– Which content pieces generated Discover traffic (often articles with strong visual assets and compelling headlines)
– Discover impressions vs. clicks (CTR on Discover is typically 3–8% — much lower than search because the user intent is passive browsing)
– Performance over time — Discover traffic is spiky (a piece gets featured, generates traffic for 24–72 hours, then drops off)
What makes content appear in Discover:
Google has not published a complete set of criteria, but data analysis across sites consistently shows:
– Original reporting or unique perspective (not content that aggregates what is already ranking)
– Strong featured image (at least 1200px wide — enable large image schema)
– High CTR from search (high historical CTR signals clickworthy content to Discover)
– Entity associations — content covering topics linked to entities Google’s Knowledge Graph values in your niche
Actionable use: In your Discover report, find your top 10 performing Discover posts. Analyse what they have in common — topic type, headline structure, content format, posting time. These are the content signals Discover rewards for your site. Produce more content matching those patterns.
Google News Report
The News report appears for sites included in Google News. If you publish news content and the tab does not appear, your site may not be included in Google News — you can apply via the Publisher Centre.
The News report shows article-level performance in Google News surfaces (Top Stories, Google News tab, Discover within News context). Unlike regular search, News ranking decays rapidly — a 24-hour window matters enormously.
Key News report insights:
– Which articles appeared in Top Stories (high impression counts in short time windows)
– Average position in the Top Stories carousel (positions 1–3 capture >85% of clicks)
– Publishing velocity impact — sites that publish multiple pieces per day tend to maintain News indexing priority
3. The Links Report — What It Reveals and How to Action It
The GSC Links report (left sidebar → Links) is underutilised by most practitioners who rely on third-party tools like Ahrefs or Semrush for backlink data. GSC’s links data is different — it represents what Google has actually crawled and processed, not what a third-party crawler has discovered.
External Links section:
The Top linked pages report shows which of your pages have the most inbound links from external sites. Cross-reference this against your target keyword ranking pages. If your homepage has 10,000 external links but your key money pages have 2–10 each, internal linking from the homepage and high-authority pages to money pages is a significant lever.
The Top linking sites report shows domains sending the most links to your site. This is useful for identifying:
– Unexpected link sources (sometimes reveal syndication partnerships you forgot about)
– Whether a recently acquired “guest post” link from a site has been discovered by Google
– Link concentration risk (if 40% of your links come from 3 domains, you have concentration risk)
The Top linking text report shows anchor text distribution. A heavy concentration of exact-match anchors is a risk signal. Natural backlink profiles have a mix of branded, generic, partial-match, and URL anchors. If your top anchors are all “buy [keyword] online” or “[keyword] services”, that is an over-optimisation pattern.
Internal Links section:
This is frequently the most actionable part of the Links report. GSC shows which pages receive the most internal links from your own site. Compare this list against your most important target pages.
Common finding: the homepage and blog index receive thousands of internal links (every page has a header navigation), while key product or service pages receive 3–8 internal links. The pages you most want to rank should receive the most internal links from contextually relevant content.
Build an internal link priority matrix: take your top 20 commercial pages, check their internal link count in GSC, and identify which pages should be linking to them but are not.
4. Core Web Vitals in GSC — Understanding Field Data
GSC’s Core Web Vitals report shows real-user measurement data from the Chrome User Experience Report (CrUX). This is fundamentally different from what PageSpeed Insights shows you in lab mode — it represents how actual visitors experienced your site over the past 28 days.
Reading GSC CWV as a strategy signal: The CWV report groups URLs into URL groups based on similar performance characteristics, not exact URLs. A “Poor” group might list yoursite.com/blog/... — meaning your entire blog template has poor CWV, not just one post. This grouping is key: fixing the template fixes all URLs in the group simultaneously.
5. URL Inspection Tool Advanced Use Cases
The URL Inspection tool (top search bar in GSC, or left sidebar → URL Inspection) is usually treated as a “request indexing” button. Its actual diagnostic value is significantly higher.
What URL Inspection shows that nothing else does:
Crawl date and crawler type: The tool shows when Googlebot last crawled the URL and which crawler (Googlebot Desktop or Googlebot Smartphone) was used. If your important pages show a crawl date of 3–6 weeks ago, your crawl budget may be constraining indexing freshness. Pages crawled by Desktop Googlebot but not Mobile Googlebot may have mobile-specific issues.
Canonical determination: URL Inspection shows both the canonical URL you specified and the canonical URL Google has chosen. When these differ, Google is overriding your canonical signal — a significant finding that requires investigation into why Google disagrees with your canonical choice (usually link equity signals or content signals pointing elsewhere).
Coverage status with exact reason: The indexed/not indexed status comes with a specific reason code. “Crawled — currently not indexed” is different from “Discovered — currently not indexed” — the former means Google crawled and decided not to index (quality signal); the latter means Google knows the URL exists but has not crawled it yet (crawl budget constraint).
Rendered page view: The tool renders the page as Googlebot sees it and shows you the rendered HTML. This is the primary diagnostic for JavaScript SEO issues — if your rendered view shows blank content where your JS-dependent content should be, Googlebot cannot see that content.
AMP status and rich result eligibility: For sites using AMP or structured data, URL Inspection shows validation status and whether the page is eligible for rich results.
6. URL Inspection API — Programmatic Auditing
The URL Inspection API (launched 2022) lets you query GSC’s URL Inspection data programmatically — the same data the UI shows, accessible via API call for bulk auditing.
Why this matters: The UI lets you inspect one URL at a time. The API lets you inspect thousands. Use cases:
- Post-deployment canonical verification: After a site migration, verify that 5,000 URLs are returning the expected canonical via API rather than manually clicking through the UI
- Indexing status monitoring: Script a daily check that alerts you when a critical URL transitions from Indexed to Not Indexed
- Batch crawl date analysis: Check crawl recency across all pages of a given template type to identify crawl budget distribution problems
API authentication: Uses OAuth 2.0. Quota: 2,000 requests per day per property.
Example request structure:
# Python example — URL Inspection API batch check
import json
from googleapiclient.discovery import build
from google.oauth2.credentials import Credentials
SCOPES = ['https://www.googleapis.com/auth/webmasters.readonly']
SITE_URL = 'https://yoursite.com'
URLS_TO_CHECK = [
'https://yoursite.com/products/red-shoes',
'https://yoursite.com/products/blue-boots',
# ... up to 2000/day
]
def check_url_status(service, site_url, inspection_url):
result = service.urlInspection().index().inspect(
body={
'inspectionUrl': inspection_url,
'siteUrl': site_url,
}
).execute()
return {
'url': inspection_url,
'indexing_state': result['inspectionResult']['indexStatusResult']['indexingState'],
'coverage_state': result['inspectionResult']['indexStatusResult']['coverageState'],
'google_canonical': result['inspectionResult']['indexStatusResult'].get('googleCanonical', 'N/A'),
'user_canonical': result['inspectionResult']['indexStatusResult'].get('userCanonical', 'N/A'),
'last_crawl': result['inspectionResult']['indexStatusResult'].get('lastCrawlTime', 'Never'),
}
# Build service, loop through URLs, export to CSV for analysis
Practical use case — canonical migration verification:
After moving a site from HTTP to HTTPS, run the API against your top 200 URLs. Filter results where google_canonical != user_canonical. Each mismatch is a page where Google has chosen a different canonical than you specified — these are your highest-priority manual investigation items.
7. Index Coverage Deep-Dive
The Coverage report (now called “Indexing” in the updated GSC interface) is more nuanced than the headlines suggest. The categories that generate the most questions:
“Crawled — currently not indexed”: Google crawled the page but chose not to index it. This is a quality signal, not a technical error. Google’s algorithm determined the page did not meet its quality threshold for inclusion. Fix: improve content depth, originality, and E-E-A-T signals. Do not try to force-index thin pages.
“Discovered — currently not indexed”: Google knows the URL exists (found it in a sitemap or via a link) but has not crawled it yet. This is a crawl budget issue. If critical pages are here, your crawl budget is being consumed by lower-priority pages. Fix: improve internal linking to priority pages, reduce crawlable low-value URLs (thin archives, parameter URLs).
“Alternate page with proper canonical tag”: This is expected and correct for non-canonical URLs (like your collection-scoped Shopify product URLs). If your intended canonical URLs appear here instead of the correct target, investigate why Google has chosen a different canonical.
“Excluded by ‘noindex’ tag”: Expected for pages you have noindexed. If pages you want indexed appear here, you have an accidental noindex tag — check your CMS settings, theme templates, and any A/B testing tools that may be adding noindex to variant pages.
8. GSC Workflows That Generate Consistent Wins
FAQ
Q: How long does GSC data lag behind reality?
A: GSC data typically lags 2–3 days for Performance data and 3–5 days for Coverage/Index data. When you make changes, allow at least 7 days before evaluating impact in GSC. The CWV data is based on a 28-day rolling window — improvements in site speed take up to 28 days to fully reflect in GSC CWV scores.
Q: Why does GSC show different keyword rankings than tools like Ahrefs?
A: GSC shows personalised, location-specific data for real Google Search queries from your actual users. Third-party tools simulate queries from specific locations using automated crawlers. The data sources are fundamentally different. GSC impressions and clicks are accurate for your audience; third-party tools provide broader market visibility data.
Q: What is the GSC Search Analytics API limit?
A: The API returns up to 25,000 rows per request, with a maximum of 16 months of historical data. The URL Inspection API has a quota of 2,000 requests per day per property. The Search Analytics API quota is higher — contact Google for elevated limits if you need more.
Q: Should I submit URLs via URL Inspection or just update my sitemap?
A: Both. Submitting a URL via Inspection triggers immediate crawling of that specific URL. Updating your sitemap and re-submitting it in GSC signals Google to re-evaluate the full URL list. For individual high-priority page changes, use URL Inspection. For bulk changes (new site section, major content update), update the sitemap.
Q: How do I identify zero-click queries in GSC?
A: Filter Performance by Impressions > 100 and CTR < 1%. These are queries where your content appears but almost no one clicks — often because Google provides the answer directly in a featured snippet, knowledge panel, or People Also Ask box. Understanding your zero-click exposure helps prioritise which queries to target and which to deprioritise.
Conclusion
Google Search Console’s most valuable features are the ones that require active analysis — not passive monitoring. The Discover report reveals content amplification patterns. The Links report surfaces internal equity distribution problems. CWV field data identifies real user experience failures lab tools miss. The URL Inspection API enables systematic auditing at scale. The workflow library above generates consistent, reproducible wins when applied monthly.
The difference between practitioners who treat GSC as a monitoring dashboard and those who treat it as a strategic tool shows up in results. Build the workflows. Run them on a schedule. Act on what you find.
Want help building GSC-driven SEO workflows for your site? Ignited Nepal works with clients across Nepal, Australia, UAE, USA, UK, Japan, Canada, and Qatar — implementing systematic GSC-based performance programmes that compound over time.
Talk to Ignited Nepal About Your SEO → ignitednepal.com
Written by the Ignited Nepal team. ignitednepal.com