“Crawled, currently not indexed” means Googlebot fetched the URL but Google chose not to add it to the index. That is often a quality, duplication, demand or site-structure signal, not automatically a technical error. This guide does not guarantee indexing; it helps you diagnose which author-defined cause fits your URL and what to fix next.

What you will learn

  • What the Search Console status means and when it matters.
  • How to separate crawled-not-indexed URLs from discovered-not-indexed URLs, noindex exclusions, canonicalized pages and deindexing.
  • How to use a 9-cause author-defined diagnosis matrix without treating it as an official Google list.
  • How to check Page Indexing and URL Inspection evidence without making up Search Console data.
  • When request indexing is useful and when it is just a distraction.

What “Crawled, currently not indexed” actually means

The status means Google has fetched the URL, but the URL is not currently in the index. It does not, by itself, prove a penalty, a crawl budget crisis or a broken plugin. The practical question is narrower: should this specific URL be indexed, and if yes, what signal is preventing it from being a strong index candidate?

Google’s own crawling and indexing documentation separates discovery, crawling, indexing and serving. A page can be discovered and crawled without being selected for indexing. That is why this status needs diagnosis before action.

First: is this status actually a problem?

It is a problem when the affected URL is meant to rank, serve users or support a business path. It may not be a problem when the URL is a weak tag archive, an internal search page, a duplicate parameter URL, an expired thin product page or a page that should be consolidated into a stronger resource.

Before fixing anything, classify the URL: keep and improve, merge, noindex, canonicalize, redirect, remove from sitemap or leave alone with documented reason.

Crawled not indexed vs discovered not indexed vs deindexed

These statuses need different responses. Crawled but not indexed means Google reached the page. Discovered but not indexed means Google knows about the URL but has not fetched it yet. Deindexing means a page that had been indexed later lost that indexed state.

Status What it means Typical cause First check When to escalate
Crawled, currently not indexed Google fetched the URL but did not add it to the index Quality, duplication, weak signals or low-value URL URL Inspection plus content review When important URLs remain affected after diagnosis
Discovered, currently not indexed Google knows the URL but has not crawled it yet Priority, crawl path or site capacity issue Sitemap and internal links When important URLs stay uncrawled across a pattern
Alternate page with proper canonical Google found another URL as the preferred version Duplicate or canonical consolidation Selected canonical When the selected canonical is wrong
Excluded by noindex A noindex directive tells Google not to index Intentional or accidental noindex HTML/meta and HTTP headers When noindex is accidental
Not found / soft 404 The page is missing or appears empty despite loading Deleted, expired, empty or thin template Rendered page and status behavior When valuable URLs should exist but return weak output
Indexed, then lost The URL used to be indexed but is no longer visible as indexed Deindexing, canonical shift, noindex, quality or consolidation Historic state plus current URL Inspection Use the deindexing guide instead

If the page used to be indexed and later disappeared, use the deindexing diagnostic flowchart instead. If the issue is WordPress archive bloat or plugin output, the WordPress SEO guide is the better supporting read.

The 9 author-defined causes, ranked by diagnosis priority

These 9 causes are my diagnostic buckets, not Google’s official list and not the only possible explanations. They are ranked by the order I usually check them in an indexing audit because they separate content, duplication, internal linking, canonical signals and site-wide patterns quickly.

