Discovered - Currently Not Indexed: How to Fix

What this status actually means

"Discovered - currently not indexed" means Google knows the URL exists — usually because it appeared in your sitemap or a link somewhere — but hasn't crawled it yet. This is a pre-crawl state, not a rejection. Google has the address; it just hasn't knocked on the door.

Is this actually a problem?

Often, no. It's completely normal for a portion of a sitemap to sit in this state temporarily, especially right after publishing or on a large site. It becomes worth investigating when a specific page — or a large share of your site — stays here for weeks with no movement.

Common causes

• Crawl budget prioritization — Google allocates more crawling to pages it judges important; a new, low-authority page waits its turn.
• No internal links pointing to it — a sitemap entry with zero links from elsewhere on your site signals low priority.
• Server errors during a prior crawl attempt — if Googlebot hit a timeout or 5xx error trying to reach the page, it backs off and retries later rather than immediately.
• A very new or low-authority domain — Google crawls new sites more cautiously until it has a track record to go on.

How to check which of your pages are affected

In Search Console, open the Pages report under Indexing, and look for "Discovered - currently not indexed" in the "Why pages aren't indexed" table. Clicking it lists every affected URL, and clicking an individual URL opens URL Inspection for a live check.

How to speed it up

• Link to the page from somewhere Google already crawls regularly — your homepage, a category page, or a recent-posts list. A sitemap entry alone is a weak signal on its own.
• Keep your sitemap's lastmod dates accurate — a stale, unchanged sitemap gives crawlers no reason to revisit it.
• Confirm the server responds quickly and with a clean 200 status — check this with Search Console's URL Inspection "Test Live URL" feature.
• For search engines that support it — Bing, Yandex, Seznam, and Naver — push the URL directly via IndexNow instead of waiting for their next scheduled crawl.

When to actually worry

If a large share of your site sits in this state for a month or more, it's usually a signal of a deeper crawl budget or site-authority issue rather than something fixable page-by-page — worth a broader technical SEO review rather than repeatedly requesting indexing on individual URLs.

Discovered vs. crawled: which one do you have?

• Discovered: Google knows the URL but hasn't fetched it yet. The fix is usually stronger discovery signals: internal links, an accurate sitemap and a fast, healthy server.
• Crawled: Google fetched the page and decided not to index it. The fix is usually better content with more unique value and less duplication. See our guide to "Crawled - currently not indexed".

A step-by-step checklist

1. Confirm the URL itself. It should return 200, not redirect, and the sitemap should list the exact canonical version (same protocol, host and trailing slash).
2. Put the page on a real navigation path. Link to it from a category page, a hub page or a related-articles block, not only from the sitemap.
3. Check your server logs or hosting dashboard for 5xx errors, timeouts or rate limiting that could make Googlebot slow down.
4. Review Crawl stats under Settings in Search Console. Rising response times or a spike in errors reduce how much Google is willing to crawl.
5. Take low-value URLs out of the crawl path. Endless filter combinations, session IDs and calendar pages use up crawling your important pages need.
6. Request indexing once for your most important URLs in URL Inspection, then move on. Repeating the request doesn't move a page up the queue.

Large sites: when thousands of URLs are stuck

When a big share of a large site is discovered but not crawled, the cause is usually overall crawl demand rather than individual pages. Prioritize: link your most valuable pages from high-level pages, trim or noindex thin sections, split huge sitemaps into logical groups so you can see which sections lag, and speed up your server. Our crawl budget guide covers this in more depth.