~/search-console/crawled-currently-not-indexed

§ page indexing report

judgement call

"Crawled - currently not indexed" in Search Console

The most common and least actionable row in the report. Google fetched the page, read it, and decided not to index it. No tool can verify a fix for this one, including ours.

Nothing technical is broken. Google decided the page was not worth indexing.

check a url →

§ check your url

Is it still happening?

This is the one page in this hub where we cannot confirm a fix, and we are not going to pretend otherwise. What we can do is eliminate every technical cause at once: status, crawlability, indexability, canonical, and how much text the page actually contains.

what this proves

Whether anything technical is blocking indexing. If something is, it is more specific and more fixable than the label Google gave you.

what it cannot prove

Whether Google will index the page. This row is a judgement about whether the content earns a slot, and nothing measurable from outside predicts it. A clean result here means the mechanics are not the problem, which narrows the question to the content and leaves it there.

§ what google is telling you

What this error actually means.

Google requested this URL, received it, parsed it, and chose not to add it to the index. Nothing blocked it. There is no directive to remove, no status code to fix, and no tag to correct.

This is a judgement about whether the page is worth a slot in the index. Google has explicitly said no fix is guaranteed and the page may be indexed later without you changing anything. That is unsatisfying, and it is also the honest position.

Which means the useful work is elimination. Roughly a third of the time there is a technical cause the label obscures: a near-duplicate of another page, a thin template, a page nothing links to. The rest of the time the answer is that the page does not yet justify inclusion, and no amount of technical auditing will change that.

Be sceptical of any tool, including this one, that claims to confirm a fix for this row. What can be verified is that nothing technical is in the way. What cannot be verified is Google's opinion.

§ causes

6 things that produce this error.

Ordered by how often they turn out to be the cause, not by how obvious they look.

The page duplicates something already indexed

Not necessarily word-for-word. Location pages differing by a town name, product variants differing by size, or tag archives listing the same posts in a different order are all near-duplicates in practice. Google indexes one and leaves the rest here, without labelling them duplicates.

There is not enough on the page to be worth a slot

A page that is mostly navigation, a stub with two sentences, an auto-generated listing. There is no word count threshold and adding filler does not help. The question Google is answering is whether this page would satisfy anyone searching, and a page with little to say answers it badly.

Nothing on the site treats the page as important

It is linked once from a footer, or from a sitemap and nowhere else. Internal linking is how a site signals which of its own pages matter, and a page nothing links to prominently is one the site itself has not argued for.

Site-wide quality dragging individual pages down

Google assesses sites as well as pages. A site with thousands of thin URLs gets a smaller share of the index across the board, and pages that would be indexed on a healthier domain sit in this row instead. This is why the fix is sometimes removing pages rather than adding them.

The page is new and still in the queue

Crawled and not yet indexed is a legitimate intermediate state, particularly on a new site or after a large publishing push. Days to a few weeks is normal, and a page can move out of this row without you doing anything.

Crawl budget spent on URLs that do not matter

Faceted navigation, session parameters, and infinite calendar pages generate URLs faster than Google will crawl them. On a large site this genuinely crowds out real pages, and the fix is to stop producing the noise rather than to promote the individual page.

§ the fix

How to clear it.

step 1

Rule out the technical causes first, then stop auditing

Confirm the page returns 200, is crawlable, carries no noindex, canonicalises to itself, and renders its content without JavaScript. That is the complete technical checklist. If it passes, further technical auditing will not help and the problem is the content.

step 2

Ask what this page offers that an indexed page does not

Compare it against a page on your site that is indexed. If you cannot articulate why someone would want this one instead, Google cannot either. The productive move is usually to merge it into the stronger page rather than to improve it in place.

step 3

Link to it as though it matters

Add contextual links from relevant indexed pages, using descriptive anchor text. A page linked only from a sitemap is one your own site has declined to vouch for, and internal links are the clearest way to change that.

step 4

Consider removing pages rather than adding them

Counterintuitive and often correct. If a section is full of near-identical thin pages, consolidating them into fewer substantial ones tends to move the survivors into the index. Noindex or remove the ones with nothing to say, and stop generating URLs nobody will search for.

step 5

Then give it time, and do not keep requesting indexing

Repeatedly requesting indexing for a page Google has already declined does not change its assessment. Make a real change, request once, and check back in a few weeks.

§ related

Next to check.

blockingDiscovered - currently not indexedGoogle knows this URL exists and has not fetched it yet. Unlike its near-namesake, this one usually has a measurable cause: your server is slow, or you are asking for more crawling than you have earned.blockingDuplicate without user-selected canonicalGoogle found several URLs with the same content, you did not say which one counts, so it picked for you. Here is how to take the decision back.blockingSoft 404Your server says 200 and your page says the content is gone. Google believes the page, not the status code, and refuses to index either.toolMeta Tag CheckerCheck your page title, meta description, viewport, charset, and robots tags.

→ How to Audit Your Website for SEO (Step-by-Step)

LintPage rules covering this: thin-content, content-to-html-ratio, canonical-self-referencing, title-uniqueness

§ faq

Questions, answered.

How do I fix "Crawled - currently not indexed"?

There is no guaranteed fix, and Google says so directly. Rule out the technical causes, which takes minutes, then treat it as a content question: is this page distinct from, and as useful as, the pages that do get indexed? Most durable improvements come from consolidating thin pages into fewer strong ones and linking to them properly, not from technical changes.

Will the page eventually be indexed on its own?

Sometimes, yes. Google states that URLs in this row may be indexed later without any action from you, and on a new or recently expanded site that is a common outcome. If a page has sat here for months while comparable pages are indexed, waiting longer is unlikely to be the answer.

Does this mean my content is low quality?

Not necessarily, and it is worth resisting that reading. The more common causes are duplication with another page on your own site, thin templated pages, and poor internal linking. Google is deciding whether the page adds anything to what it already has, which is a comparison rather than a verdict on the writing.

Should I request indexing repeatedly?

No. Requesting indexing queues a crawl; it does not change the assessment that follows. Google has crawled this page already, which is what the label says. Repeated requests for an unchanged page achieve nothing. Change something real, request once, then wait.

Can too many pages cause this?

Yes. Faceted navigation, tag archives, and parameterised URLs can generate more addresses than Google will crawl and index for a site of your size, and the thin ones crowd out the real ones. Cutting the number of low-value URLs frequently moves the remaining pages into the index without touching them.

Can a tool confirm I fixed this?

No, and be wary of any that claims to. A checker can prove that nothing technical is blocking indexing, which is genuinely useful because it stops you auditing something that is already fine. It cannot predict whether Google will judge the page worth indexing, because that assessment is not exposed anywhere and is not derivable from the page itself.

§ before the next deploy

Catch this one before Search Console does.

Search Console tells you weeks after the fact. LintPage runs 60 checks against a URL in about 30 seconds. Free, no signup.

run a full scan →