Discovered or Crawled—Currently Not Indexed: Which Should You Fix First?

If Search Console shows both Discovered - currently not indexed and Crawled - currently not indexed, do not treat them as one backlog. Discovered means Google found the URL but has not crawled it yet—often after rescheduling to avoid overloading the site. Crawled means Google already fetched the page and chose not to index it. Fix discovery and crawl-capacity problems before you spend weeks rewriting pages Google has not even fetched; fix content quality and duplicate signals when important URLs are already crawled but still excluded.

Key takeaways

• Discovered and Crawled are different stages. Mixing them leads teams to request indexing, rewrite copy, or rebuild templates for the wrong failure.

• Google does not guarantee that every crawled page will be indexed, and it does not promise crawl timing even when a URL is known.

• Prioritize Discovered when revenue pages have empty last-crawl dates and host availability or URL inventory is congested.

• Prioritize Crawled when Google already fetches the URL but still declines indexing—then inspect usefulness, duplicates, and whether the page should exist at all.

• Use the Indexing Stage Ladder below, then score the situation with the Stage Fit Scorecard before changing templates or expanding content production.

What each Search Console status actually means

Google Search works in stages: discovery, crawling, indexing, and serving. Not every URL makes it through each stage. The Page indexing report separates reasons for non-indexed URLs so you can see where the process stopped.

Discovered - currently not indexed

According to Google's Page indexing documentation, this status means the page was found, but not crawled yet. Typically, Google wanted to crawl the URL but expected the crawl to overload the site, so it rescheduled. That is why the last crawl date is empty in the report.

For a business site, this status is mainly a discovery-and-capacity problem. Google knows the URL exists—from a sitemap, internal links, or another source—but has not yet spent crawl resources to fetch it.

Crawled - currently not indexed

This status means Google crawled the page and did not index it. Google states that it does not index every page across the web, so the message is common and does not automatically mean something is broken. For important pages, Google recommends using the URL Inspection tool and related diagnostics to check for issues that prevent the page from appearing.

For a business site, this status is mainly a selection-and-quality problem after fetch. Google already spent crawl budget on the URL. Requesting crawl again without changing the page usually does not solve the underlying decision.

Why the distinction matters for growth teams

Many teams open Page indexing, see a large gray total, and assume the site has an indexing crisis. Google's own guidance for smaller sites is more restrained: you do not need every URL indexed—only the canonical versions of important pages. Duplicates, removed pages, intentionally blocked URLs, and low-value parameter variants can remain not indexed for legitimate reasons.

The practical risk is misallocated work. If the real bottleneck is crawl capacity and URL inventory, rewriting product descriptions will not move the needle. If Google already crawls your money pages and still leaves them out, buying more sitemap submissions will not either. This is where disciplined search engine optimization services diagnosis pays off: stage identification before tactics.

The Indexing Stage Ladder

Use this ladder when both statuses appear. Climb only as far as the evidence requires. Do not jump to content rewrites while L0 through L2 still fail for the URLs that matter.

1. L0 — Confirm importance and canonicity. List the 20–50 URLs that should earn organic demand: homepage, category hubs, top products or services, key location pages, and cornerstone guides. Confirm each should be the canonical version. Ignore low-value filters, cart states, and expired campaign landing pages unless they are still linked publicly.

2. L1 — Split the backlog by stage. Export or sample Discovered URLs and Crawled URLs separately. For each important URL, note whether Search Console shows an empty last crawl date (Discovered) or a completed crawl without indexing (Crawled). Do not average the two buckets into one KPI.

3. L2 — Clear discovery and crawl friction first when Discovered dominates money pages. Check Crawl Stats host availability, server errors, long redirect chains, soft 404 clusters, accidental robots.txt blocks, and sitemap hygiene. Google's large-site crawl guidance treats a large Discovered share as a signal to manage crawl capacity and URL inventory. Even mid-size catalogs can hit the same pattern after a migration, faceted navigation expansion, or parameter explosion.

4. L3 — Diagnose Crawled exclusions as selection decisions. For important Crawled URLs, use URL Inspection to review indexing status, canonical choice, crawl allowed, and page fetch. Ask whether the page is thin, overlapping, outdated, blocked by metadata, or simply not useful enough relative to stronger pages. Fix the page or consolidate it; do not treat crawl requests as a ranking lever.

