Discovered but not indexed (GSC): a practical checklist to move URLs to crawl + index
seogoogle-search-consoleindexing

Discovered but not indexed (GSC): a practical checklist to move URLs to crawl + index

3 min read

If Search Console shows “Discovered - currently not indexed”, this checklist helps you move pages from discovery to crawl to index by fixing crawl accessibility and increasing internal prioritization—without spamming indexing requests.

Table of Contents

What should you do when GSC shows “Discovered - currently not indexed”?

Conclusion

“Discovered” usually means:

  • Google knows the URL (sitemap/internal links)
  • but has not crawled it yet

The practical order is:

  1. confirm the URL is indexable (robots/noindex/canonical/200)
  2. make the sitemap clean (no duplicates/blocked/404)
  3. increase internal prioritization (hubs + related links)
  4. request indexing only for top pages (don’t spam)

If the status becomes “Crawled - currently not indexed”, that’s a different problem.

Explanation

This status is not primarily a content-quality verdict. It’s often a prioritization/crawl allocation issue.

Teams waste time by:

  • repeatedly requesting indexing
  • tweaking content before verifying crawlability

Fix the prerequisites first, then strengthen internal signals.

Practical Guide

Step 1: confirm the page is indexable

For a representative URL, check:

  • robots.txt does not block the path
  • the page is not noindex
  • rel=canonical points to the intended URL
  • HTTP status is 200 (avoid redirect chains)
  • core content is renderable (not an empty shell)

Step 2: make the sitemap an accelerator (not a list)

  • submit https://example.com/sitemap.xml
  • ensure it becomes Success
  • keep it clean:
    • no 404s
    • no blocked URLs
    • no duplicate URL variants (slash/casing/params)

Step 3: increase internal prioritization

Google prioritizes what your site prioritizes.

  • add hub pages (“Start here”, category hubs)
  • add related links per page (3 is enough)
  • ensure important pages are reachable within ~3 clicks

Step 4: do not spam “Request indexing”

Use it only for:

  • homepage
  • hubs
  • top 5–10 pages

Then wait. Re-requesting daily doesn’t help.

Step 5: if it becomes “Crawled - currently not indexed”

Now you’re in a different diagnosis:

  • uniqueness and intent clarity
  • duplication and template signals
  • prioritization and internal linking

Pitfalls

  • fixing content before confirming crawlability
  • sitemap includes duplicates or blocked URLs
  • no hubs/related links (no internal prioritization)
  • daily indexing requests

Checklist

  • [ ] URL is not blocked by robots
  • [ ] URL is not noindex
  • [ ] Canonical points to the intended URL
  • [ ] URL returns 200 and avoids redirect chains
  • [ ] Core content is renderable (not empty shell)
  • [ ] Sitemap is submitted and Success in GSC
  • [ ] Sitemap contains no 404/blocked URLs
  • [ ] Sitemap contains no duplicate variants (slash/casing/params)
  • [ ] Hubs exist for key categories
  • [ ] Each page has related links (3)
  • [ ] Request indexing used only for top pages

FAQ

Q1. Should I request indexing for every discovered URL?

No. Use it only for the homepage, hubs, and the most important pages. It’s not a scalable crawl-budget strategy.

Q2. Why does this happen even when the sitemap is submitted?

Because crawl allocation is still a prioritization decision. Clean sitemaps help, but internal linking and site structure matter.

Q3. What’s the fastest thing that actually helps?

Fix crawlability first, then add hubs + related links so Google sees which pages matter.

Disclaimer

Indexing is probabilistic. You can improve signals, but you cannot force Google to index every URL.

Popular

  1. 1Permit2 explained (Web3): why approvals changed and how to use it safely (checklist)
  2. 2Read wallet signing screens (Web3): a 30-second checklist to avoid permission traps
  3. 3Spec-to-implementation prompt template (AI development): how to stop the model from guessing
  4. 4Revoke token approvals on EVM: how to audit allowances safely (checklist)
  5. 5Clarifying questions checklist (AI development): what to ask before you let an LLM build

Related Articles