Skip to content
Technical SEO 11 min read By Lewis Jones Editorial policy

Search Console Indexing Issues Explained

Search Console indexing issues explained: every status in the Page indexing report, what each means, which need action, with examples from our own site.

Part of Technical SEO Guide: Crawl, Index, Speed

Key takeaways

  • Search Console's Page indexing report sorts every URL into one status, and most of them describe a queue position, an instruction Google obeyed, or a judgement Google made, not an error you caused
  • The statuses that always need fixing are the ones where Google could not reach the page at all: server errors, redirect errors, 401 and 403 refusals, and robots.txt blocks on pages you want indexed
  • "Crawled - currently not indexed" and "Duplicate, Google chose different canonical than user" are the judgement calls worth investigating
  • "Page with redirect", "Alternate page with proper canonical tag" and "Excluded by 'noindex' tag" are usually confirmation that your own setup is working
  • Every status reflects Google's last crawl of that URL, so check the crawl date before acting on any of them

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, Blocked by robots.txt, and a dozen others. Some of these need action. Most don't. This page is the hub for the whole report: what each status means, which ones are worth investigating, a link to a full explainer for each, and real examples pulled from our own site's URL Inspection results, first on 21 September 2026 and rechecked on 6 October 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.

Note

Every status covered here has its own explainer, linked from its section. For the raw definitions, Google's own Page indexing report documentation is the authoritative source; each of our posts quotes it and then goes into the causes and fixes Google's page does not.

Search Console indexing issues, sorted by what they ask of you

Read across a whole site, the statuses in the report split into four groups:

  1. Google could not get the page. Server error (5xx), Redirect error, 401 and 403 refusals, Soft 404, and Blocked by robots.txt on a page you want indexed. These always need fixing, because nothing else you do reaches Google until they are.
  2. Google made a judgement. Crawled - currently not indexed, and the two duplicate-canonical statuses. Worth checking whether Google's call was the right one.
  3. Google is waiting. Discovered - currently not indexed. Needs internal links and time, not action on the page.
  4. Google did what you asked. Page with redirect, Alternate page with proper canonical tag, Excluded by 'noindex' tag, and Not found (404) for a page that is meant to be gone. Confirmation, not a problem.

Two warnings sit outside those groups: Indexed, though blocked by robots.txt, and Page indexed without content. Both describe a page that is in the index but should not be, or is in the index but empty, and both need action.

Google could not get the page

Server error (5xx)

Your server answered Googlebot with a 500-level status. Google treats it as temporary at first, slows its crawl of the whole site, and drops the page if the error persists. The usual causes are overload under crawl bursts, upstream timeouts, a failed deploy, and bot protection returning a 503 to crawlers. Full explainer: server error (5xx) in Search Console.

Redirect error

Google tried to follow a redirect and could not finish: a chain past ten hops, a loop, a URL that grew past the length limit, or a bad or empty hop. Unlike "Page with redirect", nothing at either end is being indexed. Full explainer: redirect error.

Blocked due to unauthorized request (401) and Blocked due to access forbidden (403)

The server refused Googlebot: 401 asked for a login it cannot give, 403 refused it outright. Correct for private areas, and the most damaging status in the report for a public page, where a firewall, geo-block or leftover staging password is almost always the cause. Full explainer: blocked due to access forbidden (403), which covers both codes.

Blocked by robots.txt

A Disallow rule stopped Google fetching the URL. Right for admin paths and crawl traps; a serious problem for any page you want ranking, because Google has not even read it. Note that robots.txt controls crawling, not indexing, which is why a blocked URL can still appear in results. Full explainer: blocked by robots.txt.

Soft 404

The page returns a "not found" message with a 200 status instead of a real 404. Google treats it as missing but your server keeps saying it exists. The fix is to return a proper 404 or 410, or to give the page real content. A site that does this for every unknown URL creates a crawl trap; the soft 404 issue page covers how to find and fix it. Full explainer, with the five patterns that trigger it and how common they are across 1,000 UK sites: Soft 404 in Search Console.

Google made a judgement

Crawled - currently not indexed

This is the one worth paying closest 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. Full explainer: crawled currently not indexed.

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 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. To check duplicate content on your own site before Google groups it, crawl it with a duplicate content checker. Full explainer, including two of our own pages carrying the status with a genuine canonical tag in place: duplicate without user-selected canonical.

"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. Full explainer: Duplicate, Google chose different canonical than user.

Real example, rechecked on 6 October 2026: 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 301-redirects to it. But Search Console still shows Google's canonical choice pointing at the www URL, from a crawl on 26 July 2026, with the www URL itself sitting at "Crawled - currently not indexed" since 1 July: a stale judgement from before the redirect was in place. 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.

