Guide

Crawled, Currently Not Indexed: Causes and Fixes

Crawled, currently not indexed means Google fetched the page and chose not to keep it in the index. The page was seen. It was not judged worth storing, so the fix is usually quality, duplication or signals, not a resubmit.

Crawled, currently not indexed is a Search Console status. It means Google visited the page, read it, and decided not to add it to its index for now. The page is not blocked and not broken. Google judged it as not worth storing, or saw it as a copy of something it already holds. Fixing it means making the page worth indexing and telling Google clearly that it matters.

What the status actually means

You find it in Search Console under Indexing, then Pages, in the list of reasons pages are not indexed. Each URL listed was fetched by Googlebot. Nothing stopped the crawl. After crawling, Google decided against indexing.

Google does not say why for each page. That is why this status frustrates owners. You have to work out the cause from the evidence, one group of pages at a time.

Do not confuse it with its neighbour. Our guide on Discovered, currently not indexed covers pages Google knows about but has not crawled. Different report, different problem.

How to tell if it is a real problem

Not every URL here needs rescuing. Start by sorting the list.

  1. Export the affected URLs from the report.
  2. Mark which ones you actually want to rank.
  3. Ignore the rest: utility pages, filter combinations, tag archives, old tests.

If the pages you want are in the list, or the number is growing, treat it as a problem. A sudden rise after a redesign or a change to templates is a warning sign worth chasing.

The usual causes

Likely causes

Why Google crawls and still skips a page

Thin or empty content

Little unique text, or a page that adds nothing beyond what the site already says.

Duplicate or near duplicate

Pages that match another page closely, so Google keeps only one version.

Low value at scale

Thousands of auto generated or templated pages with small changes.

Weak internal links

Orphaned or deeply buried pages with few links pointing at them.

Rendering problems

Content that only appears after JavaScript runs and fails to load for Google.

Site quality signals

A site with a lot of unhelpful content can see new pages held back.

Several can apply at once. Pages that are both thin and orphaned are the classic case.

Step by step fix

1. Inspect one page properly

Open the URL Inspection tool and test a sample URL. Look at the crawled page and the rendered HTML. Confirm that the main content is present in what Google saw. If the rendered page is empty or missing text, you have a rendering problem. Our guide on JavaScript SEO rendering covers it.

2. Check canonicals and duplicates

Look at the Google selected canonical in the inspection result. If Google chose a different URL than the one you set, it considers the page a duplicate. Fix the real duplication, not only the tag. See canonical tag mistakes and duplicate content fixes.

3. Judge the content honestly

Ask what this page offers that the pages already indexed do not. If the honest answer is nothing, add real substance, merge it into a stronger page, or accept that it should stay out of the index.

Link to important pages from pages that already rank and get crawled often. Use clear anchor text. A page with no internal links tells Google it is not important.

5. Clean the sitemap

Your XML sitemap should list only the pages you want indexed. Removing junk URLs focuses Google on the pages that matter.

6. Request indexing, then wait and re-check

After real changes, use Request Indexing on key pages and re-check the report. Expect it to take time. Pages move out of the status as Google recrawls and reassesses them.

Triage

Crawled not indexed checklist

Work through the list on a sample of five to ten URLs from the report. If the same answer repeats, you have found the pattern, and the fix usually applies to the whole group.

Check these in order

  • Does the rendered page in URL Inspection show the main content
  • Did Google pick a different canonical than yours
  • Is the page unique enough to deserve its own result
  • Does the page have internal links from crawled pages
  • Is the URL in your sitemap, and should it be
  • Did the count jump after a template, plugin or redesign change

When this points to a bigger problem

A few listed pages are normal. Hundreds or thousands of pages you care about means something is wrong at the site level, such as mass thin content, a crawl budget problem or a quality issue. Our short answer on why pages are not indexed lists the other statuses to rule out.

When to call for help

Get help when large groups of important pages stay unindexed after you fixed the obvious causes, when the count keeps climbing, or when you cannot tell whether the cause is content, duplication or rendering. Guessing here wastes weeks.

We start with the crawl evidence and name the cause before we suggest a fix. Ask for a free SEO triage and we will tell you which pages are worth saving. Our technical SEO fixes work covers the repairs.

FAQ

Questions owners ask us

Will requesting indexing fix Crawled, currently not indexed?

Rarely. Google already crawled the page and decided against indexing it. Requesting indexing again asks it to look at the same page. Improve the page or its signals first, then request indexing.

Is this status always a problem?

No. Pages such as thin tag archives, filtered listings or old press pages may be better left out of the index. It becomes a problem when pages you want to rank sit in this report.

How is this different from Discovered, currently not indexed?

Discovered means Google knows the URL but has not fetched it yet. Crawled means Google fetched it and decided not to index it. The causes and fixes differ, so check which report your URLs are in.

Get started

Tell us where it hurts.

Your site, what changed and when. We reply with a first read on the cause.