5. L4 — Run one intervention queue for 30 days. Choose a single primary workstream: inventory-and-crawl cleanup or page-quality consolidation. Measure progress by important-URL movement in URL Inspection and by indexed count for the money set—not by total not-indexed volume across the whole property.

Stage Fit Scorecard

Score each row from 0 to 2. A high Discovered-fit score means crawl and inventory work should lead. A high Crawled-fit score means selection and usefulness work should lead. If both scores are high, sequence Discovered cleanup for the money set first, then move to Crawled rewrites so you are not improving pages Google still cannot fetch efficiently.

Worked example: a mid-size ecommerce catalog

Hypothetical example: a 12,000-URL catalog brand sees 3,400 Discovered URLs and 2,100 Crawled URLs in Page indexing. Leadership asks for a content sprint because "Google is not indexing us."

When the team samples the top 40 category and product URLs, 18 Discovered money pages have no last crawl date. Crawl Stats shows repeated host availability pressure during peak hours. Faceted filter combinations are linked in the footer and also appear in an outdated sitemap. Meanwhile, several blog posts and old campaign pages sit in Crawled - currently not indexed.

Under the Indexing Stage Ladder, the first 30-day queue is Discovered-first: remove facet URLs from the sitemap, block low-value filter crawl paths where appropriate, strengthen internal links from category hubs to priority products, and raise serving capacity during Googlebot peaks. The Crawled blog and campaign leftovers wait until the money-page crawl gap closes. Only then does the team consolidate overlapping guides that Google already fetches but still declines to index.

If the same catalog had stable crawl health, clean sitemaps, and every priority product already crawled weekly—but still not indexed—the scorecard would flip. The intervention would become template usefulness, unique copy, and consolidation rather than crawl inventory theater.

Common failure patterns

• Treating total not-indexed count as the KPI. Google does not expect 100% coverage. Obsessing over the gray total encourages bad incentives, including indexing pages that should stay out.

• Spamming URL Inspection requests. Google notes a quota for individual requests and says requesting the same URL repeatedly will not get it crawled faster. Requests also do not guarantee inclusion.

• Rewriting pages Google has not crawled. Content quality cannot be evaluated until fetch happens. Discovered-heavy money pages need discovery and capacity work first.

• Leaving soft 404 and redirect waste untouched. Soft 404s and long redirect chains consume crawl attention. Pair this article with Oasbit's soft 404 triage guidance when those statuses appear alongside Discovered volume.

• Confusing intentional exclusion with failure. Robots rules, noindex, and true 404s can be correct outcomes. Use robots.txt, noindex, and 404 decisions when the question is whether a page should be crawlable or indexable at all.

Limitations and when this advice does not apply

• Brand-new sites can take days before meaningful crawl and index activity appears. Early Discovered counts alone are not proof of a structural crawl-budget crisis.

• Google's detailed crawl-budget guide is written primarily for large, frequently updated sites. Smaller sites should still separate Discovered from Crawled, but they should not over-engineer crawl-budget programs.

• Site-wide indexing bugs are rare. Google provides an indexing-issue reporting path only after you have fully diagnosed potential site issues.

• Indexed status still does not guarantee visibility for every query. Serving depends on relevance and many other factors beyond indexing stage triage.

• This framework does not replace investigation of hard errors such as 5xx responses, robots blocks on money pages, or canonical conflicts already covered in separate Oasbit articles.

Recommended next steps

1. Build your money-page list and verify each intended canonical with URL Inspection.

2. Split current not-indexed examples into Discovered versus Crawled, then complete the Stage Fit Scorecard.

3. If Discovered leads, clean URL inventory, restore availability, and improve discovery signals before launching a rewrite program.

4. If Crawled leads, inspect usefulness and overlap, then improve, merge, or intentionally accept non-indexing for low-value URLs.

5. Reassess after one focused 30-day queue. Change only one primary lever at a time so you can interpret the result.

If your team is stuck arguing about sitemap submissions while revenue pages sit in the wrong indexing stage, book a growth strategy session. Oasbit can help separate crawl capacity issues from selection problems and turn the Page indexing report into a prioritized work plan.

Sources

• Page indexing report — Google Search Console Help (Discovered and Crawled definitions)

• In-depth guide to how Google Search works — Google Search Central

• Large site owner's guide to managing your crawl budget — Google Search Central

• Ask Google to recrawl your URLs — Google Search Central

• URL Inspection tool — Google Search Console Help

• Crawl Stats report — Google Search Console Help