By SitemapFixer Team
Updated September 2026

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

Rule out technical problems in your sitemap firstFind My Sitemap

What does “Crawled - currently not indexed” mean?

It means Google fetched your page, then chose not to add it to its index for now. Nothing is blocked or broken; Google judged the page not worth indexing yet.

  • •Google says it may or may not be indexed later, and there is no need to resubmit it.
  • •Rule out rendering and canonical problems first with URL Inspection.
  • •If many pages are affected, compare them with indexed ones: the cause may be site-wide.
  • •Fix it by merging duplicates or making the page clearly more useful.
Free scan: finds your sitemap and tests 30 URLs for 404s, redirects, noindex and canonicals→

“Crawled - currently not indexed” is one of the reasons listed under “Why pages aren’t indexed” in Search Console’s Page indexing report. In URL Inspection it reads “Page is not indexed: Crawled - currently not indexed,” and people often shorten it to “crawled but not indexed.” Google’s help text for it is two sentences long: the page was crawled but not indexed, it may or may not be indexed in the future, and there’s no need to resubmit it. Everything below is about what to do with that.

Crawling Is Not Indexing

Google Search works in three stages: crawling (fetching the page), indexing (analyzing it and storing it), and serving (showing it for searches). Not every page makes it through each stage. Google’s own guide says it plainly: indexing isn’t guaranteed, and not every page Google processes will be indexed. Among the common reasons it names first: the quality of the content on the page is low.

So this status is a decision, not a malfunction. Google could read the page. It chose not to store it, at least for now. That’s different from “Discovered - currently not indexed”, where Google knows the URL but hasn’t fetched it yet.

Step 1: Rule Out the Technical Causes

Before you rewrite anything, spend five minutes making sure Google saw the page you think it saw.

  • Check what rendered. In URL Inspection, run Test live URL and open View tested page. If the main text is missing from the screenshot or HTML, Google judged an empty shell. Fix rendering first; content changes won’t matter until Google can see them.
  • Check the canonical. The page should declare itself as canonical, and your internal links and sitemap should use the exact same URL (https, www or not, trailing slash). Mixed signals split attention across versions of one page.
  • Check the sitemap. List only URLs that return 200, have no noindex tag, and are canonical. A sitemap full of redirects and dead links is noise around the pages you care about.

Step 2: Is It a Page Problem or a Site Problem?

This step saves the most wasted work. Google has said its core ranking systems work mainly at the page level, but it also has “some site-wide signals.” If a handful of pages are affected, the cause is probably on those pages. If most of a site sits in this bucket, polishing pages one at a time rarely moves it.

A quick test: export the affected URLs from the report, then pick a sample of pages that are indexed. Compare the two groups on what you can measure: word count, template, internal links pointing in, how unique the text is, and whether anyone searches for the topic.

  • The affected pages are clearly weaker (thinner, one shared template, few links in): it’s a page problem. Fix that template or those pages.
  • The two groups look the same on every measure: the verdict is probably about the site as a whole. The fix is fewer, stronger pages across the site: merge overlapping pages, improve or retire thin sections, and stop adding more pages of the same kind.

Step 3: Fix Each Group of Pages

Duplicates and near-duplicates

If two or more of your pages answer the same question, Google has little reason to index both. Pick the strongest one, move the best material from the others into it, and 301 the others to it. One complete page beats three partial ones.

Thin pages on topics people search for

Look at the pages that rank for the query and note what they cover that yours doesn’t. Then make yours clearly more useful. Google’s guide to helpful content suggests checks such as: does the page offer original information or analysis, does it cover the topic fully, and would someone leave feeling they learned enough? Adding words without adding answers doesn’t pass those checks.

Pages with no search demand and no job for visitors

Some pages don’t need to be in Google: thin tag archives, filter combinations, near-empty profiles. Take them out of the sitemap, and either merge them into a better page or leave them unindexed. Don’t expect a noindex tag to save crawl budget, though: Google’s crawl budget guide notes that it still requests noindexed pages before dropping them.

Pages nobody links to

A page reachable only from the sitemap can look unimportant to visitors and to crawlers. Link to it from related pages with descriptive anchor text.

Step 4: Ask for a Recrawl, Once

After a real change, use Request indexing in URL Inspection for your most important URLs. Google’s recrawl guide sets expectations: crawling can take anywhere from a few days to a few weeks, requesting a crawl doesn’t guarantee indexing, and there’s a quota for individual requests. Asking again for the same URL won’t get it crawled any faster. For many URLs, keep the sitemap accurate, with honest lastmod dates, and let Google work through it.

What Doesn’t Help

  • Resubmitting the same URL again and again. Google says there’s no need to resubmit these URLs, and repeat requests don’t speed anything up.
  • Padding the page. Longer isn’t better if the extra text says what other pages already say.
  • Publishing more pages like the ones that weren’t indexed. If the verdict is site-wide, more of the same adds to the problem.
  • Changing only the title or meta description. They help how a page appears in results. They don’t change what the page offers.

Crawled vs Discovered - Currently Not Indexed

Crawled: Google fetched the page and chose not to index it. The lever is the page (or the site): quality, uniqueness, usefulness. Discovered: Google knows the URL but hasn’t fetched it; Search Console’s help says the crawl was usually rescheduled because it was expected to overload the site, which is why no crawl date shows. The levers there are server speed, crawl demand and fewer low-value URLs. See the discovered guide for that side.

FAQ

What happens if a page is crawled but not indexed?

It can’t appear in Google Search results. Google may still index it later, for example after the page or the site improves, but there’s no date and no guarantee.

How long does it take to get indexed after I fix the page?

Google’s recrawl guide says crawling alone can take a few days to a few weeks. Indexing then depends on whether Google now thinks the page is worth storing. Check a few fixed URLs in URL Inspection instead of watching the report total.

Is “Crawled - currently not indexed” an error?

No. Search Console lists it as a reason a page isn’t indexed, not as a crawl error. Whether it needs fixing depends on the page: a thin tag archive can stay there, while a key product or guide page shouldn’t.

Can a technical problem cause it?

Yes, indirectly. If the main content doesn’t render for Googlebot, Google judges the empty version. That’s why Step 1 comes before any rewriting.

Rule out sitemap problems first
Free - finds your sitemap and tests 30 URLs live
Find My Sitemap Free

Related Guides