Google Search Console SEO Audit: A Step-by-Step Walkthrough

Your site isn’t ranking the way you’d expect. Before you pay for a crawler subscription or hire someone to investigate, open the tool you already have: Google Search Console. It’s free, already collecting your site’s data, and can carry an entire SEO audit on its own.

This guide walks through every report worth checking, in order, and tells you exactly what to look for and what to do when you find it. By the end, you’ll have a prioritized fix list built entirely from Search Console data.

The Direct Answer: What a GSC-Only Audit Covers

A Google Search Console SEO audit means working through five report groups in sequence:

1. Performance — what’s actually driving clicks and impressions, and where you’re leaking potential traffic
2. Indexing (Coverage) — what Google has and hasn’t indexed, and why
3. Sitemaps — whether Google can discover your URLs in the first place
4. Page Experience / Core Web Vitals — whether your pages are fast and stable enough to compete
5. Enhancements — structured data and mobile usability issues that affect how you appear in results

Each report answers a different question. Performance tells you what’s working. Coverage tells you what’s missing. Sitemaps and robots.txt tell you what Google can even see. Page Experience tells you whether technical quality is holding you back. Run through all five, and you’ll have a full picture — visibility, indexing, technical health — without touching a paid crawler.

Step 1: Start With the Performance Report

Open Search Console > Performance > Search results. This report shows how real searchers interact with your site.

The four core metrics:

• Clicks — how many times someone clicked through to your site from a search result
• Impressions — how many times your site appeared in search results
• Average CTR — clicks divided by impressions
• Average position — your average ranking position across all queries and pages

What to look for

Start with the Queries tab. Sort by impressions, descending. This tells you what Google already associates your site with — even if you’re not ranking well for those terms yet. Any query with high impressions but low clicks is a page that’s showing up but not winning the click. That’s usually a title tag or meta description problem.

Next, sort by average position. Queries sitting between roughly position 5 and 15 are your best short-term opportunity — you’re already relevant enough to appear, but not high enough to capture serious traffic.

Then switch to the Pages tab and do the same sort. A page with strong impressions and weak clicks is worth an on-page audit.

Finally, compare the last 3 months against the prior period. A steady decline across many pages usually points to a site-wide issue — a Core Web Vitals problem, a bad redirect, or content decay. A decline isolated to a handful of pages is usually content-specific.

What to fix from this report

• Rewrite titles and meta descriptions on high-impression, low-CTR pages
• Flag pages ranking 5–15 for on-page improvement (headings, depth, internal links)
• Investigate any month-over-month traffic decline in later steps

Step 2: Move to Indexing (Coverage)

Open Search Console > Indexing > Pages (in older interface versions this was labeled Index Coverage). It answers a blunt question: does Google actually have your pages in its index?

If a page isn’t indexed, nothing else matters. It can’t rank, appear in Performance data, or earn a click.

What to look for

The report splits URLs into indexed and not-indexed buckets with reasons. Common reasons:

• Crawled — currently not indexed: Google visited the page but chose not to index it, usually a quality or duplication signal
• Discovered — currently not indexed: Google knows the URL exists but hasn’t crawled it yet, often a crawl budget or priority issue
• Excluded by ‘noindex’ tag: intentional or accidental — check which
• Duplicate without user-selected canonical: Google found near-identical content and picked (or failed to pick) a canonical version
• Page with redirect: the URL redirects elsewhere, so it isn’t indexed under its own address
• Not found (404): the URL no longer resolves

Click into each “not indexed” category and review the URL list. Ask three questions for every page that shouldn’t be excluded:

1. Is there a stray noindex tag left over from staging or a CMS default?
2. Is the content thin, duplicated, or nearly identical to another page?
3. Is the page orphaned — not linked from anywhere else on the site?

What to fix from this report

• Remove accidental noindex tags on pages meant to rank
• Merge or canonicalize duplicate/near-duplicate pages
• Add internal links to orphaned pages
• Rewrite or expand thin pages stuck in “Crawled — currently not indexed”
• Confirm 404s are intentional; redirect anything that used to carry traffic or links

Step 3: Check Sitemaps

Open Search Console > Sitemaps. Your sitemap is how Google discovers URLs efficiently instead of relying purely on internal links and external mentions.

What to look for

• Is a sitemap submitted at all? If not, submit your sitemap.xml URL — it’s a five-minute fix with an outsized payoff for discovery speed.
• What’s the submitted-vs-indexed count? A large gap is a signal worth chasing down in the Coverage report from Step 2.
• Are there errors listed against the sitemap — fetch failures, invalid URLs, or format issues?
• Does the sitemap reflect your current site? A sitemap listing pages you deleted months ago, or missing pages you published recently, is actively misleading Google.

Step 4: Review Robots.txt and Crawlability

Sitemaps tell Google where to look. Robots.txt tells Google where not to look. Both need to be correct.

What to look for

Check your robots.txt file directly (at yourdomain.com/robots.txt) and confirm:

• No accidental Disallow rule is blocking a section you want indexed — this happens constantly after a site migration or a developer forgetting to remove a staging rule
• Your sitemap is referenced in robots.txt
• Low-value sections — internal search results, admin routes, filtered/faceted URLs creating near-duplicates — are appropriately disallowed so crawl attention isn’t wasted

