What "Discovered — Currently Not Indexed" Means
When Google Search Console flags a URL as "Discovered — currently not indexed," it means Google's crawl scheduler knows the URL exists but has not sent Googlebot to fetch its content yet. The page is in a queue, waiting for its crawl priority to be assigned.
This is a prioritization problem, not a penalty. Google allocates crawl budget based on perceived importance. Your page hasn't demonstrated enough importance signals to jump the queue. The good news: this status is fully fixable without any technical SEO expertise.
Every day your pages are in this limbo, they generate zero impressions and zero clicks. For sites with dozens or hundreds of affected pages, fixing this is often the fastest path to meaningful organic traffic growth — no link building, no technical audits required.
| Status | What Happened | Root Cause | Typical Fix Time |
|---|---|---|---|
| Discovered — Not Indexed | Google knows URL exists, hasn't crawled it | Priority / crawl budget issue | 7–21 days with fixes |
| Crawled — Not Indexed | Google crawled but rejected the content | Content quality issue | Weeks to months |
| Indexed | Page appears in Google's index | N/A — working correctly | N/A |
Step 1: Diagnose the Scope in Google Search Console
Before fixing anything, understand the scale. Open Google Search Console, go to Indexing → Pages, and find "Discovered — currently not indexed." Export the full list. Sort by priority: revenue-generating pages first, then informational content.
Under 10% of pages affected
Normal. Fix individually with targeted internal links and direct URL submissions.
10–40% of pages affected
Crawl budget or internal linking problem. Site-wide fixes needed alongside individual submissions.
Over 40% of pages affected
Critical: domain authority, server speed, or robots.txt blocking Googlebot at the site level. Fix structurally first.
Re-Submit All Affected URLs in Bulk
Don't submit one URL at a time in Search Console. Use IndexFlow to re-submit all affected URLs through Google API, IndexNow, and crawl networks simultaneously. 100 free credits every month.
The 8-Step Fix: Complete Checklist
Follow these steps in order. Steps 1–4 fix the root cause. Steps 5–8 accelerate resolution. Most pages shift from "Discovered" to "Indexed" within 7–21 days after completing the full checklist.
Add Internal Links from Indexed Pages
Internal links are the single most powerful crawl signal you control. A page with zero internal links pointing to it is effectively invisible in Googlebot's crawl prioritization. Research by Botify shows that pages with 5+ internal links are 2.5x more likely to be crawled within 30 days than pages with only 1 internal link.
For each "Discovered" page, find 3–5 already-indexed pages on your site that are topically related. Add a contextual link in the body copy (not the footer or sidebar) pointing to the stuck page. Use descriptive anchor text that includes the target keyword.
Action
Use your CMS search to find existing pages that mention topics related to your stuck pages. Add 3–5 natural in-body links per stuck page. Prioritize links from your homepage, category pages, and 10 highest-traffic posts.
Update Your Sitemap with Fresh lastmod Dates
Your XML sitemap is a direct crawl request to Google. If your affected URLs aren't in the sitemap, Google is discovering them purely through links — which is slower. If they are in the sitemap but the lastmod date is old or missing, Google has less reason to reprioritize them.
Update your sitemap to include every affected URL with today's date as the lastmod. Even if the page content hasn't changed, updating the date signals that something is new and worth a fresh crawl.
Action
Add all affected URLs to sitemap.xml with lastmod set to today. Resubmit the sitemap in Google Search Console under Sitemaps. Verify with the sitemap checker tool.
Check robots.txt for Accidental Blocks
A misconfigured robots.txt is one of the most common causes of "Discovered — currently not indexed" at scale. If your robots.txt has a Disallow rule covering your stuck pages, Google discovers the URLs (from the sitemap) but cannot crawl them. The result: perpetual "Discovered" status.
This is especially common on WordPress sites, staging environments copied to production, and sites with URL parameters blocked by wildcard rules.
Action
Visit yourdomain.com/robots.txt. Look for Disallow rules covering your affected URLs. Use Google's robots.txt tester in Search Console. If you find accidental blocks, remove them and resubmit the sitemap.
Improve Server Response Speed
Googlebot adjusts its crawl rate based on your server's responsiveness. If your server takes more than 500ms to respond, Googlebot reduces crawl frequency to avoid overloading your server. For sites with many pages to index, a slow server directly translates to more pages stuck in "Discovered" status.
Target: under 200ms Time to First Byte (TTFB) for all pages. Enable a CDN, add server-side caching, and optimize database queries.
Action
Use the site speed checker tool to measure TTFB. If above 500ms, enable a CDN (Cloudflare free tier works), add full-page caching for non-personalized pages, and check for database bottlenecks.
Submit URLs via Google Indexing API
The Google Indexing API allows direct crawl requests to Google — bypassing the normal crawl queue. Unlike Search Console URL Inspection (limited to ~10 manual submissions per day), the Indexing API allows up to 200 requests per day per service account.
Google officially supports the API for job postings and video content, but it works for any page type. Most practitioners report crawling within 24–72 hours for API-submitted pages, compared to 7–21 days for organic discovery.
Fastest Method
Use the Google Indexing Tool in IndexFlow to submit all affected URLs via the Indexing API in one batch. No manual API setup — IndexFlow handles authentication and rate limiting automatically. Or use the URL indexing service to submit any URL to Google in under 60 seconds.
Build Topical Authority for the Affected Section
If you have a cluster of pages in "Discovered" status within a specific topic (all your product category pages, all posts in a tag), the problem may be that Google hasn't established authority for that topic cluster on your domain.
Google allocates more crawl resources to sections it deems authoritative. Publishing related content consistently, getting external links to that section, and ensuring strong internal cross-linking all signal that this section deserves more crawl attention.
Action
Identify the section with the most 'Discovered' pages. Publish 2–3 high-quality related pieces. Add internal links between all pages in the section. Get at least 1–2 external links pointing to the most important pages.
Share URLs to Trigger Social Crawls
Sharing a URL on platforms crawled by Googlebot (Twitter/X, LinkedIn, Reddit) creates additional discovery pathways. When Googlebot crawls Twitter and finds a link to your page, it adds the URL to the crawl queue — often with higher priority because a social share implies recency.
For important pages stuck for more than 2 weeks, posting the URL on Twitter/X and LinkedIn often results in Googlebot crawling within 24–48 hours.
Action
For your top 10 stuck pages, post each URL on Twitter/X and LinkedIn with a brief description. Share relevant ones to Hacker News, Reddit, or niche forums. Check GSC 48 hours later — many will have moved to crawled status.
Monitor and Re-Submit Stragglers
After completing steps 1–7, check Google Search Console in 14 days. Most pages will have moved out of "Discovered" status. Those that haven't are worth examining individually: check for canonical tag issues, meta noindex tags, or content that might have been devalued.
Pages remaining stuck after 4+ weeks usually have a content quality issue. Use URL Inspection in Search Console to see what Googlebot sees when it eventually crawls the page.
Action
Re-export the 'Discovered' URL list from GSC after 14 days. Submit stragglers again via Google Indexing Tool. For pages stuck 30+ days, inspect with URL Inspection and review the rendered HTML for issues.
Expected Fix Timeline by Site Type
| Site Type | Without Fixes | With This Guide | With API Submission |
|---|---|---|---|
| Established site (DA 40+) | 7–14 days | 3–7 days | 24–72 hours |
| Mid-authority (DA 15–40) | 14–30 days | 7–14 days | 3–7 days |
| New site (<6 months) | 30–60+ days | 14–28 days | 7–21 days |
| New site, zero backlinks | 60–90+ days | 30–60 days | 14–30 days |
New sites with no backlinks face the hardest battle. Building even 5–10 quality backlinks dramatically improves your crawl rate. Use the backlink indexer to ensure your new backlinks get indexed quickly, which in turn improves your overall crawl budget.
Bulk-Submit Your Affected URLs in One Click
Stop submitting URLs one-by-one in Search Console. IndexFlow's backlink indexer and URL submission tool processes your entire exported URL list in seconds, submitting through Google API, IndexNow, and crawl networks simultaneously.
Common Mistakes That Make It Worse
Deleting and republishing the page
This resets any crawl priority the URL had accumulated. Google has to rediscover the new URL from scratch. Never delete a page to fix indexing issues unless the URL is fundamentally changing.
Adding noindex then removing it
Adding a noindex tag causes Google to eventually remove the URL from its index if crawled. Removing it later means starting the indexing process from zero. This also triggers a quality review.
Submitting the same URL hundreds of times per day
The Indexing API has a 200 request/day limit. Multiple submissions of the same URL don't accelerate indexing — they just consume your quota.
Waiting for Google to fix it on its own
Active steps (internal links, API submission, social sharing) can cut resolution time by 60–80%. Passive waiting is the slowest strategy for important pages.
Buying low-quality backlinks to force crawling
Link farm backlinks may get crawled but they add spam signals to your domain. They won't improve crawl budget and can harm rankings.
When "Discovered" Pages Should Stay That Way
Not every "Discovered" page needs fixing. Some pages are legitimately low-value:
- • Paginated archive pages beyond page 2 (use noindex or canonical instead)
- • URL parameter variants (filters, sorting, session IDs) that duplicate content
- • Thank-you pages, checkout pages, account pages with personalized content
- • Thin tag or category pages with fewer than 5 relevant posts
- • Printer-friendly versions, PDF download landing pages, or utility pages
For these, add noindex meta tags. This actually helps your important pages get crawled faster by freeing up budget.
Related Guides
In-depth analysis of each cause behind this GSC status.
Same problem, applied specifically to backlink pages.
Proactive indexing strategy to avoid this problem from the start.
Frequently Asked Questions
How long does 'Discovered — currently not indexed' last?
Without intervention, it can last anywhere from 2 weeks on established sites to 60+ days on new domains. With active fixes — adding internal links, updating the sitemap, and submitting via the Google Indexing API — most pages resolve within 7–21 days. Pages on brand-new domains with no backlinks are the hardest to accelerate, typically taking 14–30 days even with all fixes applied.
Is 'Discovered — currently not indexed' a Google penalty?
No. It is not a penalty or a manual action. It simply means your page is in Google's crawl queue but hasn't been assigned enough priority to be crawled yet. There is no negative ranking signal associated with this status. Once the page gets crawled and indexed, it can rank immediately based on its content quality and authority signals.
Why are so many of my pages in this status at once?
If more than 20–30% of your site shows this status simultaneously, the most likely causes are: (1) you recently published a large batch of new pages that triggered spam signals, (2) your domain authority is low and Google allocates very little crawl budget, or (3) your server is slow and Googlebot throttles its crawl rate. Site-wide issues require site-wide fixes — start with internal linking and server speed.
Can I fix 'Discovered — currently not indexed' for hundreds of pages at once?
Yes. The most efficient method is to export the full list from Google Search Console (Indexing → Pages → 'Discovered — currently not indexed'), then bulk-submit all URLs via the Google Indexing API using IndexFlow. The API allows up to 200 submissions per day per service account. Combined with sitemap updates and internal link improvements, this resolves large batches within 2–4 weeks.
Does 'Discovered — currently not indexed' affect my current rankings?
Not directly — your already-indexed pages are not affected. However, if important pages remain unindexed, you're missing out on organic traffic those pages should be generating. Focus your fixing efforts on pages with the highest traffic potential first.
What's the difference between Search Console URL Inspection vs. the Indexing API?
Google Search Console's URL Inspection tool limits you to roughly 10–15 manual submissions per day. The Google Indexing API allows up to 200 URL submissions per day and can be used programmatically for batch submissions, resulting in faster crawling — often within 24–72 hours vs. 7+ days for organic discovery.
Should I use IndexNow if Google hasn't indexed my pages?
IndexNow is primarily for Bing, Yandex, and other supporting search engines — not Google. Use the Google Indexing API for Google-specific submissions, and IndexNow as a supplementary channel for Bing and others.
My page has been 'Discovered — currently not indexed' for 3 months. What now?
After 3+ months, systematically check: (1) robots.txt for accidental blocks, (2) noindex meta tags on the page, (3) canonical tags pointing to a different URL, (4) content quality via URL Inspection in GSC, (5) whether the page has any internal links at all, (6) whether your domain has any backlinks. If everything checks out, evaluate whether the page has enough unique, valuable content to deserve indexing.
Fix "Discovered Currently Not Indexed" at Scale
Use IndexFlow to bulk-submit every affected URL, monitor indexing status in real-time, and automatically re-submit pages that drop out of the index. Free plan includes 100 submissions per month.