'Page discovered — currently not indexed' is one of the most frustrating statuses in Google Search Console. Google knows your URL exists but has decided not to crawl and index it yet. This is different from 'Excluded by noindex' (a deliberate block) — it means Google made a judgment call.
Which "not indexed" status are you seeing?
Google Search Console doesn't just tell you a page isn't indexed — it tells you why, and the fix is completely different for each reason. Find your exact status before you touch anything.
- Discovered – currently not indexed. Google knows the URL exists but hasn't crawled it yet. This is a crawl-budget or internal-linking signal, not a content verdict — Google is effectively saying "not worth my time yet." Fix internal linking and page value first.
- Crawled – currently not indexed. Google crawled the page, evaluated the content, and still declined to index it. This is a stronger, more worrying signal than "discovered" — it's usually about quality, thinness, or duplication. Improve the content substantively; clicking "request indexing" alone won't move it.
- URL is unknown to Google. Google has no record of the page at all. Normal for brand-new URLs. Add it to your sitemap, link to it internally, and use URL Inspection → Request indexing.
- Duplicate, Google chose a different canonical than the user. Google found your page but decided a different URL is the "real" version and indexed that one instead. Your canonical tags are being overridden. Check which URL Google picked, then either align your canonical to it or strengthen the signals (internal links, content) toward your preferred version.
- Duplicate without user-selected canonical. You have near-identical pages and no canonical telling Google which to keep. Add a self-referencing canonical to the version you want indexed.
- Excluded by 'noindex' tag. A deliberate block — confirm it's intentional. If you want this page indexed, remove the noindex directive and request indexing.
- Blocked by robots.txt. Your robots.txt is stopping Googlebot from crawling the page. If that's a mistake, fix the Disallow rule.
- Soft 404. Google thinks the page is effectively empty or an error page even though it returns a 200 status. Add real, substantive content — or return a proper 404/410 if the page shouldn't exist.
Why Google skips discovered pages
Google has a finite crawl budget for every site. When it finds more URLs than it can afford to crawl, it queues them and may deprioritise or skip pages it considers low-value. The most common causes:
- Low perceived page quality — thin content, duplicate or near-duplicate pages, no incoming internal links
- Crawl budget exhaustion — the site has too many URLs (pagination, filters, parameters) relative to its authority
- Slow server response times — Googlebot times out and moves on
- The page was only recently created and hasn't been crawled yet (may resolve on its own within days)
- The page has very few or no internal links pointing to it (orphan page)
Step 1: Check for internal linking gaps
Check your internal link structure: any page with zero internal links pointing to it is an orphan page — discovered via your sitemap but systematically deprioritised by Google. In Google Search Console, go to Links → Internal links and look for pages with the fewest entries. Fix this first: add contextual internal links from at least two high-traffic pages on the same topic. Orphan pages are the single most common reason for this status.
Step 2: Audit the page's quality signals
Ask yourself: if a human editor reviewed this page, would they consider it genuinely useful? Google's quality evaluators use E-E-A-T criteria (Experience, Expertise, Authoritativeness, Trustworthiness). Pages that are thin, repetitive, auto-generated, or duplicates of other pages on the site are systematically deprioritised.
✦ Insight
A useful test: search Google for the first two sentences of your page content in quotes. If an identical or very similar passage appears elsewhere on the web (or on your own site), Google may be treating your version as a duplicate and withholding indexation.
Step 3: Check for crawl budget waste
In Google Search Console, go to Settings → Crawl Stats. Look at the total URLs crawled per day. Then check your Coverage report for the total indexed + excluded URL count. If your site has tens of thousands of URLs in the 'Excluded' bucket (mostly parameterised URLs, infinite scroll variants, or auto-generated filter pages), Google is wasting its budget on noise instead of your real content.
# Add to robots.txt to block common crawl-budget wasters:
Disallow: /*?sort=
Disallow: /*?filter=
Disallow: /*?ref=
Disallow: /search
# OR use canonical tags on parameterised pages to consolidate signals:
<link rel="canonical" href="https://example.com/category/shoes" />Step 4: Request indexing (sparingly)
Once you've improved internal linking and content quality, use the URL Inspection tool in GSC and click 'Request Indexing'. Google throttles this — you get roughly 10–12 requests per day across your property. Use it on your highest-priority pages only, not as a mass action. Submitting an updated XML sitemap is a better lever for bulk re-crawl signalling.
⚠️ Warning
Spamming the 'Request Indexing' button does not speed things up. Google processes the requests asynchronously. Repeated requests for the same URL within 48 hours are ignored.
Step 5: Build external signals
A page that nobody on the internet links to or shares has no reason to be prioritised. Even a single high-quality external link, a social share that gets clicks, or being cited in a relevant community can trigger Googlebot to re-evaluate a stalled page. This is why content marketing and link building are inseparable from indexation.
💡 Tip
Practice this in the game: Chapter 1 (The Indexing Inferno) simulates a real discovery-vs-indexing crisis where you must triage which pages deserve crawl budget and fix the internal architecture before a product launch.