“Discovered – currently not indexed” means Google knows a URL exists but has not crawled it yet, so the page cannot appear in search results. The usual fix is not to keep pressing “Request indexing.” A site owner should first check crawl budget signals, internal links, duplicate content, page quality, server speed, and sitemap accuracy.
TLDR: This Google Search Console status means the URL is in Google’s queue, but Google has not fetched and indexed it. For example, an ecommerce site may submit 120 new product pages, then see 70 listed as Discovered – currently not indexed after two weeks because many pages have thin descriptions and weak internal links. In one common case, improving internal links and removing low-value URLs from the sitemap can reduce affected pages by 40% to 60% within a month. The fastest win is usually better site structure, not repeated manual indexing requests.
What the Status Means
All Heading
In Google Search Console, Discovered – currently not indexed appears under page indexing reports. It means Google found the URL through a sitemap, internal link, external link, or another discovery path. But Google has not crawled the page yet.
This is different from Crawled – currently not indexed. In that case, Google has already visited the page and decided not to index it, at least for now. With Discovered, the page is still waiting for its first crawl.
That distinction matters. A discovered page may have no content problem at all. Google may simply be delaying the crawl due to site quality, crawl demand, server limits, URL overload, or weak signals.
Honestly, it feels like Search Console could explain this better. A page can sit in this status for days, weeks, or longer, and the report may update slowly. That delay can make normal troubleshooting feel more confusing than it should.
Why Google Discovers a Page but Does Not Crawl It
Google does not crawl every known URL at once. It decides where to spend crawl resources. If a site sends too many weak or similar URLs, Google may slow down. If a server responds slowly, Google may also reduce crawl activity.
The most common causes include:
- Low internal link strength: The page exists in the sitemap but is not linked well from important pages.
- Thin or repetitive content: Product pages, tag pages, and location pages often trigger this issue.
- Too many low-value URLs: Filters, parameters, archives, and search result pages can waste crawl attention.
- Slow server response: If pages take several seconds to respond, Google may crawl less.
- Large sitemap bloat: A sitemap with thousands of weak URLs can dilute signals.
- New site or new section: Google may need more time to trust and crawl fresh areas.
- Poor canonical signals: Conflicting canonicals can make Google unsure which URL deserves attention.
How to Troubleshoot the Issue
The best process starts with pattern detection. A single affected URL may not matter. Hundreds of affected URLs usually mean a site-wide issue.
1. Check Whether the Page Should Be Indexed
Not every discovered URL deserves indexing. A site owner should first ask whether the page has search value. A checkout URL, filtered category page, internal search result, or duplicate tag archive usually should not be indexed.
If the page should not rank, it should be removed from XML sitemaps. It may also need a noindex tag, blocked links, or better parameter handling. Google should not be invited to crawl junk URLs.
2. Inspect the URL in Search Console
The URL Inspection tool shows how Google sees the page. It can confirm whether the URL is known, submitted in a sitemap, allowed by robots.txt, and eligible for indexing.
If the page is allowed and listed in the sitemap, the next step is to check whether it has enough crawl signals. The tool is helpful, but it can be slow. Expect to waste time on fresh pages, since Search Console data can lag behind live changes by a few days.
3. Improve Internal Linking
Internal links are one of the clearest signals that a page matters. A page buried five clicks deep may be discovered but ignored for a while.
Useful fixes include:
- Linking from relevant category pages.
- Adding links from high-traffic blog posts.
- Including new pages in “related products” or “related articles” blocks.
- Reducing click depth for key pages to three clicks or fewer.
- Using descriptive anchor text instead of vague text like “read more.”
4. Clean the XML Sitemap
An XML sitemap should not be a dump of every URL. It should list canonical, indexable, useful pages only.
Common sitemap mistakes include including redirected URLs, noindex URLs, duplicate URLs, parameter URLs, and pages with almost no content. If Google sees too many poor URLs in a sitemap, it may treat the sitemap as less useful.
A clean sitemap helps Google focus. For large sites, separate sitemaps by type. For example, a site may use one sitemap for products, one for categories, and one for articles. This makes diagnosis easier when a specific section gets stuck.
5. Check Server Logs and Crawl Stats
Search Console’s Crawl Stats report can show whether Googlebot is visiting the site often. Server logs give even better detail. They show which URLs Googlebot requests, when it visits, and what status codes it receives.
Warning signs include:
- Many 5xx server errors.
- Frequent timeouts.
- Heavy crawling of low-value parameter URLs.
- Very low Googlebot activity on new pages.
- Slow response times above 1,000 ms for HTML pages.
If the server struggles, Google may crawl less. Fixing hosting, caching, database load, or CDN setup can improve crawl activity.
6. Improve Page Quality
Google may delay crawling pages that look similar to many others. This happens often with ecommerce, real estate, travel, local landing pages, and programmatic SEO pages.
Strong pages usually include unique copy, useful images, clear headings, helpful specs, reviews, FAQs, and original data. Weak pages often contain only a title, stock text, and a few repeated lines.
For example, a product page with 80 words of manufacturer text may struggle. A product page with 500 words of unique detail, comparison notes, customer questions, and original photos sends a stronger signal.
7. Fix Duplicate and Canonical Confusion
Google may discover several versions of the same page. Examples include trailing slash variations, HTTP and HTTPS versions, uppercase URLs, tracking parameters, and filtered category URLs.
The canonical tag should point to the preferred version. Internal links should also use that same version. Mixed signals can slow crawling and indexing.
8. Submit Requests Carefully
The “Request indexing” button can help for a few important pages. It is not a bulk indexing tool. If hundreds of URLs are affected, the root cause is usually structural.
Manual requests make sense after a page has been improved, linked internally, and confirmed as indexable. Submitting the same weak URL again and again rarely changes the result.
How Long Does It Take to Resolve?
There is no fixed timeline. A strong page on a trusted site may leave this status in a day or two. A weak page on a new or bloated site may stay there for weeks.
After technical and content fixes, many sites see movement within 7 to 30 days. Large sites may need several crawl cycles. Teams should track affected URL counts weekly, not hourly.
When the Status Is Not a Problem
This status is not always bad. If Google discovers thousands of filter URLs, admin paths, or duplicate archives and does not crawl them, that may be fine. The goal is not to index every URL. The goal is to get useful, canonical, search-worthy pages indexed.
A healthy site may still have some URLs listed as Discovered – currently not indexed. The issue becomes serious when key revenue pages, articles, or category pages remain stuck.
FAQ
What does “Discovered – currently not indexed” mean?
It means Google knows the URL exists but has not crawled it yet. Since it has not been crawled, it cannot be indexed or ranked.
Is “Discovered – currently not indexed” bad?
It depends. It is bad if important pages are affected. It may be harmless if the URLs are duplicates, filters, or low-value pages.
How can a site owner fix this status?
The main fixes are stronger internal links, cleaner sitemaps, better content, faster server response, and removal of low-value URLs from crawl paths.
Should the URL be submitted again in Search Console?
Only after the page has been improved and confirmed as indexable. Repeated submissions without fixes usually do little.
How long does Google take to index discovered pages?
It can take days or weeks. Strong pages on trusted sites are usually crawled faster. Weak pages on bloated or new sites often wait longer.
What is the difference between “Discovered” and “Crawled” not indexed?
Discovered means Google has not visited the page yet. Crawled means Google visited the page but chose not to index it.
Recent Comments