Search Console is the only place where Google reports directly on your website — which queries show your pages, why URLs drop from the index, and what its crawler experienced. Learning how to use Google Search Console for SEO converts that raw feedback into a working loop: publish, inspect, diagnose, fix, resubmit.
Quick Answer: Verify your property, submit a sitemap, then run a weekly loop through four reports — Performance for query data, URL Inspection for individual page verdicts, Sitemaps to confirm discovery, and Page indexing to triage exclusions.
What follows is the complete setup-to-triage walkthrough, ordered so each step builds on the last. Budget one focused hour for setup; the maintenance rhythm afterwards costs minutes per week.
Step 1: Create and Verify Your Property
- Open Search Console and choose Domain property when you control DNS — it covers every subdomain and both HTTP and HTTPS in one property. Pick URL prefix only if DNS access is impossible; HTML-file upload or the meta-tag method then work fine.
- For Domain verification, add the supplied TXT record at your registrar, then press verify. Propagation usually completes within minutes, occasionally longer.
- Once verified, add all relevant versions and let the domain property consolidate them automatically.
Data begins accumulating immediately, though Performance figures need a few days before trends mean anything. Verification grants nothing to Google — it proves ownership to you.
Step 2: Submit Your Sitemap
Navigate to Sitemaps, enter your XML sitemap's location (typically /sitemap.xml) and submit. The report then tracks discovered versus processed URLs, flagging parse errors or unreachable files. A sitemap does not force indexing — it assists discovery, particularly valuable for new pages on sites crawled infrequently. Regenerate it whenever content structure changes materially.
Step 3: Read the Performance Report Properly
This is where SEO decisions live. Clicks, impressions, average position and click-through rate are sliceable by query, page, country and device across any date range.
Find Rising Queries Early
Set the view to compare two periods and sort queries by impression growth. Rising impressions mark topics Google is testing you against — strengthening those pages while attention lasts compounds quickly.
Fix CTR Leaks Before Rankings
Queries ranking positions one through ten with weak click-through rates signal unappealing snippets rather than visibility problems. Rewrite those titles and descriptions first; CTR gains require no new authority whatsoever.
| Report | Question It Answers | Action It Triggers |
|---|---|---|
| Performance | Which queries and pages earn visibility? | Rewrite snippets; reinforce rising queries |
| URL Inspection | What is this specific URL's status right now? | Fix blocks; request indexing after changes |
| Sitemaps | Does Google discover my new URLs? | Resubmit after structural changes |
| Page indexing | Why aren't all my URLs indexed? | Triage exclusion reasons by traffic impact |
Step 4: Inspect Any URL On Demand
Paste any address into the top search bar for its indexed state: whether it sits in Google's index, under which canonical, with which detected enhancements. Switching to Live Test fetches the page as Google sees it now — invaluable immediately after publishing or fixing something. Following fixes, hit Request indexing to queue prioritised recrawling; treat it as a nudge for important pages, not a bulk command, since quotas apply.
Step 5: Triage the Page Indexing Report
This report sorts every known URL into indexed versus excluded, with reasons grouped by cause. Work it in this order:
- Alternate page with proper canonical tag — almost always correct behaviour; ignore.
- Crawled – currently not indexed — quality judgement by Google; improve depth and internal links toward these pages.
- Discovered – currently not indexed — crawl budget or quality hesitation; strengthen internal linking and request indexing individually.
- Noindex or blocked directives — deliberate or accidental? Remove accidental ones immediately.
- Not found (404) or redirect errors — restore or update internal links pointing at them.
Turning Setup Into a Habit
Enable email alerts in settings so critical issues reach you unprompted. Then anchor a fifteen-minute weekly review: Performance comparison, Pages anomalies, any pending sitemap processing. Search Console rewards pattern recognition, and patterns only emerge when inspection happens on schedule rather than during crises.
Key Takeaways
- Choose a Domain property wherever DNS control exists — one verification covers everything.
- Sitemaps aid discovery but never guarantee indexing; quality still decides.
- Performance comparisons between periods reveal rising queries and snippet opportunities first.
- URL Inspection arbitrates single-page disputes; Live Test shows current reality.
- Triage Page indexing exclusions by traffic impact, starting with directive accidents.