“Discovered – Currently Not Indexed”: What It Means and How to Fix It

What does “Discovered – currently not indexed” mean?

It means Google has found the URL, through a link or a sitemap, but hasn’t crawled it yet. Google’s own description says it typically wanted to crawl the URL, expected that to overload the site, and rescheduled the crawl. That is why the report shows no last crawl date for these pages.

It is different from “Crawled – currently not indexed”, where Google fetched the page and decided not to index it. That status points to content quality; “Discovered” points to crawling priority.

Is it a problem, or should you wait?

Google’s report says that not being indexed is not necessarily bad. For a site launched in the last few weeks, or a batch of new pages, waiting is often enough. It becomes a problem when important pages, such as your services, products or contact page, stay in this state for weeks, or when the number keeps growing while indexed pages don’t.

Google says crawl budget mostly matters for very large sites, but it also names many URLs in “Discovered – currently not indexed” as a sign worth acting on. On a small site, the cause is rarely server capacity; it is usually that the pages look unimportant because few links point to them.

Are your links visible without JavaScript?

Google can follow links only when they are ordinary <a> elements with an href attribute. Menus that open with JavaScript, buttons that navigate with onClick, or links that are only added after the page loads may never be seen as links at all.

On websnexus.com, Search Console listed /services, /contact, /case-studies, /ui-ux-design and /pos-system as “Discovered – currently not indexed”. Our services menu was only added to the page when a visitor hovered over it, so its links weren’t in the HTML Google received. We changed the navigation so every menu link is a plain <a href> in the server-rendered HTML, even while the dropdown is closed.

Do the pages get links from pages Google already crawls?

Google decides what to crawl partly from how a page is linked. A page reached only through a sitemap, or buried several clicks deep, looks less important than one linked from the homepage, the menu and related pages.

We added three kinds of links: footer links to our market pages, which Search Console had also listed as discovered but not indexed; a related-articles block under every blog post linking to four neighbours on the same topic; and hub pages such as /fix and /compare that link to every guide in their group.

Is your sitemap accurate?

List every page you want indexed in an XML sitemap, submit it in Search Console and reference it in robots.txt. Google uses the lastmod date only when it is consistently accurate, so set it to the date the page’s content really changed, not the date the sitemap was generated.

We split our sitemap so each content hub has its own file with real lastmod dates. That also makes Search Console show indexing figures per section, so you can see which group of pages is lagging.

Are the pages thin or duplicates?

Google crawls less of what it expects to be low value. Many near-identical pages, such as tag archives, filtered URLs, location pages that only swap a city name, or old locale copies, can make Google slow down on the rest of the site.

Merge or remove thin pages, set canonical tags on true duplicates, and keep low-value URLs out of the sitemap. On our site, we redirected old untranslated locale copies of every page to the English page.

Does a slow or failing server hold crawling back?

Yes. Google sets how much it crawls from how the server responds. Fast, stable responses let it crawl more; slow responses, 5xx errors and 429 rate-limit responses make it crawl less. Check the Crawl stats report in Search Console for server errors and response times.

Should you use Request Indexing?

Use the URL Inspection tool’s Request Indexing for the handful of pages that matter most, after you have fixed links and content. It asks Google to crawl that page sooner, but it has a daily limit and doesn’t guarantee indexing. It is not a fix for hundreds of pages: links and sitemaps are.

• 1. Check the page returns 200, has no noindex and isn’t blocked in robots.txt.
• 2. Link to it with a plain <a href> from the menu, a hub or related pages.
• 3. List it in the sitemap with an accurate lastmod date.
• 4. Improve, merge or remove thin and duplicate pages.
• 5. Request indexing for your most important pages.