Cause Symptom in GSC / site review How to diagnose What to fix What to watch next
Thin or low-value content The URL was crawled, but the page says little that is useful beyond a title, a short paragraph or repeated boilerplate. Compare the page against the query intent, inspect the rendered content and check whether the page has a distinct job. Rewrite, expand or merge the page so it answers a real need; noindex or retire it if it has no useful role. Watch whether the page earns internal links and whether Search Console starts showing a clearer indexing state.
Duplicate or near-duplicate content Several URLs cover the same intent with similar copy, titles or templates. Search your own site for the title, opening paragraph and URL pattern; inspect selected canonical hints where available. Consolidate duplicates, strengthen the preferred URL and remove or noindex redundant variants. Watch canonical consistency, sitemap inclusion and internal links to the preferred page.
Internal link starvation / orphan-like URL The page exists in the sitemap or CMS but is barely linked from relevant pages. Review navigation, hub pages, related posts and crawl paths; check whether a user can naturally reach the URL. Add contextual internal links from relevant hubs, categories and supporting articles. Watch whether crawl discovery and URL Inspection signals become more consistent.
Weak search intent match or unclear page purpose The page targets a query but does not clearly solve the searcher problem. Read the page title, H1, intro and section order against the query; look for mixed intent or vague promise. Refocus the page around one primary job, restructure headings and remove unrelated sections. Watch engagement signals you can measure internally and whether the page receives better internal support.
Crawl-then-quality-filter behavior Google can fetch the URL, but the page still appears excluded after crawl. Rule out technical blocks first, then review content usefulness, duplication and site role. Improve the page only if it deserves to exist; otherwise consolidate, noindex or leave it out of the index intentionally. Watch for repeated patterns across similar templates, not one isolated URL only.
Canonical or duplicate URL pattern confusion Declared canonical, selected canonical, sitemap URL and internal links do not reinforce the same version. Use URL Inspection and rendered HTML checks to compare canonical signals and URL variants. Align canonical tags, internal links, sitemap entries and redirects around the preferred URL. Watch whether Google keeps choosing a different canonical candidate.
Archive, tag, parameter, or faceted URL bloat Many low-value archive or filter URLs compete with useful pages. Sample category, tag, search, parameter and faceted URLs; check whether they provide unique value. Noindex, canonicalize, block crawl paths carefully or consolidate based on the URL type and user value. Watch sitemap cleanliness and whether internal links stop reinforcing low-value URLs.
Soft 404, empty template, or thin template page The URL returns a normal page but looks empty, broken, expired or not useful to a user. Render the page, check template data, product availability, category contents and main content output. Return a proper status, fill the template with useful content, redirect if appropriate or remove the URL from index targets. Watch recurring template issues after product, category or CMS changes.
Site-wide quality or trust pattern Many similar pages across the site are crawled but skipped, even when individual pages look technically accessible. Group affected URLs by template, content type, author, category and internal-link path. Improve the weak template family, prune low-value pages, strengthen authorship and internal architecture. Watch the pattern at template level before judging individual URLs.

Pages stuck out of the index? Book a technical audit and I will identify which of these 9 diagnostic buckets fits your URLs, with evidence from your setup.

Cause-by-cause diagnosis and fixes

Thin or low-value content

Symptom: the URL loads, but the main content does not give Google or users a strong reason to keep the page as a separate index result. Diagnosis: compare the page to the query intent and inspect the rendered content, not only the editor draft. Fix: improve the page into a useful standalone answer, merge it into a stronger page or noindex it if it has no search role.

Duplicate or near-duplicate content

Symptom: multiple URLs say nearly the same thing. Diagnosis: compare titles, introductions, headings, body copy and template output across similar URLs. Fix: consolidate duplicates, strengthen the preferred URL and align internal links and sitemap entries around that URL.

Symptom: the page exists but has little meaningful support from the rest of the site. Diagnosis: check whether users and crawlers can reach it through relevant hubs, categories, navigation or contextual links. Fix: add internal links from pages that already have topical relevance, not random footer links.

Weak search intent match or unclear page purpose

Symptom: the page appears to target a query but does not clearly answer it. Diagnosis: read the title, H1, introduction and section order against the searcher’s problem. Fix: refocus the page around one primary task, move unrelated sections elsewhere and make the answer visible early.

Crawl-then-quality-filter behavior

Symptom: technical access looks fine, but the URL is still skipped after crawl. Diagnosis: rule out noindex, robots.txt, canonical and template issues first, then review usefulness and duplication. Fix: improve only pages that deserve indexation; consolidate or noindex pages that should not compete.

Canonical or duplicate URL pattern confusion

Symptom: the inspected URL and Google’s preferred URL do not line up. Diagnosis: compare declared canonical, selected canonical hints, sitemap URL, internal links and redirects. Fix: make all signals reinforce the intended URL.

Archive, tag, parameter, or faceted URL bloat

Symptom: many low-value generated URLs appear in Page Indexing groups. Diagnosis: sample tag, archive, parameter and faceted URLs to see whether they have unique value. Fix: noindex, canonicalize, consolidate or control crawl paths based on the URL type.

Soft 404, empty template, or thin template page

Symptom: the URL returns a normal response but looks empty, expired, broken or too thin to satisfy a user. Diagnosis: render the page and review CMS data, product/category state and template output. Fix: return the right status, fill the page with useful content, redirect it or remove it from index targets.

Site-wide quality or trust pattern

Symptom: many similar pages across a template family are crawled but not indexed. Diagnosis: group affected URLs by content type, author, category, template and internal-link path. Fix: improve the template family, prune weak pages, strengthen internal architecture and document what should be indexed.

How to check the issue in Google Search Console

Use Search Console as evidence, not as a magic fix button. The Page Indexing report helps you see patterns. URL Inspection helps you inspect one URL deeply. Neither replaces reviewing the page, template, internal links and canonical signals yourself.

