Crawled, Currently Not Indexed: What It Means and Which Pages to Fix (or Let Die)

If you have opened the page indexing report and found a pile of URLs sitting under “Crawled, currently not indexed”, the honest short answer is this: Google crawled those pages, looked at them, and decided they were not worth adding to the index right now.

That sounds harsh, but it is usually not the emergency it feels like, and the popular fix doing the rounds (add author bios and E-E-A-T signals) mostly misses what the status is actually about.

Here is what it means, and how I decide which of these pages to fix, which to merge, and which to leave exactly where they are.

What “Crawled, currently not indexed” actually means

Google’s own page indexing report documentation defines it plainly: the page “was crawled by Google but not indexed”, and “it may or may not be indexed in the future; no need to resubmit this URL for crawling.”

So the page is not blocked, not broken, and not penalized. It was seen and, for now, passed over.

The detail people miss is who makes that call. In the report, the Source column for this row reads “Google systems”, not “Website”.

That wording matters, because it tells you this is Google’s own quality and duplication judgment, not something a tag on your site switched on.

On our own property the scale is easy to show. Out of 525 not-indexed URLs, 323 sit under this one status, with another 81 under the sibling “Discovered, currently not indexed”.

Most of that 323 is pages I am perfectly happy leaving out, which is the part the guides rarely say out loud.

Why author bios and E-E-A-T badges will not get a page indexed

The advice making the rounds is to bolt author bios, an about page, and “E-E-A-T signals” onto anything stuck here. I understand the instinct, but indexing selection does not work like a trust-badge checklist.

None of Google’s indexing docs mention author identity anywhere. Google’s John MuellerJohn MuellerSearch Advocate, GoogleGoogles „Search Advocate“ und der wichtigste offizielle Sprecher der Google Search Relations.LinkedInXSuchzentrale has been clear that the Quality Rater Guidelines, where the whole E-E-A-T idea lives, are not a guide for search rankings.

They tell human raters what good looks like; they are not a switch you flip on a page. E-E-A-T is a concept raters use, not an indexing gate the algorithm checks.

Now the honest caveat, because this is where the badge crowd is half right. Quality genuinely does affect indexing; Mueller names overall site quality as one of the two main reasons pages get crawled but not indexed.

The distinction is precise: raising the real value of a page, and of the site around it, can lift indexing, but pasting an author box onto a thin or duplicate URL changes none of that value. The myth is the cargo-cult shortcut, not the idea that quality matters.

What the algorithm actually weighs is spelled out in the URL Inspection documentation: “The page quality must be high enough to warrant indexing” and “The page cannot be a duplicate of another indexed page; it must either be unique, or selected as the canonical version of a set of similar pages.”

Quality and duplication. That is the real test, and no bio fixes a duplicate.

The real reasons a page gets crawled but not indexed

Strip away the folklore and a short list of causes explains most of what you see in that bucket:

• Duplication: the page is a near-duplicate of one Google already indexed, so adding it gains nothing and Google keeps the canonical instead.
• Thin value: the page does not carry enough unique value to earn its own slot, which is the quality bar the URL Inspection doc names.
• Crawl and server capacity: on very large sites Google simply does not crawl and index everything, so lower-value URLs wait or never make it in.

Mueller frames the non-technical side as mostly about overall website quality, with crawl and server capacity a factor mainly on very large sites.

This is also why crawling and indexing are not the same promise. Getting crawled just means Googlebot fetched the page; indexing is a separate decision that happens after, and a URL can be crawled many times and still never make the cut.

If your indexed count recently dropped and this bucket grew, do not assume the two are the same story; I walk through separating a real drop from a reporting recount in my guide on Search Console indexed pages decreasing.

And if the pages are thin because they earn nothing anyway, my note on impressions without clicks is the other half of reading that report honestly.

The eCommerce reason the guides skip: faceted and near-duplicate URLs

For stores, this status is very often self-inflicted, and almost no guide says so. Faceted navigation (every color, size, sort, and price filter) can spin up an effectively infinite set of URLs, and Google’s faceted navigation documentation is blunt that “oftentimes there’s no good reason to allow crawling of filtered items, as it consumes server resources for no or negligible benefit.”

So a store with thousands stuck in “crawled, currently not indexed” usually does not have a quality problem on its products; it has a crawl-space problem on its filters.

