Crawled Currently Not Indexed: What It Means and How to Fix It

People paste this exact phrase into Google because it is alarming and unclear: the page is fine, it loads, Google has obviously seen it, and yet there it sits in Search Console marked “crawled, currently not indexed.” The status sounds like an error. It is not. It is a decision, and understanding what kind of decision it is tells you whether to fix the page, fix how it renders, or leave it alone.

This guide owns that one status and the indexation question around it. For where indexation sits in the order you should diagnose a struggling page, our technical SEO foundations guide covers the sequence. Here we go deep on the status itself.

Crawled versus discovered versus indexed: what each status actually means

Three statuses in the Page Indexing report get confused constantly, and the difference between them is the difference between the right fix and the wrong one.

Crawled, currently not indexed means Google fetched the page, evaluated its content, and made a deliberate choice not to store it. The page exists in Google’s crawl records but not in the index. This is a judgement, usually about quality or duplication.

Discovered, currently not indexed means something different: Google knows the URL exists, from your sitemap or an internal link, but has not actually crawled it yet. That is typically a crawl-budget or queue issue, and it often points to Google deciding the page is not worth the crawl resource, which is itself a soft quality signal.

Indexed means the page is in the index and in the contest. Note the line that catches people out: indexed is not the same as ranking. A page can be fully indexed and still rank for nothing, which is a content and authority problem, not an indexation one.

The practical takeaway: “crawled” means Google looked and passed, “discovered” means Google has not looked yet. They need different responses, and treating them as the same problem is the first mistake.

Why Google walks away from a page it already crawled

Google does not index every page on the web. Its index is finite, and it filters aggressively to keep search quality up, so some pages simply do not make the cut. When Google crawls a page and declines to index it, the reason is almost always one of these:

• Thin content relative to what already ranks for the topic. If the page says less, and less usefully, than the results already in the index, Google has no reason to add it.
• Near-duplication of other pages, on your own site or elsewhere. If the page substantially repeats content Google already has, it gets passed over.
• Low perceived value or demand. Pages nobody searches for and nothing links to read as low priority.
• A site-level quality signal. Google’s own guidance is clear that page quality has to be high enough to warrant indexing, and that bar is applied in the context of the whole site. A lower-authority domain can find Google rationing how much of it gets indexed.

Worth keeping in proportion: almost every site has something in this report, and a lot of it is meant to be there. Feed URLs, filtered and faceted variants, tag archives, paginated pages and the like routinely sit in “crawled, currently not indexed” and are fine left alone. The signal to act on is when pages you actually want indexed, your money pages and key content, are the ones sitting there, or when the count suddenly spikes.

The duplication and templating trap

The most common avoidable cause is templated pages that are technically distinct URLs but substantially the same page. A set of location pages that differ only by a city name in the heading. Filtered category URLs that return near-identical content. Programmatic pages spun up at scale with a variable swapped in.

Google sees these for what they are. A unique URL is not the same thing as a page worth indexing, and the crawler is good at recognising when twenty pages are one page wearing twenty different town names. When that happens, Google indexes one and leaves the rest in “crawled, currently not indexed”, or passes on all of them.

The fix is a real decision, not a tweak: consolidate the near-duplicates into one strong page, genuinely differentiate them so each earns its place with distinct and useful content, or accept that some of them should not exist and remove them. Adding more thin variants makes the pattern worse, not better.

When it is actually a rendering problem, not a quality one

Here is the cause almost every generic guide misses, and the reason two sites with the identical status need opposite fixes. Sometimes the page is not thin at all. It is rich and useful in a browser, but the content only exists after client-side JavaScript runs, and the version Google evaluated was a near-empty shell. Google indexed the shell, judged it thin, and walked away, and the status is identical to a genuine quality problem.

You tell the two apart with the URL Inspection tool. Inspect the URL, open the crawled page view, and look at the rendered HTML Google actually captured. If your main content, the body copy, the headings, the internal links, is present in that rendered HTML, the problem is genuinely quality or duplication. If your main content is missing from what Google rendered, even though it is right there in the browser, you have a render gap, and no amount of improving the content will help until the crawler can see it.

The same status, “crawled, currently not indexed”, comes from two opposite problems. One is a page that says too little. The other is a page that says plenty, to everyone except the crawler.

This matters because the fix diverges completely from here. A render gap is its own subject with its own diagnosis, and we cover it in full in our guide to JavaScript SEO and the render gap. The point for this status is simply that you must rule the render gap in or out before you spend a single hour rewriting content, because if the cause is rendering, the rewrite changes nothing.

