Site icon Saad Raza SEO

Crawled Currently Not Indexed: Causes and Fixes

Cover graphic for the SEO measurement guide "Crawled Currently Not Indexed: Causes and Fixes" by Saad Raza SEO

“Crawled, currently not indexed” means Google fetched your page but chose not to add it to its index, for now. It is a quality and value decision, not a technical error. To fix it, find out whether the page deserves indexing, then improve it, consolidate it, link to it properly or deliberately leave it out.

Not every URL earns a place in search results: Ahrefs found that 96.55% of the roughly 14 billion pages in its index get zero organic traffic from Google, which is a useful reminder that a handful of unindexed URLs is rarely a crisis.

What “crawled, currently not indexed” means

In the Page indexing report, this status sits among the reasons pages are not indexed. Google’s own definition on the Page indexing report help page is plain: the page was crawled by Google but not indexed, it may or may not be indexed in the future, and there is no need to resubmit the URL for crawling.

Read that carefully, because it tells you three things. Google has already visited, so this is not a crawling or access problem. The decision is not final, so the status can change. And asking again will not help, because the request is not what is missing.

This is the point where people confuse it with its neighbour. “Discovered, currently not indexed” means Google knows about the URL but has not fetched it yet, which is a scheduling issue. I cover that separately in my guide to discovered, currently not indexed. If the status says crawled, the fetch already happened, and the question is why the page was not judged worth keeping.

Decide first: does this page deserve to be indexed?

Before you fix anything, sort the affected URLs into two piles. This single step saves more time than any technical tweak.

If your report is full of the second pile, you have a site hygiene issue rather than a content issue, and finding and removing low-value index bloat is the better route. For the broader picture of how the statuses fit together, see my explanation of the Search Console coverage report.

The usual causes, and how to tell them apart

Google does not give a reason code for this status, so you infer the cause from the page itself. These are the patterns I see most often when I audit a site.

Cause What it looks like First check
Thin content A few lines of text, a heading and a form; nothing a searcher could not find elsewhere Read the page as a stranger. Would you bookmark it?
Duplicate or near-duplicate content Many pages that differ only by a city name, product colour or one sentence Compare the main text of three affected pages side by side
Another canonical chosen Google treats a different URL as the main version Look at the Google-selected canonical in URL Inspection
Weak internal links The page is only reachable from a sitemap or a deep pagination link Count the contextual links pointing to it from important pages
Soft 404 behaviour An empty category or a “no results” page returning a normal status Check whether the page has real content and a correct status code
Low site-level trust or quality Large parts of the site are shallow, so new pages get less benefit of the doubt Review a sample of recently published pages for usefulness
Very new page Published days ago, with little linking to it yet Wait, and make sure it is linked from a relevant page

Two of those deserve a note. On duplicate pages, Google’s own documentation explains that it picks the page it considers the most complete and useful version as the canonical, and that a canonical tag from you is a hint, not a rule. So a near-copy can be crawled and then quietly dropped. On soft 404s, an empty page with a 200 status looks like content to a server but like nothing to Google; my guide to soft 404 errors covers the detail.

Diagnose a sample with the URL Inspection tool

Do not try to diagnose hundreds of URLs one at a time. Group them by template or folder, pick three to five from each group, and inspect those. The URL Inspection tool guide explains each field; for this problem, the sequence below is what matters.

  1. Inspect the URL and read the indexing status. Confirm it says the page is not on Google and note the last crawl date. A crawl date from months ago suggests Google has not found the page worth revisiting.
  2. Compare the user-declared canonical with the Google-selected canonical. If Google chose a different URL, you have a duplication problem, not a quality problem. Fix the duplication.
  3. Check how it was discovered. The tool shows referring sitemaps and, where available, referring pages. A URL with no referring pages except a sitemap is probably under-linked.
  4. Open the crawled page view. Look at the rendered HTML and confirm the main content is actually there. If your content loads only after a script runs and the render is empty, Google may have seen a hollow page.
  5. Run a live test. This shows whether the page as it stands today can be fetched and rendered. It does not tell you whether Google will index it, but it confirms a fix has taken effect before you ask for a recrawl.

Google is clear that the tool’s result is a technical check only. As the URL Inspection help page notes, it does not test quality guidelines, so a clean inspection on a weak page proves nothing about its value.

A fix workflow for pages that matter

Once you know which pages deserve to be indexed and have a likely cause, choose one action per group.

  1. Improve the page. Add what is missing: specific detail, original examples, clear answers, real photographs or data, author information where relevant. The question to answer is “what does this page give a searcher that the existing results do not?”
  2. Consolidate near-duplicates. If twelve pages say almost the same thing, merge them into one strong page and redirect the others. One useful page beats twelve thin ones.
  3. Strengthen internal links. Link to the page from related, already-indexed pages with descriptive anchor text, and include it in your main navigation or hub pages if it is commercially important. Internal links tell Google the page matters to you.
  4. Fix technical signals. Make sure the page returns the right status code, has a self-referencing canonical, is not blocked, and does not rely on a script to show its main content.
  5. Decide to exclude. For genuinely low-value pages, use noindex or remove them, and take them out of your sitemap. A clean sitemap should list only URLs you want indexed.

An illustrative example

Imagine a Karachi tile supplier with a page for every neighbourhood it delivers to, each containing the same two paragraphs and the neighbourhood name swapped in. Most of those pages end up crawled but not indexed. A sensible fix is to keep a single well-developed delivery-areas page, add real information about delivery times and showroom pickup, and fold the near-identical pages into it. This is an invented scenario to show the logic, not a client result.

What not to do

Validating the fix and watching the result

After making improvements, you can use the validation option in the Page indexing report. Google says validation typically takes up to about two weeks, though it can take much longer, and that only URLs with known instances of the issue are rechecked. Validation ends if Google still finds an instance of the problem, so group your fixes and validate when the whole batch is ready.

Then track the result rather than waiting for a green tick. Check, a few weeks later, whether the improved pages have moved out of the status, and whether they begin to show impressions in the Search Console performance report. If nothing changes after a real improvement, the page may still be too similar to what already ranks, and the next step is more differentiation, not more requests.

Indexing review is one part of what a professional SEO audit includes. When I run one, I rank these findings by commercial importance rather than by URL count, which is the approach in my guide to prioritising SEO audit findings. Fifty unindexed tag pages matter far less than one unindexed service page.

Questions people ask about crawled, currently not indexed

Is “crawled, currently not indexed” a penalty?

No. It is a status describing a decision about one URL, not a manual action or a site-wide penalty. A large share of affected pages can point to a wider quality problem, but the status itself is not a punishment.

How long does it take to move out of this status?

There is no fixed time. Google says the page may or may not be indexed in the future. Improve it, link to it well, and give Google time to recrawl; after that, judge by the result rather than the calendar.

Will adding a page to the sitemap fix it?

Not by itself. A sitemap helps discovery, and Google has already discovered and crawled this page. What it needs is a reason to be indexed: better content, stronger internal links or a clearer canonical.

What is the difference between this and “discovered, currently not indexed”?

Crawled means Google fetched the page and decided not to index it. Discovered means Google knows the URL but has not fetched it. The first is mostly about page value; the second is mostly about crawl scheduling.

If you have a long list of unindexed pages and cannot tell which ones matter, my SEO audit services include an indexing review that sorts them by priority. You are welcome to request a free audit and I will tell you where to start.

More in this series (SEO measurement and Search Console): start with What a Professional SEO Audit Includes (and Red Flags), then explore:

Exit mobile version