“Discovered - currently not indexed”: what it means and how to fix it
Google found the URL, usually in your sitemap or through a link, but hasn't crawled it yet, so 'Last crawled' is empty. Google postponed the crawl, often to avoid overloading the site. On a small site it mostly means Google doesn't see the page as a priority yet.
- Google hasn't read the page at all yet, so content changes alone won't help until it's crawled.
- Normal for brand-new pages and sites.
- For pages stuck for weeks: link to them from pages Google already crawls, and check your server is fast and error-free.
What does Google say?
Google found the page but hasn't crawled it yet. Usually Google wanted to crawl it but rescheduled, to avoid overloading the site, which is why the last crawl date is empty.
Paraphrased from Google's Page indexing report help.
Why does it happen?
- 01The page or the whole site is new.
- 02The page is only listed in the sitemap, with no internal links pointing to it.
- 03The server was slow or returned errors, so Google crawls less.
- 04The site has lots of low-value URLs (filters, parameters, tag pages) competing for crawls.
- 05Google doesn't expect the page to add much, based on similar pages on your site.
Is “Discovered, not indexed” a problem?
It depends on which URLs Search Console lists. Check them against these two lists.
Ignore it if
- The page was published in the last few days.
- It's a low-value URL you don't need in search.
Fix it if
- An important page has been 'Discovered' for weeks.
- Most new posts get stuck here. That points to crawl priority or server issues.
How do I fix “Discovered, not indexed”?
Check any single URL with URL Inspection. After fixing, open the issue in the Page indexing report and click Validate fix; Google says it typically takes up to about two weeks.
# after a real changeInspect URL → Request indexing # in the Page indexing reportOpen the status → Validate fix
- 1
Link to it from pages Google already crawls
Your homepage, blog index and two or three related posts. A URL that only exists in the sitemap looks unimportant.
- 2
Check your server
In Search Console, open Settings → Crawl stats. Look for slow average response times or spikes in server errors. A slow or failing server makes Google crawl less.
- 3
Cut low-value URLs
Tag pages, filtered views and URLs with tracking parameters all compete for the same crawls. Keep them out of the sitemap and mark the ones you don't need in search with noindex.
- 4
Keep the sitemap clean
List only canonical, indexable URLs that return 200. Sitemaps full of redirects or errors get trusted less.
- 5
Request indexing once
In URL Inspection, click Request indexing for your most important stuck pages. It nudges the crawl but there's a daily quota, so save it for pages that matter.
How does Blogizi handle “Discovered, not indexed”?
Blogizi shows this status as 'Discovered, not crawled' for each post in the Search tab and keeps checking daily, so you see when Google finally crawls it. Every published post goes into your blog's sitemap automatically.
Index checks for every post are part of Pro, $19/month with a 7-day trial for $0. Your AI agent can read the same statuses over MCP.
Search › IndexingChecked dailyFrequently asked questions
For a new page on a small site, often a few days to a few weeks. If it lasts longer, the page probably needs more internal links.
Last reviewed October 23, 2026 against Google's Page indexing report help.
Related Search Console statuses
Crawled - currently not indexed
Google read the page and decided not to index it, for now.
Read the guide →Usually finePage with redirect
The URL redirects somewhere else, so Google indexes the destination.
Read the guide →Check itBlocked by robots.txt
Your robots.txt file tells Google not to crawl this URL.
Read the guide →Get every post indexed
Publish on your own domain with sitemaps and canonicals handled, and see which posts Google hasn't indexed without opening Search Console.
Ready to get started?
Your agents write. Blogizi publishes. Google sends the traffic to your domain.