The fix, in order

Once you know which problem you have, the sequence is straightforward. Do it in this order, because each step rules out a cause before you spend effort on the next:

• Confirm the status is current. Search Console data lags reality. Inspect the URL and check the last crawl date, since the page may already have been indexed since the report was generated. Do not diagnose a problem that has resolved itself.
• Rule out the render gap. Check the rendered HTML in URL Inspection as above. If the content is missing for the crawler, that is your problem, and it is a rendering fix, not a content one.
• Check for an accidental block. This status usually is not a stray noindex tag or a robots rule, but rule it out anyway, an X-Robots-Tag header from a CDN or a misconfigured rule can block indexing invisibly.
• Strengthen the page itself. If it is a genuine quality call, make the page deeper and more distinct than what already ranks, and point internal links at it from relevant, authoritative pages on your own site so its importance is signalled.
• Request indexing, once. Use URL Inspection to request indexing after the fix. Understand that this is a request, not a command: it does not guarantee indexing, and re-submitting the same URL will not get it crawled any faster.

What not to do

The wasted effort around this status is predictable, and avoiding it is half the battle:

• Spamming the indexing request button. Re-requesting the same URL repeatedly does nothing. The button is a hint to Google, not a lever, and Google’s own guidance is explicit that repeated requests do not speed up crawling.
• Building links to a thin page. If the page is thin, external links do not fix the thinness. You are pointing authority at a page Google has already judged not worth indexing.
• Optimising Core Web Vitals on a page that is not in the index. Page speed is irrelevant to a page Google has not indexed. Fixing performance here is effort spent on a metric that cannot help until the page is actually in the contest, which is exactly the diagnose-in-the-right-order point our foundations guide makes.

FAQs

What does “crawled, currently not indexed” mean?

It means Google fetched your page, evaluated its content, and made a deliberate decision not to store it in the index. The page is in Google’s crawl records but not in search results, so it cannot rank for anything. It is not an error or a technical block in most cases. It is a judgement, usually that the page is thin, duplicative or low-demand, or occasionally that the page renders empty for the crawler.

How is it different from “discovered, currently not indexed”?

The difference is whether Google has actually crawled the page. “Crawled, currently not indexed” means Google fetched and evaluated it and chose not to index it, a quality or duplication judgement. “Discovered, currently not indexed” means Google knows the URL exists but has not crawled it yet, usually a crawl-budget or queue issue that often reflects Google not prioritising the page. One is “looked and passed”, the other is “has not looked yet”, and they need different responses.

How long does it take to get a page indexed?

There is no guaranteed timeframe. New content can take a few days to a few weeks to be indexed, and Google does not promise that every page will be indexed at all. Requesting indexing through URL Inspection can reduce the lag, but it is a request, not a guarantee. If a page has been sitting in “crawled, currently not indexed” for a while, the delay is not the issue, the page has been judged and passed over, and the fix is the page itself.

Does requesting indexing in Search Console force Google to index a page?

No. The Request Indexing button is a hint, not a command. It places the URL in a priority queue for crawling, but Google still decides whether the page is worth indexing, and re-submitting the same URL repeatedly will not get it crawled any faster. If Google declined to index a page on quality grounds, requesting indexing again changes nothing. You have to improve the page first, then request indexing once.

Can thin or duplicate content cause non-indexation?

Yes, and it is the most common cause. If a page is thin relative to what already ranks, or substantially duplicates other pages on your site or elsewhere, Google often crawls it and declines to index it. Templated pages that differ only by a city name or a filter value are a classic example. The fix is to consolidate near-duplicates, genuinely differentiate the pages, or remove the ones that do not deserve to exist, not to add more thin variants.

Why is my page indexed but ranking for nothing?

Because indexing and ranking are different things. Being indexed means the page is eligible to appear in search results. Ranking means it actually competes for queries, which depends on content quality, relevance, topical authority and competition. A page can be cleanly indexed and still rank for nothing because the content is too generic or the keywords too competitive. If URL Inspection confirms the page is on Google, the problem is ranking, not indexation, and the fix is in content and authority.

Last reviewed: June 2026

This article provides general information about Google indexation and is not affiliated with or endorsed by Google. Search Console reports, statuses and tool behaviour change, and indexing is never guaranteed. Verify the current behaviour of the Page Indexing report and URL Inspection tool against Google’s own documentation before relying on it.