Google Search Console for SEO: How to Use Every Report That Matters

Google Search Console (GSC) is the most important free SEO tool available, because it's the only tool that shows you data directly from Google: which queries your site ranks for, which pages Google has indexed, which pages it can't crawl, and whether your Core Web Vitals meet Google's thresholds.

Everything else — Ahrefs, Semrush, Moz, any third-party rank tracker — is estimated from data they collect themselves. GSC shows you what Google actually sees.

This guide covers every report in GSC that has meaningful SEO value, what to look for in each, and what to do with what you find.

Setting up Google Search Console

Before you can use GSC, you need to verify ownership of your site. Two property types:

Domain property (sc-domain:yoursite.com) — covers all subdomains (www, blog, mail) and both HTTP and HTTPS. This is almost always the right choice. Verification requires adding a DNS TXT record.

URL-prefix property (https://www.yoursite.com) — covers only the exact URL prefix you enter. Less comprehensive; use if you only want to track a specific subdomain.

After verification, GSC takes 24–48 hours to start accumulating data. Historical data doesn't backfill — GSC only shows data from the day you verified onward, so verify early and leave it running.

Performance report

The Performance report is the most valuable report in GSC for day-to-day SEO work. It shows:

• Clicks — the number of times users clicked a result that led to your site
• Impressions — the number of times a URL appeared in search results (even if it was below the fold)
• CTR (click-through rate) — clicks divided by impressions
• Average position — the average ranking position across all queries where the URL appeared

What to do with it:

1. Find striking-distance keywords. Filter by Search type: Web, then sort by Impressions descending. Add a Position filter showing positions 4–20. These are queries where you're ranking on the first page but not in the top 3 — and top-3 positions get 3–7x the CTR of positions 4–10. These are your highest-ROI optimisation targets: Google has already confirmed topical relevance by ranking you; improving the page depth, strengthening internal links, and potentially earning a few backlinks can move from position 8 to position 3.

2. Find low-CTR pages that are ranking well. Filter for positions 1–5 with CTR below 3%. For informational queries in position 1, typical CTR is 25–35%. If you're ranking position 2 with 1% CTR, the title and meta description aren't earning clicks — rewrite them to match the query's intent and trigger more clicks from the existing ranking.

3. Monitor 6-month trends. Set the date range to the last 6 months and use the Dimensions tab to view by Page. Identify which pages are trending up (build on them) and which are declining (investigate content decay or new competition).

4. Check the Queries tab for each top page. Click a page in the Pages tab, then switch to the Queries tab to see every query that page ranks for. You'll often find secondary keywords where the page gets impressions but isn't well-optimised — adding a section or FAQ item targeting that secondary query can consolidate more traffic into the existing URL.

Index Coverage report

The Index Coverage report (now called "Pages" in the updated GSC interface) shows which of your URLs Google has crawled and indexed, and which it hasn't — and why.

Status categories:

• Valid — the page is indexed and eligible to appear in search results
• Valid with warnings — indexed but with a potential issue (e.g., indexed but with a noindex tag on an alternate hreflang page)
• Excluded — not indexed, but not because of an error; examples: crawled but not indexed (Google chose not to index it), redirect, canonical (Google chose a different canonical), noindex directive
• Error — not indexed because of a crawl or indexing error; examples: 404 (not found), server error (5xx), URL blocked by robots.txt

What to look for:

Unexpectedly low valid URL count. If you have 500 pages on your site but only 200 are indexed, that's index bloat — Google chose not to index 300 pages, often because they're thin, duplicate, or low-quality. Review the "Crawled, currently not indexed" and "Discovered, currently not indexed" categories.

404 errors on pages that should exist. 404s on pages you care about are a crawl waste. Find and fix the underlying cause — a broken internal link pointing to an old URL, a sitemap entry with an outdated path.

Noindex pages that shouldn't be noindexed. Scan the "Excluded by 'noindex' tag" count. Sometimes a staging environment noindex gets shipped to production, or a CMS plugin adds noindex to the wrong content type.

Redirect chains. GSC flags redirect loops and chains as errors. These waste crawl budget and lose some PageRank at each hop — consolidate to direct canonical URLs.

Sitemap report

The Sitemap report shows which sitemaps you've submitted and their status: how many URLs were submitted versus how many were discovered and indexed.

Submit your sitemap if you haven't. Go to Sitemaps → Add a new sitemap, enter your sitemap URL (typically /sitemap.xml). This helps Google discover URLs faster — especially for new content.

Watch the submitted vs. indexed ratio. If you've submitted 500 URLs but Google has only indexed 200, the 300 unindexed URLs need investigation in the Index Coverage report. Common causes: pages are thin, they're too similar to other indexed pages, or they have technical issues preventing indexing.

Keep the sitemap accurate. Sitemaps should only include URLs you want indexed: no paginated pages (unless they use rel=next/prev), no filtered e-commerce variants without canonical tags, no draft content. A sitemap full of low-value URLs dilutes Google's attention and hints that your site has a quality problem.

Core Web Vitals report

The Core Web Vitals report in GSC shows real CrUX field data — actual Chrome users' experience — for LCP, INP, and CLS, grouped by Good / Needs Improvement / Poor. This is the same data Google uses as a Page Experience ranking signal.

Why this matters more than PageSpeed Insights. PageSpeed Insights shows lab scores (a simulated Lighthouse test). The GSC Core Web Vitals report shows field data from real users on real devices and real connections — which is what Google actually uses. A page can score 90+ in Lighthouse but show Poor CLS in the field because of ad injection or dynamic content loading that the lab test doesn't replicate.

What to look for:

Pages with "Poor" status. Click "Poor" to see which specific URLs are classified as Poor for each metric. These are the highest-priority CWV fixes — they're actively affecting your Page Experience signal.

LCP issues. Poor LCP is most commonly caused by: slow server response time (TTFB above 800ms), render-blocking resources delaying LCP image load, and LCP images without loading="eager" or fetchpriority="high". For Next.js sites, the priority prop on the above-the-fold image resolves most LCP issues.

INP issues. Poor INP (>500ms) indicates the page is unresponsive to interactions — typically caused by long tasks blocking the main thread, heavy JavaScript frameworks with synchronous re-renders, or third-party scripts executing during user input handling.

CLS issues. Poor CLS (>0.25) is most often caused by images without explicit dimensions, dynamically injected ad slots or banners, and web fonts causing a Flash of Invisible Text (FOIT) or Flash of Unstyled Text (FOUT). Fix: always set width and height on images; use font-display: swap and next/font.

URL Inspection tool

The URL Inspection tool lets you check a specific URL to see: whether it's indexed, what the rendered HTML looks like (after JavaScript execution), what canonical URL Google is using, and any crawl or indexing issues.

Most useful for:

Debugging missing pages. If a page you expect to be indexed isn't appearing in search results, inspect the URL to find out if Google has crawled it, what issues were found, and what version of the page it rendered.

Checking JavaScript-rendered content. For pages that use client-side rendering, the rendered HTML view shows what Googlebot actually sees after running JavaScript. If your page content, headings, or structured data only appear in the rendered HTML (not the raw HTML), Google uses the rendered version — but there's a delay for JS-rendered pages that can affect how quickly new or updated content appears in the index.

Requesting indexing for new or updated pages. After publishing a new page or making a significant update to an existing one, use "Request Indexing" in URL Inspection to ask Google to crawl it soon. This doesn't guarantee immediate indexing but typically speeds it up from days to hours for pages Google already trusts.

Manual Actions

The Manual Actions report shows whether Google has applied a manual penalty to your site or specific pages. Manual actions are issued by Google's human reviewers when a site violates Google's spam policies — examples: unnatural links, thin or auto-generated content, cloaking, hidden text.

What to do if you have a manual action:

Most sites don't have manual actions — they're relatively rare. If you do:

1. Read the specific action and the linked policy violation
2. Fix the underlying issue (remove unnatural links via the disavow tool, remove thin content, fix the cloaking)
3. Submit a reconsideration request describing what you found and fixed

Manual actions aren't the same as algorithmic demotion from a Helpful Content or Core Update. Algorithmic changes don't appear in Manual Actions — you'd see the effect in the Performance report as a traffic drop around the update date.

Security Issues

The Security Issues report flags if Google has detected malware, suspicious downloads, deceptive pages, or hacked content on your site. If your site appears here, it may be showing a warning in search results to users.

Security issues require immediate action: investigate for malware or compromised code, clean the infection, then request a review. This is separate from SEO optimisation — it's a technical emergency.

Connecting GSC to your SEO audit

GSC data and a technical site audit complement each other: GSC shows you what Google sees and how it's responding; a technical audit shows you why. If GSC shows declining impressions on a group of pages, the technical audit can identify whether canonical tags, noindex directives, internal link depth, or content quality issues are the likely cause.

To verify your site's technical health alongside GSC data, run the DeepSEOAnalysis free audit.

---

Frequently asked questions

How long does it take for GSC data to appear?

After verifying your site in GSC, data starts accumulating immediately, but it typically takes 24–48 hours for the first data to appear in reports. The Performance report has a 2–4 day lag — data from today won't show in the Performance report for a few days. This is normal. The URL Inspection tool shows near-real-time crawl status for individual URLs.

Why is my site ranking in Google but not showing in GSC?

If your site appears in Google search results but shows no data in GSC, you're either looking at the wrong property (check that the GSC property matches your exact domain and protocol), or the site was recently verified and data hasn't accumulated yet. It's also possible the rankings are appearing in a different country or Search type (Images, News, Discover) than the default filter shows.

What is a "crawled but not indexed" URL in GSC?

"Crawled, currently not indexed" means Google crawled the URL and read the content, but chose not to add it to the index. This is a quality signal, not a technical error. Common reasons: the page is thin (too little unique content), it's too similar to other indexed pages (near-duplicate), or Google assessed it as low-value relative to the rest of the site. Fix: improve the content depth and uniqueness of the page, or consolidate it with a related page via a 301 redirect and update the canonical.

Should I submit every URL to GSC?

No — submit your XML sitemap, which includes only the URLs you want indexed. GSC's "Request Indexing" feature in URL Inspection is for individual new or significantly updated pages you want crawled quickly. Don't submit low-value pages, paginated pages, or filtered URL variants — doing so tells Google to prioritise crawling URLs you'd actually prefer it to skip, which wastes crawl budget.