"'Discovered - Currently Not Indexed' Explained"
Updated
A Search Console status meaning Google knows your page exists but hasn't visited it yet, so it isn't in search results.
What it means
"Discovered - currently not indexed" means Google has found the page's address, usually from a link or your sitemap, but hasn't crawled it yet, so it can't be in search results. Google's own explanation is that it wanted to crawl the page but expected the visit to overload your site, so it rescheduled; that's why the report shows no last crawl date for these pages.
The key word is discovered. Google has the address on its to-do list and nothing more. It hasn't read a word of the page, so nothing on the page itself can be the reason yet.
Why it matters
A page in this state is invisible in Google Search. For a brand-new page that's normal and usually clears up within days. Google says it can take a week or so for it to start crawling a new page or site. A page that sits here for weeks is telling you Google doesn't see enough reason to spend a visit on it.
It's easy to confuse with its neighbor, Crawled - currently not indexed. The difference decides where you look:
| Discovered - currently not indexed | Crawled - currently not indexed | |
|---|---|---|
| Has Google visited the page? | No | Yes |
| Last crawl date in the report | Empty | Filled in |
| What Google is judging | Whether the page is worth a visit at all | Whether what it read is worth indexing |
| Where to look first | Links to the page, your sitemap, your server | The page's content: thin, duplicated, or too similar to another page |
Common reasons a page stays "discovered" for a long time:
- Nothing important links to it. A page only reachable from your sitemap, or buried several clicks deep, looks unimportant. Google says pages need to be linked from a known page or listed in a sitemap to be found, and a link from your own menu or homepage is a much stronger nudge than a sitemap entry alone.
- Your server is slow or struggling. Google's stated reason for this status is avoiding overloading the site. If your host is slow or returns errors, Google crawls less.
- Too many low-value addresses. Filtered, sorted or tagged versions of the same page (for example
?sort=priceor?color=green) can create far more addresses than real pages, and Google spreads its visits across all of them. - The page is new. Sometimes the only fix is time.
How to fix it
- Check the page's real status. Open Search Console, paste the page's full address into the inspection bar at the top, and read the result. The Pages report can lag behind; the URL Inspection tool shows Google's latest information for that one page. If it now says the page is indexed, you're done.
- Make sure the page is worth crawling. Is it a real page with its own content, or one of many near-copies? If it's a filtered or tagged duplicate, it doesn't need to be indexed and you can leave it.
- Link to it from pages Google already visits. Add a link from your homepage, a main menu, or a related, popular page. This is usually the single most effective fix for a small site.
- Confirm it's in your sitemap. Include only pages you want in search, then resubmit it under Indexing → Sitemaps. See how to submit a sitemap.
- Check your server. In Search Console, open Settings → Crawling → Crawl stats and look at the host status. If it reports availability problems, talk to your web host; a firewall or bot protection that blocks Googlebot can cause this too.
- Request indexing for your most important pages. In the URL Inspection result, click Request indexing. It speeds up the visit for that page but doesn't guarantee indexing. See how to request indexing.
- Give it time, then check again. After a fix, wait a week or two before inspecting again. If the page moves to "Crawled - currently not indexed", Google has now visited it and the question has become about the content.
Most small sites don't have a crawl budget problem in the technical sense; Google's crawl budget guide is written for very large or fast-changing sites. On a small site, a page stuck here is almost always a linking, quality or server issue, not a limit you've hit.
ask datanephew
Which of my pages are "Discovered - currently not indexed"?
Ask datanephew which pages on your site aren't indexed and why. It reads your Search Console indexing data for free and groups pages by the reason Google gives, so you can see which ones are still waiting for a first visit and which were visited and turned down.
Can datanephew get Google to crawl these pages?
On the Owner plan, datanephew can resubmit your sitemap to Google and Bing and notify IndexNow-supporting search engines like Bing about pages you've published or changed. It can't press Google's Request indexing button, which only works for a person signed in to Search Console, but it will tell you which addresses are worth requesting yourself.
Is this page stuck because nothing links to it?
Ask datanephew to inspect the page and check whether it's in your sitemap and how Google found it. If the only route in is the sitemap, adding a link from your homepage or menu is the first thing to try.