Google Search Console · Features, Reports & Practical Use

Google Search Console is a free web service from Google that allows website owners to monitor how Google crawls, indexes, and ranks their website in Google Search. It is distinct from Google Analytics: GA4 measures what users do on the website after they arrive; GSC measures what happens in Google before users arrive — what Google shows in search results, what queries trigger the site's pages, and whether Google can successfully crawl and index the site.

GSC provides data that is not available anywhere else: the actual queries from Google Search that generated impressions and clicks for specific pages; the specific pages that are or are not indexed; the specific URLs that have crawl errors; and the Core Web Vitals performance as measured by real Chrome users (the CrUX dataset) rather than lab-based estimates. No third-party SEO tool can provide this data — it comes directly from Google's systems.

Create a GSC account at search.google.com/search-console. Add a property — either Domain (covers all variants: http, https, www, non-www) or URL Prefix (covers a specific URL prefix). Domain properties are recommended as they provide the most comprehensive data without duplication across https/http variants.

Verification methods: DNS TXT record (recommended for Domain properties — add a TXT record to the domain's DNS configuration); HTML file upload (for URL Prefix properties — upload a Google-provided HTML file to the website root); Google Tag (add the GTM-based verification code to the site); or verified Google Analytics property (if the site already has GA4 configured with the same Google account). After verifying ownership, data typically begins appearing within 48–72 hours, with historical data available for up to 16 months.

Adding users: Settings → Users and Permissions → Add User. Roles: Owner (full access including permission management), Full User (all reports, submit URLs, no permission management), Restricted User (read-only access to most reports).

The Performance report (Search Results tab) is the primary GSC report for SEO analysis — it shows the search queries generating clicks and impressions, the pages receiving traffic, and aggregate metrics across the 16-month data window.

Key metrics

Key filters and dimensions

Switch between Query, Page, Country, Device, Search Appearance, and Date dimensions to analyse performance from different angles. Most actionable workflows: filter by a specific page to see all queries it ranks for; filter by a specific query to see all pages ranking for it; compare Date ranges (current 3 months vs previous year) to identify seasonal patterns and year-over-year growth.

The Index Coverage report shows which pages on the site are indexed by Google and which are not — and why. Pages are categorised as: Error (failed to index), Valid with Warning (indexed but with a potential issue), Valid (successfully indexed), Excluded (not indexed for a legitimate reason — noindex tag, canonical to another page, crawl blocked by robots.txt).

Common indexing errors

• Server error (5xx). Google attempted to crawl the page but received a server error response. Usually indicates a server configuration problem or a page that experiences intermittent errors under crawl load.
• Redirect error. The page's redirect chain is broken, too long (more than 5 hops), or contains a redirect loop. Affects pages being redirected to a new URL.
• Submitted URL blocked by robots.txt. A page has been submitted in the sitemap but blocked from crawling by the robots.txt file — a configuration conflict.
• Submitted URL not found (404). A page in the sitemap returns a 404 — it no longer exists or has moved without a redirect. Update the sitemap or add a redirect.

The URL Inspection tool (search bar at the top of GSC) shows Google's detailed assessment of a specific URL: whether it is indexed, the last crawl date, the canonical URL Google recognises, the indexing status, any mobile usability issues, and the structured data detected on the page.

The "Test Live URL" option re-crawls the URL in real time and shows how Google renders it currently — useful after making changes to a page to verify they are reflected correctly before requesting indexing. "Request Indexing" asks Google to re-crawl and reindex the URL promptly — used after publishing new content or making significant changes to existing content. Note that Request Indexing is a suggestion to Googlebot, not a guarantee — Google ultimately crawls on its own schedule.

An XML sitemap is a file listing the URLs on a website that should be crawled and indexed. It provides a crawl roadmap for Googlebot — ensuring Google is aware of all important pages, particularly new or recently updated pages that might not yet have inbound links for Googlebot to discover. Submit a sitemap: Sitemaps report → Enter the sitemap URL (typically /sitemap.xml) → Submit.

Most CMS platforms generate sitemaps automatically: WordPress with Yoast SEO or RankMath plugins, Shopify, Squarespace, and Wix all produce XML sitemaps. After submitting, the Sitemaps report shows the number of URLs submitted and the number discovered/indexed — a significant gap between submitted and indexed indicates either indexing problems or the sitemap includes pages Google does not wish to index (duplicate content, thin pages, noindexed pages).

The Core Web Vitals report shows LCP (Largest Contentful Paint), INP (Interaction to Next Paint), and CLS (Cumulative Layout Shift) performance for pages on the site — using real user data from Chrome users (the Chrome User Experience Report, CrUX). Pages are categorised as Good, Needs Improvement, or Poor for each metric.

GSC's Core Web Vitals data is more valuable than PageSpeed Insights alone because it aggregates real user experiences across all Chrome users visiting the site — not just a single lab test. A page might perform well in a PageSpeed Insights test (which simulates a specific device and connection) while performing poorly for actual users with different devices and connections. The GSC report surfaces pages with real-world performance problems affecting the user experience for actual visitors.

The Mobile Usability report identifies pages with mobile rendering problems that affect usability — specifically the issues that can trigger Google's mobile-friendliness signals. Common issues: text too small to read (text under 12px on mobile); clickable elements too close together (touch targets within 48px of each other); content wider than screen (horizontal overflow causing horizontal scrolling). Each issue type shows the affected URLs with examples.

With Google's mobile-first indexing, mobile usability is not just a user experience concern — it affects how Google indexes and ranks pages. Pages with significant mobile usability problems may rank less well in Google Search and provide a poorer experience for the majority of users who visit on mobile devices.

The Links report (left navigation → Links) shows external links (backlinks from other websites), internal links (links between pages on the same site), and top linked pages. This data comes directly from Google's link graph — showing which links Google has actually discovered and processed, rather than the estimated data from third-party tools.

Key uses: verify that high-priority pages (homepage, key landing pages, product pages) have the most internal links pointing to them; identify any unexpected external linking domains (particularly for monitoring for spammy link activity); check the anchor text distribution of external links to verify it appears natural rather than over-optimised.

1. Performance report: Month-over-month comparison. Compare current month vs same month last year (year-over-year seasonality removed). Identify: queries with significant impression growth (new ranking opportunities); pages with declining clicks despite stable impressions (CTR problem — improve title/meta description); pages with improving rankings approaching page 1 (prime for additional internal linking and optimisation).
2. Index Coverage: Review new errors. Filter by Error status and sort by date to identify new indexing errors. Prioritise fixing 4xx (not found) and 5xx (server error) issues for important pages.
3. Core Web Vitals: Review Poor URLs. Identify pages in the Poor category for LCP or INP. Prioritise high-traffic pages with Core Web Vitals problems.
4. Mobile Usability: Review new issues. Check for newly reported mobile usability problems, particularly after template or CMS changes.