What's the difference between “discovered” and “crawled – currently not indexed”?

“Discovered” means Google hasn't fetched the page yet — it only knows the URL. “Crawled” means it fetched and assessed the page but didn't add it to the index.

Is this a crawl budget issue?

Often, yes. Google slows crawling when a server gets slow or returns errors, and when a site has huge numbers of low-value URLs such as filter combinations.

Is adding the URL to the sitemap enough?

A sitemap helps Google discover a URL but doesn't guarantee a crawl. Internal links from strong pages and a fast, stable server matter more.

“Discovered – currently not indexed” — why and what to do

Google knows the URL (from a link or a sitemap) but hasn't visited it yet. It usually postponed the crawl because the server responded slowly, there are very many URLs, or the page doesn't look important. A faster server, fewer pointless URLs and better internal linking help.

What this status means

Google has the URL on its list but hasn't fetched it. According to Google's documentation, the typical reason is that crawling was rescheduled because it was expected to overload the site. Google plans the visit for later — sometimes days, sometimes weeks.

Common causes

a slow or overloaded server: long response times, 5xx errors, 429 responses,
lots of low-value URLs: filter and sort combinations, parameters, calendars — the crawler wastes time on them,
a new site, or suddenly a very large number of new pages,
pages deep in the structure: reachable only through the sitemap or many clicks from the homepage.

What to do

Check Search Console's Crawl stats report (Settings): response time and the share of server errors.
Speed up server responses and remove the causes of 5xx errors.
Cut low-value URLs: robots.txt for filters and internal search, canonicals for variants.
Link important pages from navigation, categories and content, not only from the sitemap.
Make sure the sitemap lists only 200 URLs, without redirects or noindex.

How to watch the causes

A slower server and 5xx errors show up in response times first, and in Google's reports only later.

IndexRise measures the response time of monitored pages every night and reports a several-fold increase as well as any 5xx on a page that used to work. It also tracks the number of URLs in your sitemaps — a sudden flood of new URLs is a frequent cause of this status.

Discovered – currently not indexed