Search Console Indexing Issues Explained

Open the Page indexing report in Search Console and you'll find every URL on your site sorted into one status: Submitted and indexed, Crawled - currently not indexed, Page with redirect, and a dozen others. Some of these need action. Most don't. Here's what each status covered below actually means, which ones are worth investigating, and real examples pulled from our own site's URL Inspection results while writing this, on 21 September 2026.

Why the status matters more than the headline number

The report's top-line "not indexed" count lumps together things that need very different responses. A page stuck behind a genuine crawl error is a different problem from a page Google deliberately excluded because it's a near-duplicate of another URL, which is different again from a redirect doing exactly what it's supposed to do. Treating all three the same way, by resubmitting the sitemap and waiting, only fixes the first one, and does nothing for the other two.

Discovered - currently not indexed

Google found the URL, through a sitemap, an internal link, or an external link, but has not fetched it yet. It's a queue position, not a verdict. We've written a full explainer on this one, with real examples from our own site, in Discovered - currently not indexed: what it means.

Crawled - currently not indexed

This is the one worth paying closer attention to, because it means Google did fetch the page and chose not to index it anyway. That's usually a quality, duplication or relevance call on Google's part, not a scheduling delay you can wait out. We've written a full explainer on this one too, in Crawled - currently not indexed: what it means.

Real example, checked this session: /blog/redirect-chains-and-loops currently carries this status in our own Search Console, last crawled 4 July 2026. The page is live, carries no noindex tag, and is linked from /blog/technical-seo-guide and elsewhere on the site. Nothing about it is technically broken. It's a genuine editorial judgement call by Google, on a domain that's still earning trust, rather than a fault we can point at and repair.

The difference from "Discovered" matters for what you do next:

• If a page has been Discovered for weeks, the lever is usually internal links and overall site authority.
• If a page has been Crawled but excluded, Google has already looked and decided against it. Reworking or consolidating thin content, strengthening internal links to the page, and giving it time as the site's overall trust builds are the realistic options. There is no resubmit button that overrides a quality judgement Google has already made.

The two duplicate-canonical statuses

These sound similar and get confused constantly, but they describe different situations.

"Duplicate without user-selected canonical" means Google found this page to be a near-duplicate of another URL and didn't see it express a real preference either way, so Google picked a canonical on its own. The textbook cause is a missing canonical tag entirely. But a self-referencing tag doesn't reliably clear this either: it only confirms a page's own URL, which tells Google nothing about a duplicate elsewhere. We cover this in more depth, including two of our own pages currently carrying the status with a genuine canonical tag in place, in Duplicate without user-selected canonical: what it means.

"Duplicate, Google chose different canonical than user" is more pointed: you did declare a canonical tag, and Google looked at its own signals, such as inbound links, redirects and content similarity, and picked a different URL anyway. Google is telling you it trusts what it observed independently over the tag you wrote.

Real example, checked this session: https://crawlcove.com/blog/core-web-vitals-explained declares itself as its own canonical, which is correct, since that's the live URL, and https://www.crawlcove.com/blog/core-web-vitals-explained currently 301-redirects to it. But Search Console's live inspection still shows the www version indexed separately, with Google's own canonical choice pointing at the www URL rather than our declared one: a stale judgement from before the redirect was in place, sitting alongside a redirect that is correct and current today. It's a useful reminder that URL Inspection shows you what Google currently believes, which can lag what your site currently does by months.

If you see this status and disagree with Google's pick, the fix is rarely the canonical tag itself, since Google already saw it and chose otherwise anyway. Check instead for inconsistent internal links still pointing at the non-canonical version, and make sure any redirect between the two URLs is a clean single hop rather than a chain, since chained redirects are a common reason Google keeps trusting an older judgement.

Page with redirect

This one needs no action. It means Google inspected a URL and found it 301s (or 302s) somewhere else, exactly as intended.

Real example, checked this session: http://crawlcove.com/ inspects as "Page with redirect", correctly pointing at https://crawlcove.com/. That's the plain-HTTP version of the homepage doing exactly what an HTTP-to-HTTPS redirect should do. Seeing this status on a URL you deliberately redirect is confirmation the redirect is working, not a problem to chase.

Alternate page with proper canonical tag

Also informational, also nothing to fix. This status means Google inspected a URL, found it correctly declares a different page as its canonical, and is treating it exactly as instructed: not indexing the alternate, indexing the canonical instead. It's the system working as designed, the digital equivalent of a "see other page" sign that Google is respecting rather than ignoring.

Turning a status list into a priority order

Read across a whole site, these five statuses split into three buckets:

1. Wait and support it. Discovered - currently not indexed needs internal links and time, not action on the page itself.
2. Investigate and fix if warranted. Crawled - currently not indexed and the duplicate-canonical statuses mean Google made a call, and it is worth checking whether that call was the right one before assuming it will resolve on its own.
3. Ignore. Page with redirect and Alternate page with proper canonical tag are confirmation, not a problem.

A report full of status labels reads as one undifferentiated pile of "not indexed" until you sort it this way. Most sites, once sorted, have far fewer genuine problems than the raw count suggests.

Checking your own site's statuses

URL Inspection answers one URL at a time, which is fine for spot-checking a handful of pages the way we did above, but it won't tell you in one view which of your pages sit in which status, or why. That needs a crawl of your own site's actual link structure and content, read alongside what Google has indexed.

Crawl Cove pairs both: it crawls your site to map internal links, orphaned pages and duplicate content, and its Live Index Status feature calls Google's own URL Inspection API on demand for any URL you want a live, authoritative read on, without checking pages one at a time by hand. If you haven't connected Search Console yet, our guide to connecting it takes a few minutes. Run a full SEO audit to see which of these statuses show up across your whole site, not just the handful you happened to check.

Wrap-up

Five different labels, three different kinds of response. "Discovered" and "Crawled but excluded" are about crawl priority and quality respectively, and only the second is really a judgement worth investigating. "Page with redirect" and "Alternate page with proper canonical tag" are Google confirming your own setup is working. The two duplicate-canonical statuses sit in between, worth a look if the URL Google picked isn't the one you wanted, otherwise safe to leave alone. Check which status your own stuck pages actually carry before spending time fixing something that was never broken in the first place.