Then use the URL Inspection tool (the search bar at the top of Search Console) on a handful of important pages. For each one, check:

• Crawl status: has Google crawled this URL, and when?
• Indexing status: is it indexed, and under which canonical URL?
• Coverage details: does Google’s chosen canonical match your intended URL?

This is also where you catch crawlability issues — pages that return a soft 404, pages blocked by a login wall, or pages where the canonical tag points somewhere unexpected.

What to fix from this report

• Remove any Disallow rule blocking content you want ranked
• Add or correct the sitemap reference in robots.txt
• Disallow low-value, duplicate-generating URL patterns (search, filters, session IDs)
• Fix canonical mismatches surfaced in URL Inspection
• Re-request indexing for any important page you’ve just fixed using the “Request Indexing” option in URL Inspection

Step 5: Page Experience and Core Web Vitals

Open Search Console > Page Experience. This report groups your URLs by real-user performance data across three vitals:

• Largest Contentful Paint (LCP) — how long the main content takes to load
• Interaction to Next Paint (INP) — how responsive the page feels when a user interacts with it
• Cumulative Layout Shift (CLS) — how much the page visually jumps around while loading

What to look for

Google groups URLs into “Good,” “Needs improvement,” and “Poor” buckets. Sort by which template or page type dominates the “Poor” bucket — vitals problems are almost always template-wide, not page-specific.

Cross-reference this against Step 1. If a page group with a Core Web Vitals problem also shows declining clicks or position, you’ve found a likely cause.

What to fix from this report

• Identify the shared template behind any “Poor” cluster rather than fixing pages one at a time
• Compress or lazy-load large images causing LCP issues
• Reduce or defer third-party scripts causing slow interaction response
• Set explicit width/height on images and ads to stop layout shift

Step 6: Enhancements — Structured Data and Mobile Usability

Open Search Console > Enhancements. This section reports on structured data types you’ve implemented (reviews, products, FAQs, breadcrumbs, and similar) and on mobile usability.

What to look for

• Any structured data type showing errors or warnings — these often mean rich results (star ratings, FAQ dropdowns, breadcrumb trails) aren’t displaying even though the markup exists
• Mobile usability issues — text too small to read, clickable elements too close together, content wider than the screen

These are lower-severity than indexing or crawlability problems, but they directly affect click-through rate.

What to fix from this report

• Correct structured data errors flagged for each markup type
• Validate fixes with the Rich Results Test before assuming the issue is resolved
• Resize touch targets and text flagged under mobile usability

Scope and Limits of a GSC-Only Audit

Search Console is built entirely from Google’s own crawl and index data plus real user metrics. It will tell you what Google has seen, indexed, and measured about your site. It will not:

• Crawl your site the way a dedicated crawler does, surfacing every broken link, redirect chain, or duplicate title tag across the whole site in one pass
• Show competitor comparisons or backlink profiles
• Flag content-level issues like keyword cannibalization unless you manually cross-reference the Queries and Pages tabs

For most small-to-mid-size sites, that’s not a real limitation — the five reports above surface the issues that actually move rankings: unindexed pages, broken discovery paths, slow templates, and weak titles. A paid crawler adds breadth and automation for larger sites with thousands of URLs, but it doesn’t replace the judgment calls above.

The Prioritized Fix List

Once you’ve worked through all six steps, consolidate everything into one ordered list. Fix in this order:

Tier 1 — Indexing blockers (fix first, they block everything else)

• Remove accidental noindex tags
• Fix robots.txt rules blocking wanted content
• Submit or correct your sitemap
• Resolve canonical mismatches

Tier 2 — Crawl and discovery gaps

• Add internal links to orphaned pages
• Merge or canonicalize duplicate content
• Rewrite thin pages stuck in “Crawled — currently not indexed”

Tier 3 — Technical quality

• Fix template-wide Core Web Vitals issues (LCP, INP, CLS)
• Correct structured data errors
• Resolve mobile usability flags

Tier 4 — On-page and CTR optimization

• Rewrite titles and meta descriptions on high-impression, low-CTR pages
• Improve content depth on pages ranking positions 5–15
• Investigate and address any site-wide traffic decline pattern

Run this same six-step process quarterly, since indexing status, Core Web Vitals scores, and query rankings all shift as Google recrawls your site and as you publish new content.

FAQ

Do I need a paid crawler tool to do an SEO audit? No. Search Console alone covers indexing status, crawlability, sitemap health, Core Web Vitals, and query-level performance. A paid crawler adds scale and automation for very large sites, but it doesn’t cover anything fundamentally different.

How often should I repeat this audit? Quarterly is reasonable for most sites, with a lighter check on the Performance and Coverage reports monthly if you’re publishing new content regularly.

What’s the single highest-priority fix if I only have time for one? Indexing issues, always. A page that isn’t indexed can’t rank or earn clicks — fixing indexing gaps unblocks the value of every other improvement on the list.

Why does a page show high impressions but almost no clicks? Usually a title tag or meta description that isn’t compelling relative to competing results, though it can also mean the ranking position is too low for most searchers to scroll to.

What does “Discovered — currently not indexed” actually mean? Google knows the URL exists — usually from your sitemap or an internal link — but hasn’t crawled and indexed it yet. It often resolves on its own once the page gains internal links or the sitemap is refreshed, but persistent cases are worth investigating for quality or crawl-priority issues.