Crawled – currently not indexed: fix it or leave it?

Google fetched your page. It read it. It decided not to index it, for now.

That's Crawled – currently not indexed, and it stings more than its sibling Discovered – currently not indexed, where Google hasn't fetched the page at all. Here Google looked. This post covers what it may have seen, how to tell, and when the right move is to do nothing.

Short answer: Crawled – currently not indexed means Google fetched the page and decided, for now, that it wasn't worth adding to the index. It's a decision, not a fetch failure. The usual causes are pages that add little beyond what's already indexed, near-duplicate templates, conflicting duplicate signals, soft 404s, content missing from the rendered HTML, and a site-level doubt about quality. Group the URLs by template, compare them with indexed siblings, then improve, merge, redirect or noindex each group. Some pages are better left alone.

What the status means

Google's Page indexing report says the page was crawled but not indexed, that it "may or may not be indexed in the future," and that you needn't resubmit it. Its explanation of search adds that indexing isn't guaranteed, and lists low content quality among the common reasons.

It often isn't about the single page. Mueller said in 2021 that if five pages aren't indexed, "it's not that those five pages are the ones we would consider low quality", more that Google sees the site overall as a bit lower quality. On a July 2026 podcast he added that when Google has strong quality concerns it indexes less, and that when you see a bigger pattern with no technical reason, you need to step back and think about quality overall.

Search Console has several look-alike statuses:

Ask what Google asks first

Before debugging, put Google's own questions to the page. Its guidance on helpful content lists questions such as "Does the content provide original information, reporting, research, or analysis?" and "Does the content provide substantial value when compared to other pages in search results?"

Mueller's own version, from the same podcast, is blunter: some sites make you think "Anyone could have written this. This tells me nothing." He was clear that not all AI-generated content is bad. The test is whether the page has something only you could have written.

Google's spam policy on scaled content abuse sets the outer limit: many pages generated mainly to manipulate rankings, "no matter how it's created." Most pages in this status are nowhere near abuse. They're just not yet worth a slot. Our glossary has short entries on thin content and scaled content abuse.

Six reasons Google crawls a page and skips it

1. It adds little beyond what's indexed. Thin means little unique substance, not few words. A 1,200-word page that repeats what ten indexed pages already say is thin; a short page holding data nobody else has isn't.
2. It's a near-duplicate template page. Google groups pages with similar content and picks the most representative one; the rest are alternates. In a family where only the name changes, most siblings can end up as alternates or unindexed. See duplicate content.
3. Duplicate signals conflict. Google's canonicalization guide ranks redirects and rel="canonical" as strong signals and sitemap inclusion as weak, and says to link to the canonical URL internally. A sitemap listing URL A, a canonical pointing to B and internal links to C is a mixed message.
4. It's a soft 404. An empty category, a "no results" page or a sold-out shell that returns 200. Google defines a soft 404 as a friendly not-found message without a 404 status code. A 2xx status doesn't guarantee indexing either.
5. The content isn't in the rendered HTML. Googlebot renders 200 pages with headless Chromium and indexes the rendered HTML. Google also won't render JavaScript from blocked files or on blocked pages. If your main content appears only after a blocked script or a click, Google may have fetched an empty shell.
6. The site as a whole hasn't earned it. The pattern across many templates, with no technical cause, from the Mueller quotes above. Fixing one page won't move it.

Diagnose it in 20 minutes

1. Export and group. Open the row in the Page indexing report. The examples list is limited to 1,000 rows and may not show every URL, so export it and count by template. In our reading, a few scattered URLs are individual pages, while most of a family points to the template.
2. Run the sibling test. For each group, open two pages in this status and two indexed pages from the same template, side by side. What do the indexed ones have that the others lack: more unique text, data, inbound links, a more specific title? It's our heuristic, and the most useful step.
3. Inspect with URL Inspection. In the indexed result, compare the user-declared and Google-selected canonical. The tool says the live test can't predict canonical selection. Use View crawled page for the HTML Google received, and the live test's screenshot to see what it renders.
4. Search a distinctive sentence in quotes. If the text exists elsewhere, Google may see yours as derivative. Also check your own site for repeats.
5. Triage by value. Fix pages that should win a query first: ones with real search demand, inbound links or a job in your funnel. Leave the rest until the pattern is clear.
6. Run the basics. Our free SEO checker scores title, description, H1, canonical and indexability, the canonical checker reads the canonical from HTML and header, and the Google index checker runs a live site: search. That's an estimate, so confirm in Search Console.

Fix it by cause

To consolidate duplicates, prefer a redirect or rel="canonical": Google says it doesn't recommend noindex for steering canonical selection within a site, because it blocks the page from Search completely. Use a redirect when the old URL has no purpose, a canonical when both must exist, and noindex only for pages that should exist for visitors but not for search.

"Add what only you have" differs by page type. Our bar for each family, from the programmatic SEO post: directory pages need verified pricing and link type, comparisons need verified differences with sources, and glossary terms need a definition and an example that wouldn't fit any other term.

In a 2022 answer reported by Search Engine Journal, Mueller listed what helps Google see which pages matter: fewer, better pages (he said it sometimes means that), internal links, links from the home page, external links and sitemaps. His caveat: it's rarely one trick. After a fix, link the page from a hub Google already crawls, keep its sitemap lastmod honest, and give a recrawl time: Google says days to a few weeks. Our Search Console guide covers the report itself.

How to know it worked. Don't judge by the site total. Split your sitemaps by page family, filter the report by each, and watch one family at a time: the count in this status, the indexed count and impressions. Give changes two to four weeks, our rule of thumb. If a fixed template doesn't move, the problem is probably wider than that template.

When to leave a page alone

Google's report documentation asks whether it's OK for a page not to be indexed and answers "Absolutely": robots.txt blocks, noindex, duplicates and pages that are inappropriate to index, such as filtered variations. Mueller said the same of whole sites: it's "never going to be the case that we index 100% of everything".

Leave it alone, or make that official with noindex and a sitemap exclusion, when:

• The page has no search job. Thank-you pages, internal search results, filtered views, tag archives and login pages answer no query.
• It's useful to visitors but not to search. Keep it, and keep it out of the sitemap.
• It's a variant you keep for users. Point its canonical at the main page.
• It's brand new. Google says a new page can take about a week or so; give it a few weeks before you judge it.
• It's old and weak. Prune or merge it. Polishing a page nobody needs doesn't pay.

Our rule: if the page has no query to win, leave it. If it should win a query and doesn't, fix it.

Our own case: 23 pages

On 4 October 2026 the Page indexing report listed 23 launchranked.com URLs as Crawled – currently not indexed. That's 23 of the 667 URLs not indexed, about 3%, and under 2% of the 1,326 the report knows about. The big group is the 613 in Discovered, which we cover in the other post.

We won't name the 23 or guess at their cause before looking. Our plan is the one above: export the list, group it by template, run the sibling test on each group, and fix, merge or leave each group. Our pages are mostly built from templates and typed data (directories, comparisons, alternatives, glossary, tools, product and maker pages). The status is familiar: it filled up on Versely after our 2,500-post month. If it's one template, one fix will cover it. If they're scattered, they're individual pages. We'll add what we find to this post.

What we'd avoid: mass Request indexing, rewriting only titles, padding pages with filler to raise word counts, and deleting everything in a panic. The glossary entry on Crawled – currently not indexed is the short version.

If you'd rather have this loop run for you, quality gates before publishing are what Autopilot is built around.