Step Where to check What to look for What it usually means Next action
Page Indexing report Search Console > Indexing > Pages Excluded URLs grouped by status A pattern may exist across templates or URL types Export or sample URLs and group them by template
URL Inspection Inspect the exact URL Crawl, indexability, canonical and sitemap hints The individual URL may differ from the group pattern Save the evidence before changing the page
Canonical status URL Inspection and page source Declared canonical vs Google-selected canonical clues Google may prefer another URL Align canonical, internal links and sitemap signals
Sitemap and internal links Sitemap, navigation, hub pages and crawl paths Whether the preferred URL is included and linked Weak discovery can reinforce low priority Add relevant links or remove URL from sitemap if it should not index
Content duplication check Site search, crawl export or manual comparison Near-duplicate copy, title or template intent Google may have enough similar pages Merge, rewrite or consolidate competing URLs
Internal link review Relevant hubs, categories and related articles Whether the page is supported by meaningful links The page may be orphan-like Add contextual links from pages that already have topical relevance
Request indexing decision URL Inspection after the fix Whether the page is fixed and worth resubmitting Requesting indexing is a prompt, not a guarantee Use it after meaningful changes, not as the only fix
Escalation to audit Grouped evidence from GSC and site review Repeated patterns across many URLs The issue may be structural or template-level Run a technical/indexing audit with evidence

When requesting indexing helps, and when it does not

Request indexing can be useful after a meaningful fix: the page was accidentally noindexed, the canonical was corrected, the content was substantially improved or internal links were added. It is weak as a standalone tactic. If the page is still thin, duplicated, unsupported or confusing, requesting indexing does not make it a better index candidate.

When waiting is reasonable

Waiting is reasonable when the URL is new, technically accessible, internally linked, included appropriately in the sitemap and clearly useful. Waiting is not a strategy when the same template, archive type or duplicate pattern keeps appearing across many URLs. In that case, document the pattern and fix the underlying cause.

How this differs from deindexing

Crawled, currently not indexed is about a URL Google fetched but did not add to the index. Deindexing is about a URL that was indexed and later lost that indexed state. The evidence differs: for deindexing, you need historic indexed status and current loss; for crawled-not-indexed, you need to prove the URL deserves indexation after crawl.

Wrong article: deindexing vs never indexed

If the page used to receive indexed impressions or was clearly indexed before, use a deindexing workflow. If the page was crawled but never selected for the index, stay with this diagnosis.

Common mistakes to avoid

  • Treating the status as a penalty without evidence.
  • Pressing request indexing before fixing the page.
  • Deleting every unindexed URL without checking its role.
  • Blaming crawl budget before checking content, duplication and internal links.
  • Assuming schema or Core Web Vitals alone will solve indexation.
  • Ignoring canonical and duplicate URL patterns.
  • Looking at one URL when the real problem is a template family.

Final recommendation

Start with intent and usefulness, then duplication, internal links, canonical signals and generated URL bloat. If only one low-value page is affected, the fix may be simple. If many important URLs are affected, treat it as an indexing audit: group the URLs, collect GSC evidence and fix the pattern rather than repeatedly requesting indexing.

Pages stuck out of the index? Book a technical audit and I will identify which of these 9 diagnostic buckets fits your URLs, with evidence from your setup.

FAQ

What does “Crawled, currently not indexed” mean?

It means Googlebot fetched the URL, but Google did not add it to the index at that point. The next step is diagnosis, not assuming a penalty or pressing request indexing repeatedly.

Is “Crawled, currently not indexed” a penalty?

Not by itself. It can happen for quality, duplication, canonical, internal linking, generated URL or site-structure reasons. Check Search Console evidence before using penalty language.

How long does it take Google to index a fixed page?

There is no safe universal timeline. After a meaningful fix, monitor URL Inspection, Page Indexing patterns, sitemap inclusion and internal links instead of promising a fixed indexing window.

Does requesting indexing solve this status?

Request indexing can help Google revisit a fixed URL, but it does not guarantee indexing. Use it after the page has a stronger reason to be indexed.

Should I delete pages that are crawled but not indexed?

Not automatically. Some pages should be improved, some merged, some noindexed, some redirected and some left alone. Decide based on the page’s role and evidence.

What is the difference between crawled not indexed and discovered not indexed?

Crawled not indexed means Google fetched the URL. Discovered not indexed means Google knows the URL exists but has not crawled it yet. The first points more often to page selection; the second can point to discovery, priority or crawl path.

How is this different from deindexing?

Deindexing means a page was indexed before and later lost that indexed state. Crawled currently not indexed means Google fetched the page but did not add it to the index.

Source notes

This guide is grounded in Google Search Central documentation for crawling and indexing, Search Essentials, sitemap guidance, robots.txt guidance, URL Inspection, Page Indexing concepts and structured data limitations. The 9-cause framework is an author-defined diagnostic taxonomy, not an official Google list.