Google met a pile of near-identical filter combinations, indexed the ones worth keeping, and shelved the rest. That is the system working, not failing, and it is crawl budget you would rather spend elsewhere, as I cover in Auffinden des Kriechbudgets und seiner Anwendungsfälle.

The fix is not to force those URLs in, it is to stop them being crawled in the first place. A simple robots pattern that blocks the filter parameters while keeping the real collection pages open does most of the work:

# Stop crawlers wandering infinite filter combinations
User-agent: *
Disallow: /*?color=
Disallow: /*?size=
Disallow: /*?sort=
Allow: /*?products=all$

Canonical tags and nofollow help at the margins, but Google itself calls them “generally less effective in the long term” for this, so lead with crawl control and reserve indexing for the collection and product pages that actually sell.

Clean internal links into those pages do more than any amount of tinkering with the filters.

Should you fix, merge, or let an unindexed page die?

Here is the mindset shift that makes this status manageable: not every URL is supposed to be indexed. Google’s own documentation says it outright, “You should not expect all URLs on your site to be indexed, only the canonical pages”, and that a page marked duplicate or alternate is “usually a good thing”.

So before fixing anything, I ask whether the URL deserves a slot at all. Junk, filter, tag, and near-duplicate URLs staying out is the correct outcome, not a problem to solve.

The report even tells you to “use your judgment when deciding whether to address a given issue”, which is Google giving you permission to leave things alone.

For the URLs that do deserve indexing, the levers are unglamorous and they work:

• Raise the actual value: make the page genuinely more useful than what already ranks, because quality is the gate Google names.
• Kill the duplication: remove or canonicalize the near-duplicate versions so the page reads as unique, not a copy.
• Add internal links: point links from your strong pages at it, so Google sees the URL matters and reaches it sooner.

Then request indexing once and wait; a day or two is normal, and sometimes a week or two. Hammering the button does not speed it up.

What about the Indexing API and instant-indexing plugins?

This is the other tempting shortcut, and it is a dead end for normal pages. Google’s Indexing API quickstart states its scope directly: “The Indexing API can only be used to crawl pages with either JobPosting or BroadcastEvent embedded in a VideoObject.” Blog posts and product pages are simply not in scope.

Point it at ordinary URLs anyway and, best case, nothing sticks; worst case you draw attention you do not want, since the same doc warns that “all submissions through the Indexing API undergo rigorous spam detection” and that abuse “may result in access being revoked.”

I tested what these instant-indexing plugins actually do (and do not do) in a separate breakdown of whether they index anything, and the short version is that a 200 OK is not the same as getting indexed.

Hammering “Request indexing” has the same shape of problem: it is rate-limited, it does not compound, and the status definition itself says “no need to resubmit this URL for crawling.” Ask once for a genuinely new or fixed page, then let it be.

If an ugly variant is already indexed and you want it gone, the Removals tool is the right lever, not more indexing requests.

So, should you worry about “crawled, currently not indexed”?

In my opinion, most of the time, no. On the majority of sites this bucket is Google doing its job, filtering out duplicates, filters, and thin pages that were never going to earn their keep, and the honest move is to read it, not react to it.

The exceptions are real and worth catching. A genuinely valuable page stuck here deserves a proper look at its uniqueness and internal links, and a store drowning in filter URLs needs its crawl space cleaned up.

But if the fix you are being sold is an author bio, save your time; that is treating a value-and-duplication decision as if it were a trust badge you forgot to tick.

---

Share Link kopieren Als Markdown kopieren

Want our posts to show up more often on Google?

One step & Google will surface this site in your Top Stories.

Add us as a preferred source on Google

Abdullah Nouman eCommerce SEO, Agentic Commerce SEO & AI Search Specialist

I publish the industry's most critical SEO and AI Search blog, cutting through the hype and explaining what actually holds up in plain English.

Arbeite mit mir zusammen

Weiterführende Literatur

Zurück zu allen Beiträgen →

Why Your Search Console Impressions Spiked With No Clicks (Bots and a Logging Bug) Search Console Indexed Pages Decreased After a Freeze? Recount vs Real Deindexing Wie man das Problem "Sitemap konnte nicht abgerufen werden" in der Google Search Console löst: Eine ausführliche Anleitung