Your shopping cart is empty!
Google Search Console: Complete Guide for SEO
Google Search Console shows which queries drive traffic, which pages are excluded from the index and where Core Web Vitals failures are — free, directly from Google, with no third-party tools required. Running SEO without GSC means working without ground-truth data.
Contents
- What Google Search Console is and why it matters
- Adding and verifying your property
- Performance report: clicks, impressions, CTR, position
- Coverage report: indexation and errors
- URL Inspection Tool
- Core Web Vitals in Search Console
- Links report
- Sitemaps and robots.txt
- Manual actions and site security
- Monthly SEO audit via GSC: checklist
- Frequently asked questions
What Google Search Console is and why it matters
Google Search Console (formerly Google Webmaster Tools) is Google's free service showing how the search crawler sees your site. Unlike Google Analytics 4, which measures user behaviour after a visit, GSC records Googlebot's interaction with your site: what has been indexed, what has been excluded, where errors exist, and which queries trigger your pages in search results.
GSC solves three problems that make systematic SEO impossible without it. First — organic visibility monitoring: which queries and pages generate clicks, where CTR falls below benchmark, where positions have slipped. Second — technical diagnosis: crawl errors, indexation problems, Core Web Vitals failures, security warnings. Third — change verification: confirming Google has processed your post-audit fixes.
Official documentation: Getting started with Search Console — features overview and access requirements. The tool itself is available at search.google.com/search-console — free for any Google account.
Three tools that SEO professionals use simultaneously — and what each uniquely provides:
| Tool | What it measures | Data source | Cost |
|---|---|---|---|
| Google Search Console | Organic traffic, indexation, technical status, CWV | Google — primary data | Free |
| Google Analytics 4 | On-site user behaviour, conversions, all traffic channels | JavaScript tag on the site | Free |
| Ahrefs / Semrush | Competitor keywords, backlinks, ranking trends over time | Proprietary crawler and databases | From $99/mo |
We connect GSC to every new project on day one. Across 200+ projects, sites without GSC lose an average of 2–3 months identifying technical problems that GSC would have surfaced immediately. Without it, you are making strategic decisions based on third-party data instead of the primary source.
Adding and verifying your property
Only a Google account owner can add a site to GSC. The first decision is property type:
| Property type | Data scope | When to use |
|---|---|---|
| Domain property | Full domain: http and https, all subdomains (www, blog, shop) | Always — if you have DNS panel access |
| URL-prefix property | A specific protocol and path (e.g. https://example.com only) | If DNS access is unavailable, or you need separate data for a subdomain |
Verification methods — from fastest to most resilient:
- Google Analytics — if GA4 is already installed with the code in
<head>, verification completes automatically in one click - Google Tag Manager — same via GTM if the container is deployed on the site
- HTML tag — a meta tag in
<head>. WordPress plugins like Yoast or Rank Math add it automatically - HTML file — upload the file to the root directory via FTP or the hosting control panel
- DNS TXT record — required for Domain property. The most resilient option: verification persists even after a CMS or theme change
Performance report: clicks, impressions, CTR, position
Performance is the central GSC report for evaluating organic traffic. Data is stored for the past 16 months. Four metrics together give the complete picture of your site's visibility in Google:
| Metric | What it measures | Working benchmark |
|---|---|---|
| Clicks | Visits to your site from Google's organic results | Month-over-month growth > 5% |
| Impressions | How often your site appeared in results (regardless of clicks) | Typically 10–50× more than clicks |
| CTR | Share of clicks from impressions: (clicks / impressions) × 100% | Position 1: ~28%, Position 3: ~10%, Position 10: 2–3% |
| Average position | Mean ranking across all queries triggering the site | Below 10 — pages need work |
Key filters for deeper Performance analysis:
- Search type: Web / Image / Video / News — the default view shows Web data. If your site has recipes, products or news articles, check Image and News separately — CTR benchmarks differ significantly across types
- Date comparison: Year over Year — compare the current quarter against the same quarter the previous year, not just the previous three months. Seasonal businesses will show misleading drops when compared against their own peak
- Query filter → "Does not contain brand" — exclude branded queries to see true non-branded organic performance. Most sites receive 30–60% of clicks from branded queries, which masks the actual state of non-branded visibility
- Page filter → specific category or URL pattern — analyse individual sections of the site rather than the whole domain in aggregate
The highest-leverage use of Performance is finding growth opportunities. Filter for queries with positions 11–20 and more than 100 impressions per month — these pages are already close to the top 10 but not quite there. Working on them delivers faster results than creating new content from scratch.
We applied this approach for an electronics retailer: found 47 such queries, rewrote title tags and meta descriptions for the corresponding pages. Six weeks later, CTR on those queries rose from 0.8% to 4.2% — an additional 340 organic clicks per month with no position changes and no new content.
Coverage report: indexation and errors
Coverage (in the newer GSC interface — Indexing → Pages) shows what Google has done with each page on your site. Four statuses:
- Error — critical. The page is not indexed due to an error: 404, Server error 5xx, redirect loop. Fix these first
- Valid with warnings — indexed, but contradictory signals exist (e.g. a page blocked in robots.txt but carrying an index tag)
- Valid — all good. Page is in Google's index
- Excluded — intentionally or accidentally excluded. The largest category, with the most varied reasons
How to read Coverage for a large site: don't aim for 100% Valid out of total pages. For an e-commerce site with 10,000+ URLs, having 40–50% of pages in Excluded is normal — provided those are filter pages, pagination and duplicates rather than category or product pages. The key signal is whether Valid page count grows alongside organic traffic. If Valid pages increase but traffic stays flat, the constraint is content quality, not indexation.
The trickiest Excluded reason is "Crawled — currently not indexed". Google visited the page but chose not to index it. This almost always signals low quality: thin content (under 300–400 words), duplication, or no unique value. No technical fix will work here — the page itself needs to improve.
URL Inspection Tool
The URL Inspection Tool (the search bar at the top of GSC, or Ctrl+Enter) lets you check any individual URL. It shows everything Google knows about that page:
- Whether the URL is in the index and when Googlebot last crawled it
- The rendered version of the page the bot sees — including JavaScript-rendered content (More info → Crawl tab)
- Which canonical URL Google selected (may differ from your canonical tag)
- Coverage status: why the page is absent from the index, if it is
- Structured data (schema.org) and Rich Results eligibility
The "Request Indexing" button queues the URL for recrawl. It doesn't guarantee indexation, but it accelerates Google's response after fixes — typically 24–48 hours instead of the usual 1–2 weeks. We use it after every significant content update or technical error correction.
The "Test live URL" tab crawls the page in real time — useful to verify a fix immediately after deployment without waiting for the next scheduled crawl.
Core Web Vitals in Search Console
GSC displays real Core Web Vitals data from the Chrome UX Report — field data from actual Chrome users, not PageSpeed lab tests. Three metrics with threshold bands:
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP — largest contentful paint | < 2.5 s | 2.5–4.0 s | > 4.0 s |
| INP — interaction to next paint | < 200 ms | 200–500 ms | > 500 ms |
| CLS — cumulative layout shift | < 0.1 | 0.1–0.25 | > 0.25 |
GSC automatically clusters pages with similar CWV issues — you don't have to check every URL individually. Click a cluster to get example URLs for detailed analysis in PageSpeed Insights. For a full breakdown of each metric, root causes and fixes, see our dedicated article on Core Web Vitals: LCP, INP and CLS.
Links report
The Links section in GSC contains two separate data blocks — both useful for SEO analysis.
External links — Google's official data on your site's backlinks. Includes the top linking sites, the most-linked pages and the top anchor text strings. These numbers will differ from Ahrefs or Semrush — but they are the backlinks Google has actually indexed and considers for ranking.
Internal links — a count of internal links pointing to each page. If an important commercial page receives 3 internal links while a secondary blog post receives 50, that is a signal to review your internal linking architecture. Link equity flows unevenly, and GSC makes the imbalance visible.
Cross-reference the top pages by External links against the top pages by clicks from Performance. If they diverge significantly, meaningful link equity is flowing to pages that don't generate traffic or conversions.
Rich Results and structured data in GSC
The Search Appearance → Rich Results section shows which types of enhanced search results Google has found on your site: star ratings (Review snippets), breadcrumbs, article cards, local business panels. When structured data (schema.org) is implemented correctly and matches the page content, Google may display these elements in search results — often lifting CTR by 10–25% without any change in position.
Three problem types GSC tracks in Rich Results:
- Error — a required field is missing from the markup. Google won't show a Rich Result even if the rest of the schema is correct
- Warning — a recommended field is absent. Rich Result appears but with a reduced set of elements
- Valid — markup is correct, the page is eligible for enhanced display
Most common Rich Result types for commercial sites and blogs:
| Type | Schema type | Where it appears in search |
|---|---|---|
| Ratings & reviews | Review, AggregateRating | Star ratings below the page title |
| Article / News | Article, NewsArticle | Top Stories carousel, Google Discover |
| Breadcrumbs | BreadcrumbList | Navigation path instead of raw URL |
| Local business | LocalBusiness | Knowledge Panel, Google Maps |
| Product | Product | Price, availability, rating in Shopping results |
To validate a specific page before publishing, use the Rich Results Test (accessible via URL Inspection Tool → "Test live URL" → Rich Results tab). We've seen correctly written schema.org fail purely because of a malformed datePublished field or a missing author.name property — GSC identifies the failure at URL level rather than just flagging "structured data issues exist on the site."
Sitemaps and robots.txt
The Sitemaps section lets you submit an XML sitemap and track how many of its URLs Google has indexed. If you submitted 500 URLs and Google indexed 180, that's not a GSC error — it's a signal that 320 pages fall below Google's quality threshold or duplicate each other.
Requirements for a valid sitemap:
- Contains only canonical, indexable URLs — no noindex pages, no redirect URLs
- Updates automatically when new content is published (most CMS platforms handle this natively)
- Size limit: 50,000 URLs or 50 MB. For large sites — use multiple sitemaps referenced by a sitemapindex.xml file
- URLs in the sitemap exactly match the canonical tags on the corresponding pages
The robots.txt tester (Crawl Stats → Open Report) lets you check any URL against your current robots.txt rules. A common post-migration failure: important pages get accidentally blocked by an overly broad Disallow directive.
Manual actions and site security
The Manual Actions section is the first place to check if traffic drops sharply with no obvious on-site explanation. A Google Search Quality Reviewer manually flags sites for violations of Spam policies: thin content, cloaking, unnatural links, sneaky redirects, user-generated spam and others.
When a manual action exists, GSC specifies exactly which violation was found and whether it applies site-wide or to a partial match. Fix the violation, then submit a Request Review directly from this section. Average review time is 2–4 weeks. Once accepted, the action is lifted and traffic typically begins recovering within weeks.
The Security Issues section surfaces warnings about a compromised site: malware, malicious redirects, phishing pages. Google scans sites continuously and notifies owners before it starts displaying browser warnings to users — giving you a correction window before traffic loss hits.
Monthly SEO audit via GSC: checklist
GSC is not a passive dashboard — it's an active working tool. Our minimum monthly checklist for every client project covers five checks:
- Performance → month-over-month comparison. Broad view of clicks and impressions. A drop of more than 15% with no site changes warrants a deep query- and page-level investigation
- Coverage → new errors. New 404s following a publish or redesign are common. Make sure errors are being fixed faster than they accumulate
- Core Web Vitals → Poor URLs. If the count of Poor pages is growing, it's a developer task — poor CWV correlates with ranking suppression
- Manual Actions → clear or not. A 5-second check that prevents unexpected traffic collapse
- Sitemaps → status and indexed URL count. If indexed URLs are declining without explanation, check for accidentally applied noindex tags on important pages
A sixth check worth adding for larger sites: Crawl Stats (Settings → Crawl Stats). This report shows how many requests Googlebot makes to your site daily and what the average page load time is for the bot. A sudden drop from 500 to 50 crawl requests per day almost always means the site was returning 5xx errors or an overly broad robots.txt rule blocked Googlebot. Crawl Stats pinpoints the date of the drop in minutes — faster than parsing server logs. If the average download time exceeds 2–3 seconds, the bot spends more time per page, which compresses crawl budget and slows indexation of new content.
Based on our work across 200+ projects: 73% of technical SEO problems are identified through GSC before they have a measurable impact on traffic. Coverage errors and Manual Actions in particular both surface well before any visible position drop.
Frequently asked questions
How long does GSC store data?
The Performance report stores 16 months of data. Coverage and Core Web Vitals reflect current state only, with no long-term history. For traffic comparisons beyond 16 months, connect GA4 and build reports in Looker Studio.
Why does GSC show fewer clicks than Google Analytics?
GSC counts only clicks from Google's organic search. GA4 covers all channels — including direct, referral and paid traffic. GA4 also undercounts due to ad blockers and cookie consent restrictions. A 10–20% gap between GSC and GA4 click figures is normal.
Does GSC show every query a site ranks for?
No. Queries below a minimum impressions or click threshold are hidden to protect user privacy — Google doesn't publish the exact threshold. For complete keyword data, use Ahrefs or Semrush alongside GSC rather than relying on either alone.
Is GSC necessary if Ahrefs is already set up?
Yes, unconditionally. Ahrefs generates its own metrics from its own crawler. GSC provides ground-truth data directly from Google: real clicks, impressions, positions and technical site status. They complement each other — neither replaces the other.
Need help setting up GSC and running an SEO audit?
The SEO-Factory team will connect Google Search Console, configure access roles, analyse your coverage and build a technical fix plan based on real Google data.