Google is waiting

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. If a page has been here for weeks, the lever is usually internal links and overall site authority. Full explainer: discovered currently not indexed.

Google did what you asked

Page with redirect

Google inspected a URL and found it 301s (or 302s) somewhere else, exactly as intended. The exceptions, a redirecting URL you wanted indexed or one your own sitemap and links still point at, are covered in the full explainer: page with redirect.

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.

Alternate page with proper canonical tag

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. The two cases worth checking are a canonical pointing at the wrong page, and a page that deserves to rank on its own. Full explainer: alternate page with proper canonical tag.

Real example, checked this session: https://www.crawlcove.com/pricing carries this status from a crawl on 16 July 2026, with Google's canonical and our declared canonical both https://crawlcove.com/pricing. The www address now redirects instead, so the status will change on the next crawl; nothing is wrong in either state.

Excluded by 'noindex' tag

Google fetched the page, found a noindex directive in the HTML or the response headers, and obeyed it. For login pages, internal search and thank-you pages it is the result you asked for. It needs action only when a page you want ranking is on the list, which usually traces to a plugin setting or a staging flag that shipped. Full explainer: excluded by noindex tag.

Real example, checked this session: https://crawlcove.com/login carries this status, last crawled 30 September 2026. It's a login form. Nobody should find it in search, and Google agreeing is the system working.

Not found (404)

Google requested a URL it discovered on its own and the server said the page does not exist. Google's own documentation says that is normal and needs no action for a page that is gone. The exceptions are a page you still want, a page that moved and should redirect, and a URL your own site still links to. Full explainer: not found 404 in Search Console.

The two warnings

Indexed, though blocked by robots.txt

Google indexed a URL it was not allowed to crawl, from links alone, so the result shows a bare address with no description. The fix runs against instinct: remove the block so Google can read a noindex, or remove it so Google can read the content. Blocking harder never works. Full explainer: indexed though blocked by robots.txt.

Page indexed without content

The page is in the index but Google could not read anything from it, usually because the content only exists after JavaScript runs and the render failed, or because the server showed Googlebot something different from what visitors see. Full explainer: page indexed without content.

Turning a status list into a priority order

Sorted this way, a report full of "not indexed" labels reads as a short list of real problems and a long list of confirmations. Work it top down: clear anything in the first group, because those pages are invisible until you do. Then look honestly at the judgement calls, which usually means the page's content and its internal links rather than its tags. Leave the waiting pages and the confirmations alone. 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. Bear in mind that every status reflects Google's last crawl of the page, which can be weeks old; how long Google takes to recrawl a page covers how to check that date before acting on a status.

Crawl Cove pairs both: it crawls your site to find the error pages, redirect chains, noindex directives, canonical conflicts, robots.txt blocks and empty pages behind these statuses, 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

Sixteen labels, four kinds of response. The errors, server, redirect, 401, 403 and robots.txt on pages you want, come first because Google cannot see past them. "Crawled but excluded" and the canonical overrides are judgements worth a look. "Discovered" is a queue. Everything else is Google confirming your own setup is working. Check which status your stuck pages actually carry before spending time fixing something that was never broken in the first place.

Frequently asked questions

What's the difference between "Discovered" and "Crawled - currently not indexed"?
"Discovered" means Google found the URL but has not fetched it yet, a queue position. "Crawled - currently not indexed" means Google did fetch it and chose, for now, not to index it, usually a quality or relevance judgement rather than a scheduling one.
Which Search Console indexing statuses are actual errors?
Server error (5xx), Redirect error, Blocked due to unauthorized request (401), Blocked due to access forbidden (403) and Soft 404 all mean Google could not get a usable page, and all need fixing on any URL you want indexed. Not found (404) is listed with them but is normally fine for a page that is meant to be gone.
Do I need to fix "Page with redirect" or "Alternate page with proper canonical tag"?
No. Both are informational labels Google applies correctly. A redirect is working as intended, and an alternate page correctly pointing its canonical elsewhere is exactly what canonical tags are for. Neither means anything is broken.
How do I check these statuses for my own URLs?
Search Console's URL Inspection tool checks one URL at a time. For checking many URLs at once against what a fresh crawl actually finds, see our guide to Live Index Status.
Does resubmitting my sitemap fix any of these?
It can prompt a faster recrawl in some cases, but it does not change Google's underlying judgement about duplication or quality. For statuses that reflect a decision rather than a queue position, the fix is on the page or its links, not the sitemap.

Audit your site the easy way

Crawl Cove finds these issues on your machine. Try the SEO Audit or see every feature.

Download free