GSC Excluded Pages: What They Mean and What to Fix

The Excluded Tab Is Not a Junk Drawer

Most SEOs open Google Search Console, check the Error count in the Index Coverage report, fix the obvious problems, and stop there. The Excluded tab sits beneath it with hundreds or thousands of URLs and gets ignored.

That's a mistake. The Excluded tab is where Google quietly tells you it decided not to index pages. Some of those decisions are correct. Others are costing you rankings you should have.

The challenge is that GSC groups excluded pages into more than a dozen distinct reasons, and the right response varies completely depending on which reason you're looking at. Treating all exclusions the same is how sites end up with important pages missing from the index for months.

How the Excluded Tab Actually Works

Google's Index Coverage report (now called the Indexing report in the refreshed GSC interface) divides URLs into four states: Indexed, Not indexed, Error, and Warning. The Excluded category sits within Not indexed.

Excluded URLs are pages Google either crawled and chose not to index, or pages it discovered but never crawled. The exclusion reason tells you which scenario applies and why Google made the call it did.

The URL Inspection tool is your companion here. When you see an exclusion reason that doesn't make sense for a specific page, inspect that URL directly to see Google's most recent crawl data, the canonical Google selected, and whether the page was indexed in a previous crawl.

For a deeper look at how to use that tool, the URL Inspection Tool guide covers the full workflow.

The Exclusion Reasons, One by One

Crawled - Currently Not Indexed

This is the most important exclusion reason to audit. Google crawled the page and decided not to index it. No canonical conflict. No redirect. Google simply looked at the content and passed.

Common causes include thin content, pages with very little unique text, near-duplicate pages across a large site, or pages with very low engagement signals historically. For large e-commerce sites, faceted navigation pages often land here.

The response depends on what those pages contain. If they're legitimate content that should rank, the fix is improving quality. If they're legitimately thin utility pages, noindexing them intentionally cleans up your coverage data and protects crawl budget.

Discovered - Currently Not Indexed

Google found the URL (through a link or sitemap) but hasn't crawled it yet. This is different from a crawl decision. Google simply hasn't gotten there.

A large spike in this category usually means one of three things: you recently added many new pages, your crawl budget is stretched, or your internal linking is weak and Googlebot isn't being guided to those pages efficiently.

Don't panic if you see this for recently published content. Give it a few weeks. If pages stay in this state for months, investigate your internal link structure and sitemap health. The sitemaps guide covers how to verify Google is processing your sitemap correctly.

Duplicate Without User-Selected Canonical

Google detected duplicate or near-duplicate content across multiple URLs and picked one as the canonical - but it wasn't the one you expected, and you hadn't specified a canonical yourself.

This exclusion is a signal that you have a canonicalization problem. Google is making the decision for you, and it may not be making the right one. The fix is adding explicit canonical tags pointing to the URL you want indexed.

Check whether the URLs Google is selecting as canonical actually carry your best content and earn the most links. If not, you need to intervene.

Duplicate, Google Chose Different Canonical Than User

This is more urgent. You specified a canonical, and Google ignored it and chose a different URL as the canonical anyway.

Google doesn't treat canonical tags as directives - they're hints. When Google overrides your canonical, it usually means there's a conflicting signal: internal links pointing to the wrong version, the HTTP version being linked to when you want HTTPS indexed, or the page content being genuinely identical to a stronger page.

Audit the winning canonical URL. If it's a variant you don't want indexed (for example, a URL with a session parameter or UTM code), fix the source of those URLs. Blocking parameter-based URLs in your sitemap and ensuring internal links point to canonical versions usually resolves this.

Alternate Page With Proper Canonical Tag

This one looks alarming but usually isn't. It means the page exists, Google crawled it, and it has a canonical tag pointing to another URL that Google has indexed. Google is respecting your canonical instruction.

Common examples: paginated pages canonicalizing to the first page, print versions of pages, or language variants handled with canonical tags rather than hreflang. Spot-check a sample to confirm Google is selecting the canonical you intended. If it is, this exclusion category is working correctly.

Soft 404

The page returns a 200 HTTP status code but the content signals a not-found or empty state. Google's systems recognized the page as functionally empty, even though your server reported success.

Soft 404s are common on e-commerce sites when products go out of stock and the page renders a near-empty shell, or on sites that show dynamic "no results" states for filtered pages. They also appear on paginated pages where the page number requested doesn't exist but the server returns a 200 with the first page of results.

The fix depends on the root cause. Out-of-stock products should either redirect to a category page, show robust related products, or return a genuine 404. Pages with thin content that load as 200 need either more content or a proper noindex tag.

Blocked by robots.txt

Googlebot attempted to crawl the page but your robots.txt file told it not to. Two very different situations look the same here: intentional blocking (admin pages, staging environments) and accidental blocking.

The fix is to open your robots.txt file and verify every blocked path is intentionally blocked. A common accident: blocking a CSS or JavaScript folder that controls your site's rendering, which breaks how Google sees your pages even if the HTML pages themselves aren't blocked.

