Google Search Console’s Pages report often shows two confusing statuses. These are “Discovered – currently not indexed” and “Crawled – currently not indexed.” They sound similar but represent fundamentally different situations. Each requires different urgency levels and unique fixes.
“Discovered” means Google knows your page exists but has not visited it. This usually indicates a queue issue, not a quality problem. “Crawled” means Google visited your page and evaluated its content. Then, Google actively decided to exclude it from the index. This points to a specific quality or technical issue.
You must understand which status you face before applying fixes. Using “Discovered” fixes on a “Crawled” problem wastes time and delays your solution. This guide explains the exact mechanisms behind both statuses. We will explore the 5-step Crawl Framework to diagnose indexing failures. Finally, we cover specific fixes and how to properly request indexing. If you want to compare your GSC data with other SEO practitioners, join Scale Xpert’s Discord community. It is an active hub for SEO learning and genuine backlink exchange.
The Fundamental Difference Between the Two Statuses
The main difference between these statuses involves your page’s exact location in Google’s pipeline. It shows exactly where the page stopped making progress.
What “Discovered” Really Means
“Discovered – currently not indexed” means Google identified the URL. Google typically finds URLs through sitemaps, internal links, or external backlinks. The system placed the URL in the crawl queue. However, Googlebot has not visited the page yet. The page exists in Google’s awareness, but not in its inspection history.
This status usually resolves itself. Google will eventually crawl the page and change its status. Alternatively, the page might sit in the queue for months if Google assigns it a low priority.
Google bases this crawl priority on the page’s perceived importance. Pages on high-authority domains with strong internal links crawl quickly. Pages on low-authority domains with weak links sit in the queue longer. In 2026, Google selects URLs much more carefully. Crawler budget strongly favors pages demonstrating high quality through domain-level signals.
What “Crawled” Really Means
“Crawled – currently not indexed” tells a different story. Google visited the page and loaded its content. It evaluated the HTML and rendered any JavaScript. After this review, Google actively chose to exclude the page from search results.
This is never a timing issue. It represents a deliberate quality or technical judgment. The page simply failed Google’s inclusion standards. Leaving the page unchanged guarantees the exact same outcome during future crawls. Google will evaluate it again and reject it again.
This distinction completely dictates your response. A “Discovered” page often just needs time. You might only need a manual indexing request after verifying technical health. A “Crawled” page requires major content improvements before you even think about requesting indexation.
The 5-Step Crawl Framework for Diagnosing Indexing Failures
A systematic diagnostic approach saves you from wasting effort on the wrong fixes. The Crawl Framework gives you this systematic process across five sequential checks.
Step 1: Check Connection
First, verify that Googlebot can physically access your servers. Check your robots.txt file at yourdomain.com/robots.txt. Ensure it lacks “Disallow” rules blocking Googlebot from the affected pages. Review your CDN and WAF configurations. You must confirm you are not blocking Googlebot’s IP addresses.
Next, check your server error rate in Google Search Console. Go to Settings, then Crawl Stats. Frequent 500, 502, or 503 errors prevent Googlebot from completing page evaluations. A failing server traps pages in the “Discovered” queue because Googlebot abandons the crawl early.
Step 2: Confirm Recognition
Confirm Google knows the affected pages exist through strong discovery signals. A properly configured XML sitemap provides the most reliable discovery signal. Submit this sitemap directly to Google Search Console.
Check that your sitemap includes the affected pages. Exclude low-value URLs like tag archives or author pages. Update the sitemap instantly when you publish new pages. Pages lacking sitemap entries and relying solely on deep internal links suffer weak discovery signals. They sit in the “Discovered” queue the longest.
Step 3: Verify Access
Confirm you lack technical signals telling Google to ignore the page. Use the URL Inspection tool on every affected page. Check the Coverage tab for any noindex tags. Ensure the listed canonical URL matches the page’s actual URL.
Look for any redirect detection indicating the URL resolves unexpectedly. A page with a noindex tag excludes itself by design. A page with a canonical pointing elsewhere intentionally consolidates itself with another URL.
Step 4: Evaluate Worth
Assess whether your page’s content quality meets current indexation standards. Google acts ruthlessly regarding indexation today. It rejects thin, duplicative, or low-value content even when technically perfect.
If a page shows “Crawled – currently not indexed” without technical issues, you face a content problem. Common issues include thin content under 300 words. Duplicative text matching internal or external pages also fails. Auto-generated content lacking original value triggers this status constantly.
Step 5: Review Linked Architecture
Assess the internal links pointing to your affected pages. Orphaned pages lack internal links from indexed pages. They receive much weaker crawl signals than well-linked pages.
Google uses internal link architecture to gauge page importance. Add three to five contextual internal links from relevant, indexed pages. This increases apparent importance and often resolves “Discovered” status. This fixes crawl prioritization, not content quality.
Read our guide on what Google Search Console is and how to use it to master these diagnostic tools.
Fixing “Discovered – Currently Not Indexed”
The right fixes for “Discovered” status target Steps 1, 2, and 5 of the Crawl Framework. You must ensure Google can access your site, knows the pages exist, and wants to crawl them.
For pages stuck in “Discovered” status for under two weeks, practice patience. Also, verify your sitemap. New pages often take two weeks to move from discovered to crawled. This happens frequently on newer domains or massive sites. Verify the page exists in your submitted sitemap. If true, monitor the status for two weeks before acting.
For pages stuck longer than two weeks, apply the Crawl Framework systematically. Fix any server errors or WAF blocking issues. Strengthen discovery signals by adding the page to your XML sitemap. Add three to five contextual internal links from high-authority pages.
After finishing these steps, use the URL Inspection tool’s “Request Indexing” button. This tells Google the page awaits crawl evaluation.
Never request indexing before fixing the underlying issue. Hitting that button on an unimproved page yields zero benefits. It wastes Google’s crawl resources and might reduce your site’s overall crawl priority.
Fixing “Crawled – Currently Not Indexed”
Fixing “Crawled” status demands action on Step 4 of the Crawl Framework: content worth indexing. This represents the most substantive fix. You must improve the actual content, not just technical signals.
Upgrading Content Quality
Start your quality assessment with a direct comparison. What does the highest-ranking page provide that your page misses? The answer highlights your specific quality gap.
You can convert “Crawled” pages to indexed pages through major content upgrades. Increase the information depth and specificity dramatically. Add original examples, case studies, or exclusive data. Improve the answer-first structure so users see immediate value in the first paragraph. Finally, delete thin sections that dilute overall page quality.
Requesting Re-Evaluation
After making major content upgrades, use the URL Inspection tool. Click the “Test Live URL” feature to confirm Google sees your improvements. Only then should you click “Request Indexing.” Wait two to four weeks for Google to re-evaluate the page.
Internal linking also helps “Crawled” pages slightly. Strong internal links signal that you consider the page valuable. This influences Google’s quality threshold marginally. However, links alone cannot save thin content. Quality remains your primary lever.
Our content audit methodology guide explains how to fix “Crawled” status across multiple pages systematically.
How Long Each Status Typically Persists
Knowing typical status durations helps you balance urgency with patience.
“Discovered – currently not indexed” usually resolves within one to four weeks on established sites. This assumes a good crawl budget and strong internal links. Pages with weak links might wait eight weeks. On new sites, this queue can last for months, especially after mass URL submissions.
“Crawled – currently not indexed” lacks a natural expiration date. Google re-crawls the page periodically. Without major content upgrades, it reaches the exact same negative conclusion every time. This status stays forever until you improve or delete the page.
Read our guide to the GSC AI Performance Report. It explains how non-indexed pages fail to appear in AI Overviews, directly harming your generative search visibility.
How to Request Indexing Correctly
Once you finish the Crawl Framework diagnosis and fix all issues, request indexing properly.
Open Google Search Console and use the top URL Inspection bar. Enter your affected URL and click “Test Live URL.” This shows Google’s current rendered view. Ensure your improvements appear clearly. After confirming this, click “Request Indexing.”
Avoid three dangerous practices. Do not click “Request Indexing” multiple times rapidly. Google queues the request, and spamming the button accomplishes nothing.
Do not use third-party “instant indexing” services. These companies abuse the Indexing API against Google’s policies. They will get your site flagged for API abuse.
Finally, do not request indexing before fixing the root problem. Asking Google to evaluate a flawed page wastes your queue budget and signals low quality to the crawler.
Frequently Asked Questions
What is the difference between “Discovered” and “Crawled” statuses?
“Discovered” means Google knows the URL exists but hasn’t visited it yet. This prioritization issue often resolves with time and better internal linking. “Crawled” means Google visited the page and actively rejected it. This indicates a severe content quality or technical flaw requiring major improvements.
How long does “Discovered” status normally last?
On high-authority sites with strong internal links, it resolves in one to four weeks. On new domains or pages with weak links, it can last up to three months. Massive URL submissions extend this waiting period due to queue competition.
Why does Google choose not to index a crawled page?
Google rejects pages featuring thin content or lacking informational depth. It also ignores content duplicating other internal or external pages. Auto-generated content lacking original value fails the indexation test constantly.
Should I keep requesting indexing if a page stays “Crawled”?
No. Requesting indexing without improving the content achieves nothing. Google evaluates the unchanged page and rejects it again. Fix the specific quality issue, verify the changes with the Live URL tool, and submit exactly one indexing request.
Can adding internal links fix “Crawled” status?
Rarely on its own. Internal linking acts as a discovery signal, which helps fix “Discovered” statuses. For a “Crawled” status, Google already evaluated and rejected the page. You must improve the content quality first. Internal links help slightly but cannot override poor content.
Conclusion
The difference between “Discovered” and “Crawled” statuses dictates your entire repair strategy. “Discovered” represents a queue problem. It requires better discovery signals and patience. “Crawled” represents a quality problem. It requires major content upgrades.
Apply the 5-step Crawl Framework systematically. Check Connection, Recognition, Access, Worth, and Linked architecture in order. This prevents you from applying the wrong fixes to the wrong statuses. Always fix the underlying issue before hitting the Request Indexing button. Then, wait two to four weeks for Google to reward your improvements. Connect with SEO practitioners fixing indexing issues at Scale Xpert on Discord. It is an excellent community for SEO learning and genuine backlink exchange
