Discovered vs Crawled Currently Not Indexed: Difference
August 17, 2026 · By BestIndexingTool Team
Discovered - currently not indexed means Google knows a URL exists but has not yet crawled it enough to index it. Crawled - currently not indexed means Google already fetched the URL and still chose not to put it in the index. Same end state (not indexed), different stage in the pipeline, different first fixes.
If you mix these statuses up, you will waste time rewriting content when the real issue is crawl priority, or you will keep "building links for crawl" when Google already crawled a thin page and rejected it.
What does each Search Console status mean?
Think of Google's path as discover, crawl, evaluate, index. These two report labels pin failure at different steps.
| Signal | Discovered - currently not indexed | Crawled - currently not indexed |
|---|---|---|
| Does Google know the URL? | Yes | Yes |
| Did Googlebot fetch the page? | Not yet in a way that completed indexing evaluation (or crawl was deferred) | Yes |
| Primary bottleneck | Crawl scheduling, access, or priority | Index selection after evaluation |
| Typical first fixes | Internal links, sitemap hygiene, host health, remove crawl traps | Content quality, duplication, usefulness, canonical clarity |
| Resubmission alone | Sometimes helps important URLs get crawled sooner | Weak without page improvements |
| Common in | Large sites, new URLs, weak IA, budget strain | Thin templates, duplicates, low-value pages |
Why does Discovered currently not indexed happen?
Google discovered the URL through a sitemap, links, or other signals, then delayed or skipped crawl. Reasons often include:
- Low perceived importance versus other URLs on the site
- Huge inventories where crawl capacity is stretched
- New domains or sections with limited demand history
- Crawl traps and low-value URL explosions stealing attention
- Server reliability problems that make crawling inefficient
- Weak internal linking so the URL looks peripheral
Important nuance: "Discovered" does not always mean Google never tried. It means you do not yet have a successful crawl-to-index outcome recorded the way the Crawled bucket does. Operationally, still treat it as a crawl-priority problem first.
Why does Crawled currently not indexed happen?
Here Google already spent crawl resources. The page was seen and still failed selection. Typical causes:
- Thin or unoriginal content
- Near-duplicates and cannibalization
- Soft 404 style emptiness
- Stronger alternate URL chosen instead
- Site-wide quality issues
- Pages that are crawlable but not helpful for searchers
This is why "just get more crawl" is the wrong default for the Crawled bucket. Google already arrived.
How should your fix strategy differ?
Match medicine to diagnosis.
If the URL is Discovered - currently not indexed
- Confirm the URL is allowed and reachable (robots, status codes, canonical target).
- Add strong internal links from relevant indexed pages.
- Include only index-worthy URLs in sitemaps; remove junk.
- Reduce low-value URL bloat that competes for crawl.
- Improve site performance and server stability if crawl errors are common.
- Request indexing selectively for business-critical new URLs.
- Earn or place quality links when the page is on a third-party host and stuck undiscovered by crawlers in practice.
If the URL is Crawled - currently not indexed
- Audit uniqueness versus indexed peers.
- Upgrade content depth and clarity.
- Consolidate duplicates.
- Fix soft 404 and boilerplate templates.
- Align canonicals and hreflang clusters.
- Then request recrawl after substantive changes.
- Recheck on a multi-day schedule rather than hourly refreshes.
Can the same site show both statuses at once?
Yes, and that pattern is informative. If product detail pages are crawled-not-indexed while faceted filter URLs are discovered-not-indexed, you likely have a quality problem on PDPs and a crawl-bloat problem on facets. Fix templates with data, not with one global myth.
Segment your exports:
- By status bucket
- By template
- By revenue importance
- By owned site versus third-party backlink host
How do backlink campaigns interpret these statuses?
For SEOs buying or earning links, both statuses mean the linking URL is not helping search visibility yet.
- Discovered not indexed on a host page: the web knows the URL exists in some graph sense, but crawl priority on that host is weak. Host authority, internal links on the publisher site, and site health matter.
- Crawled not indexed on a host page: Google saw the page and declined it. Thin guest posts and low-quality directories often land here.
Before you scale a vendor, sample-check indexation of placements. BestIndexingTool provides a forever-free index checker without requiring Google Search Console on domains you do not control. For batch follow-up, use campaigns, drip-feed from 1 to 14 days, standard (1 credit) or priority (3 credits) submissions, API access, and pay as you go packs from $19 with credits that never expire. Signup includes a one-time 3-credit trial. Credits are final purchases without auto-refunds for URLs Google still rejects.
What metrics should teams report to stakeholders?
Avoid vanity charts. Report:
- Count of URLs in each non-indexed bucket by template
- Percent of money pages indexed
- Change after specific fixes (content sprint vs IA sprint)
- Backlink placements indexed versus merely "live in browser"
- Time-to-index ranges without fake guarantees
Stakeholders understand "Google crawled 400 thin tag pages and refused them" better than "we submitted 400 times."
"Discovered vs crawled is a pipeline question. If you apply a content rewrite to a crawl-priority problem, or a crawl spam blast to a quality rejection, you will burn weeks. Read the label, then pick the lever." (BestIndexingTool Team guidance)
Quick decision tree
- Is the URL blocked or non-200? Fix access first.
- Is the status Discovered not indexed? Improve crawl priority and reduce bloat.
- Is the status Crawled not indexed? Improve usefulness and reduce duplication.
- Is the URL low value by design? Consider noindex or removal instead of rescue.
- After changes, recheck with Search Console and an independent index check tool.
FAQ
What is the main difference between Discovered and Crawled not indexed?
Discovered means Google knows the URL but has not crawled it yet (or has not successfully crawled it into evaluation). Crawled means Google fetched it and still did not index it.
Which status is worse?
Neither is automatically worse. Discovered often points to crawl priority or access issues. Crawled often points to quality or duplication after evaluation.
Can a URL move from Discovered to Crawled not indexed?
Yes. Google may later crawl a previously only-discovered URL and still choose not to index it.
Do sitemaps fix Discovered currently not indexed?
Sitemaps help discovery and recrawl hints, but Google still prioritizes what to crawl and index based on demand and quality signals.
Should I request indexing for both statuses?
You can request attention for important URLs, but pair requests with crawl access fixes for Discovered and content quality fixes for Crawled.
Does this apply to backlinks too?
Yes. Third-party pages can be discovered or crawled without being indexed. Always verify host page status before scaling link buys.
Next steps: crawled currently not indexed causes, fix checklist, fast URL indexing, pricing, for agencies, signup, docs, alternatives, BestIndexingTool home.
Updated August 2026