Note that if a URL appears here, it means Google knows the URL exists - it found it through a link or sitemap - but couldn't crawl the content. If you don't want Google knowing a page exists at all, robots.txt isn't enough. You need to remove the internal links or sitemap references pointing to it.

Excluded by noindex Tag

Google found a noindex directive on the page and respected it. This is expected behavior when you've intentionally tagged pages as noindex.

The danger zone is when noindex tags appear unintentionally. CMS plugins, staging deployments pushed to production, or template-level changes can add noindex to pages you want indexed. Spot-check 10-20 URLs from this group to verify the tag is where you intended it.

One particularly nasty scenario: a developer deploys a feature branch that has a sitewide noindex added to the head template for staging purposes. The site drops out of the index within weeks. It's a well-documented accident and easy to miss if nobody is monitoring the Excluded tab.

Page With Redirect

Google followed the URL and it redirected somewhere else. The redirected-to URL is what gets indexed (or not). This exclusion is normal and expected for properly redirected old URLs.

Watch for redirect chains here. If URL A redirects to URL B which redirects to URL C, Google may still process the chain, but it wastes crawl budget and can dilute link equity. Keep redirects to a single hop where possible.

Not Found (404)

The URL returns a 404 status. Google is listing it because it discovered the URL - typically through an external link or internal link - but the page doesn't exist.

404s for genuinely dead pages with no external links pointing to them are not a problem. Google will eventually stop crawling them. The pages worth acting on are 404s that have external backlinks pointing to them - those represent lost link equity you can recover by redirecting to a relevant live page.

The GSC Links report shows you which external sites link to your pages, so you can cross-reference 404s against your backlink data to identify which dead URLs are worth salvaging.

How to Build an Exclusion Audit Workflow

Rather than auditing the Excluded tab reactively, build a regular review process. The goal isn't to eliminate all exclusions - many are correct. The goal is to catch the ones that aren't.

Step 1: Triage by Category Size

Start by noting the count in each exclusion category. Categories with zero or near-zero counts can be skipped. Categories with unexpectedly large counts deserve investigation - especially if a category has grown since your last check.

Date comparison is your friend here. GSC's Performance tab has date range comparison tools, and the coverage data changes over time. If "Crawled - Currently Not Indexed" jumped from 200 to 800 in a month, that's a signal worth chasing.

Step 2: Sample and Inspect

For each significant exclusion category, export the URL list and take a random sample of 15-20 URLs. Inspect each one using the URL Inspection tool. Look for the pattern that explains the exclusion.

If all sampled URLs from a category are obviously correct (noindexed admin pages, paginated pages with explicit canonicals), the category is healthy. If you find surprising results in the sample, dig deeper into the full URL list.

Step 3: Fix, Accept, or Monitor

Each excluded URL ultimately falls into one of three responses. Fix it if the exclusion is unintended and the page should be indexed. Accept it if the exclusion is correct and working as intended. Monitor it if you're not sure yet or if the volume is growing.

For pages you fix, submit them for indexing using the URL Inspection tool's "Request Indexing" button. Don't expect immediate results - Google revisits pages on its own schedule - but the request can accelerate recrawling for important pages.

When Excluded Page Counts Are Too High

Some sites have exclusion counts that dwarf their indexed page count. A site with 5,000 indexed pages but 40,000 excluded pages has a structural problem worth diagnosing.

Common culprits include faceted navigation generating URL combinations, session IDs in URLs, or CMS pagination creating variants of the same content. The crawl budget guide covers how to reduce URL bloat across these scenarios.

Getting your indexed-to-excluded ratio under control matters not just for tidiness in GSC but for how Google allocates crawl resources to your site. A server that's constantly serving thin or duplicate pages to Googlebot gets less frequent crawling of the pages that actually matter.

Tracking Excluded Pages Over Time

GSC's interface doesn't make historical exclusion tracking easy. The data updates over time but doesn't give you a chart of how exclusion counts moved by category over months.

The workaround is documenting your exclusion counts in a spreadsheet during each audit. Record the date, the count per category, and any actions taken. This creates a manual changelog that lets you spot whether your fixes are working or whether a category is silently growing.

For sites that want to systematically track indexing health alongside traffic and ranking data, the site audit feature in MeasureBoard surfaces indexing problems alongside their traffic impact, so you can prioritize fixes by actual SEO value rather than raw URL counts.

The Index Coverage guide covers the error states in that same report - the counterpart to this exclusion deep dive - if you want to close the loop on both reports simultaneously.

The Bottom Line

The Excluded tab in GSC is not a list of things Google got wrong. Most exclusions are correct. But inside every large exclusion list, there are usually a handful of categories where Google made a decision based on a fixable technical issue or weak content signal.

The SEOs who audit this regularly find problems early, before they compound into traffic drops. The ones who don't are often left wondering why important pages aren't ranking when the answer has been sitting in the Excluded tab for months.