Discovered, currently not indexed: what it means, how it differs from crawled, and how to fix it

Google has the URL, usually from your sitemap or a link, and hasn't crawled it yet. Search Console prints it as Discovered - currently not indexed, and Google's Page indexing help explains it in one line: "Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl." That's also why the last crawl date is empty in the report. It isn't a penalty, it isn't an error, and on a small site with a page published last week it often clears by itself.

So start with the server. Open Crawl stats in Search Console and look at average response time and host status. Slow responses, 5xx errors and timeouts tell Google to crawl less, and that's the documented route into this status. On the small WordPress sites I work on, the other usual suspects are pages nothing meaningful links to, and large sets of near-identical URLs (tags, filters, parameters) that give Google far more addresses than the site has real pages.

It becomes worth investigating when a URL you care about sits there for weeks, or when thousands of URLs do. What it doesn't prove on its own is a crawl budget problem. Google's crawl budget guide is written for very large, fast-changing sites, and it also names sites with a large portion of their URLs in Discovered - currently not indexed as its audience. If that's most of your site, read it. If it's a handful of URLs, Google says keeping the sitemap up to date and checking the Page indexing report is enough, and crawl budget is a hypothesis to test, not a diagnosis to accept.

Google fetched the page, looked at it, and didn't add it to the index at that point. Google's help puts it plainly: it "may or may not be indexed in the future; no need to resubmit this URL for crawling." The word currently is doing real work, because Google may index it later without you touching anything.

This one's about what the page turned out to be. Contributors can include: another URL says the same thing and Google picked that one; the page is one of a set built from the same template with little to separate them; the main content arrives only after JavaScript runs and wasn't there when Google looked, which is the kind of fault JavaScript SEO services exist to find; the page is technically fine but answers nothing a searcher asked; or the site as a whole hasn't yet earned the benefit of the doubt on borderline pages.

It isn't shorthand for thin content, and treating it that way sends people off adding paragraphs to pages whose real problem is that three other URLs already cover the subject.

For a handful of new URLs on an established site, a few weeks is normal and no action's needed. Some URLs in both reports clear with no intervention, which is what currently means in both labels, and others won't (a fair number shouldn't). For an important page that has sat in either report for over a month, diagnose it. For thousands of URLs appearing at once, look for the pattern that produced them, not at any single URL, because the answer's almost always in a template or a setting.

After a real fix, Google has to recrawl before anything changes. Validate the fix in Search Console so you've got a start date, expect Google's two weeks or longer for the validation itself, and give it four to eight weeks before judging the result.