Skip to content

Discovered - currently not indexed: why Google has not crawled your page yet

By , maker of SEO ConsoleUpdated 6 min read

Short answer

"Discovered - currently not indexed" means Google knows the URL exists, from a link or your sitemap, but has not fetched it yet. Google's own explanation is that it wanted to crawl the page but put it off, often to avoid overloading the site. The fix is to make the page look more important (internal links), make the site cheaper to crawl (fewer junk URLs, a faster server), and give it time.

You will find this status under Indexing → Pages in Search Console, in the Why pages aren't indexed table. Open it and you will notice the Last crawled column is empty. That is the whole story: Google has never fetched these pages.

How it differs from "Crawled - currently not indexed"

The two statuses sound alike but point to different problems.

Discovered - currently not indexedCrawled - currently not indexed
Has Google fetched the page?NoYes
Last crawled dateEmptySet
Usual causeLow crawl priority or limited crawl capacityGoogle read the page and judged it not worth indexing
Where to look firstInternal links, URL count, server speedContent quality and duplicates

If your page is in the other bucket, read Crawled - currently not indexed instead.

Why Google has not crawled the page

Google decides how much to crawl on each site from two things: how much your server can handle without slowing down, and how much Google wants your URLs. A page stuck as "discovered" is losing on one of the two.

The server looks like it cannot take more

If your pages respond slowly or return server errors, Google backs off to avoid making things worse. New URLs then wait in the queue. Check Settings → Crawl stats in Search Console. Look at average response time and the host status section. Rising response times or a spike in 5xx errors around the time pages got stuck is a strong clue.

The page looks unimportant

Google prioritizes URLs that are linked prominently from pages it already crawls often. A page that appears only in the sitemap, or is linked only from page 14 of a paginated archive, gets low priority.

The site has more URLs than it has value

Faceted navigation, search result pages, calendar archives and URL parameters can create thousands of crawlable URLs that are mostly duplicates. Google spends its time on those, and your real pages wait. It is a frequent cause on e-commerce and large content sites.

The site is new

A new domain with few links pointing to it gets crawled cautiously. Pages often sit here for days or a few weeks before Google gets to them, and that is normal.

How to get the pages crawled

1. Check a sample of URLs

Open a few of the listed URLs in URL Inspection. Make sure each one is a page you actually want indexed, returns a 200 status, and is not blocked by robots.txt. Click Test live URL to confirm Google can fetch it right now.

This is usually the change that helps most. Add contextual links from your home page, category pages or popular articles to the stuck pages. A handful of links from frequently crawled pages does more than any sitemap tweak.

If you publish often, make sure new pages show up on a page Google visits often, such as a "latest" list on the home page or a category index.

3. Cut the URLs that should not be crawled

Find the URL patterns that generate near-duplicates and stop Google from wasting time on them:

  • Use robots.txt to disallow crawling of internal search results and infinite filter combinations.
  • Stop linking to parameter variants of the same page, and set canonicals on the ones that must exist.
  • Remove or consolidate old, thin pages that nobody visits.

Note that noindex alone does not save crawling: Google still has to fetch a page to see the noindex tag.

4. Make the server faster

If crawl stats show slow responses, fix that. Caching, a CDN and fewer slow database queries on page load all help. Faster responses let Google fetch more pages in the same time.

5. Keep the sitemap clean

List only canonical, indexable URLs that return 200, and keep lastmod dates honest. A sitemap full of redirects, noindex pages and errors teaches Google not to trust it.

6. Request indexing for the pages that matter most

For a few key pages, use Request indexing in URL Inspection. It is limited per day, so use it for the URLs you care about, not for hundreds of them.

How long should you wait?

On an established site with healthy crawl stats, newly linked pages usually get crawled within days. On a new site it can take a few weeks. If pages are still stuck a month after you have added internal links, look again at the URL count and crawl stats: the site is probably still spending its crawl on something else.

Common questions

Will submitting a sitemap fix "discovered - currently not indexed"?

Usually not by itself. A sitemap is how Google discovered many of these URLs in the first place. It tells Google the pages exist, not that they are important. Internal links and a cleaner site do that.

Does this status hurt my rankings?

Not directly. Pages that are not crawled cannot rank, but their presence does not harm your indexed pages. A very large number of them can be a sign of a crawl problem that is also slowing down updates to your important pages.

Can a page skip straight from discovered to indexed?

From your side, yes. Once Google crawls it, the page is either indexed or moves to "Crawled - currently not indexed". If it moves to the second, the problem has changed from priority to content.