Google Search Console: overview and checklist

Overview

Google Search Console (GSC) is a free Google service for site owners and technical SEOs that reports how Google discovers, crawls and indexes your site and how your pages appear in Search. Since July 2024 Google crawls sites for Search with Googlebot Smartphone by default; use GSC to confirm what Google sees and to diagnose indexation and visibility issues.

Important context: crawling, indexing and ranking are separate stages. GSC helps you identify crawl and index problems and surface performance signals (clicks, impressions, queries) in the Performance report. Fixing indexation problems makes pages eligible to rank, but ranking position is decided by Google’s multi-signal algorithms.

Step-by-step

1. Choose a property type — domain or URL-prefix. Domain properties cover all protocols and subdomains via DNS verification; URL-prefix properties are protocol- and path-specific and accept several verification methods.

2. Verify ownership. Common verification methods: DNS TXT record, HTML file upload, HTML meta tag, Google Tag Manager or GA4 tag. DNS verification is the most comprehensive for domain properties; allow DNS propagation time before re-checking.

3. Submit a sitemap. In the Sitemaps report, submit a canonical sitemap (XML or index). A sitemap is a hint—useful for discovery—especially for large sites or new content, but it does not guarantee indexing.

4. Use URL Inspection for single-URL checks. The tool shows the last crawl, index status, detected canonical, and whether rich results are eligible. For pages you own you can request indexing; this does not guarantee immediate indexing or ranking.

5. Monitor Performance and Coverage. Performance surfaces clicks, impressions, average position and queries. Coverage lists indexing errors, excluded pages, server errors and reasons why Google did or did not index a URL.

6. Add users and link other products. Grant role-based access for teammates and connect Search Console to tools such as Google Analytics (GA4) and Google Tag Manager to combine signals.

Google Search Console checks: technical checklist

- **Property verification** — where to verify: GSC > Settings > Ownership verification — passes when GSC lists an active verification method for the property.
- **Sitemap submission** — where to verify: GSC > Sitemaps — passes when your sitemap is accepted and URL counts are updated (watch for processing errors).
- **Index coverage** — where to verify: GSC > Coverage — passes when affected URLs are in the "Valid" or expected "Excluded" state with documented reasons.
- **URL live test and index request** — where to verify: GSC > URL Inspection — passes when URL Inspection reports "URL is on Google" or documents why it isn’t.
- **Structured data / rich results** — where to verify: GSC > Enhancements + Rich Results Test — passes when the Testing tools report no blocking errors and expected items are detected.
- **Mobile rendering parity** — where to verify: GSC > URL Inspection + manual device checks — passes when the mobile-rendered HTML contains the same critical content and links as desktop (parity, not pixel-identical).
- **Robots and HTTP status** — where to verify: curl, Network tab, GSC Coverage — passes when pages return 200/301 as intended and robots directives do not block Googlebot.

How to verify: tools & commands

Use the URL Inspection tool for authoritative per-URL crawl and index details on sites you own. For external verification or low-level checks use these methods:

• Check HTTP headers only: curl -I https://example.com/path (returns response headers; no body).
• Follow redirects and show final headers: curl -I -L https://example.com/path.
• Inspect HTML served to a specific user-agent: curl -A "Googlebot/2.1 (+http://www.google.com/bot.html)" https://example.com/path (use no -I to retrieve the full HTML).
• Rendered DOM and JavaScript effects: open Chrome DevTools (Network + Elements) and emulate Mobile to see what a browser actually renders.
• Structured data: run pages through Rich Results Test and the Schema Markup Validator to find implementation errors.
• Server logs: review requests from Googlebot user-agents to confirm crawl frequency and any 4xx/5xx responses.

Common problems

Verification failures: DNS records not propagated, incorrect HTML file placement, or verification removed by CMS migrations. Resolution: re-check DNS TTLs, re-upload verification file or re-add the correct meta tag and confirm via GSC Settings.

Index coverage errors: soft 404s, canonical pointing elsewhere, or pages blocked by robots.txt. Use Coverage details and URL Inspection to see the specific reason and to test fixes; requesting indexing is useful for re-evaluation but not a guarantee of indexing.

Mobile content parity problems: if critical content or structured data appears only on desktop, pages may be crawled and indexed with reduced content. Since Google uses the mobile version as the primary basis for indexing, ensure parity of important content and metadata.

Manual actions and algorithmic adjustments: GSC shows Manual Actions for your property when Google issues reviewer actions. Most visibility changes are algorithmic and not labeled; distinguish between the two when troubleshooting.

Note on public index checks: the site: operator is a useful external signal that Google knows about a page, but it’s not definitive. For authoritative index status use URL Inspection for pages you own.

Read the Technical SEO Guide

Frequently asked questions