IDX-03
IDX
P0
Discovered, currently not indexed
The Page Indexing report lists a page as "Discovered, currently not indexed", and it has sat in that state for 7 or more days.
What This Is
The Page Indexing report lists a page as “Discovered, currently not indexed”, and it has sat in that state for 7 or more days.
This state means Google found the URL but has not crawled it yet, or crawled it and is holding off on indexing. The page is not blocked. It has simply not earned a crawl yet.
Before you check
You are reading the “Discovered, currently not indexed” row in the Page Indexing report, not a different reason.
You have the exact URL and can open it in a browser.
You can see the page’s place in the internal link structure and the sitemap.
If any of these is false, fix it before running the tree.
Diagnostic tree
Run the checks in order. Each check ends in a resolution or the next check.
Check 1. Is the page linked internally?
How: open the page and count how many other pages on the site link to it. Check the homepage, the category pages, and at least two related articles.
Why: Google discovers pages by following links. A page with no internal links, or one buried far from the homepage, is hard to reach and gets crawled late or never.
If the page has zero internal links, or sits more than three clicks from the homepage, go to Resolution A. If the page has at least one internal link and sits within three clicks of the homepage, go to Check 2.
Check 2. Is the page in the sitemap?
How: open Sitemaps in Search Console. Path: Indexing, then Sitemaps. Download the sitemap and search for the URL. Confirm the sitemap reads “Success”.
Why: a sitemap lists the URLs you want crawled. A missing URL or a broken sitemap delays discovery.
If the URL is missing from the sitemap, or the sitemap shows one or more errors, go to Resolution B. If the URL appears in a sitemap with zero errors and reads “Success”, go to Check 3.
Check 3. Is the page crawlable and unique?
How: run a live test in the URL Inspection tool. Read “Crawl allowed?”, “Page fetch”, and “User-declared canonical”. Then check the page for thin or duplicate content.
Why: a blocked or duplicate page will not move past this state. Google will not spend a crawl on a page it cannot use.
If the page is blocked, a duplicate, or thin (under 300 substantive words), go to Resolution C. If the page is crawlable and has 300 or more substantive words of unique content, go to Resolution D.
Resolutions
Resolution | Condition | Action |
|---|---|---|
A. No internal path | Zero internal links or more than three clicks from the homepage | Add internal links from related pages and from the nearest category or hub page |
B. Not in sitemap | URL missing from the sitemap or sitemap errors | Add the URL to the sitemap, resubmit the sitemap, and confirm it reads “Success” |
C. Blocked or duplicate | robots.txt, noindex, duplicate, or thin content | Fix the block or improve the content so the page earns a crawl |
D. Wait | Crawlable, unique, linked, and in the sitemap | Submit once, then wait 14 or more days. Google decides when to crawl |
When to escalate
Escalate when all three are true.
The page is internally linked, in a valid sitemap, crawlable, and unique.
It has held “Discovered, currently not indexed” for 14 or more days.
The page carries revenue, and a competing page already ranks for the same query.
Everything else closes in the resolutions above.
Primary sources
Related articles
Last verified
·
Owner
Mahesh