Context
Discovered Currently Not Indexed Versus Crawled: Two Statuses, Two Different Judges
I read the two statuses as judged by different parts of Google, and the fix for one does nothing for the other.
“Discovered, currently not indexed” means Google has the URL, from the sitemap or a link, and has not fetched it. It is a queue. Nothing about the page has been read, so nothing about the page has been judged. What decides when the queue moves is crawl demand: how many links point at the page, how fresh Google thinks the site is, how much of its crawl budget it is willing to spend on a domain nobody links to. Encited’s guide to the discovered status reports the same split and points out that the fix for a queued page is links and dates, not a rewrite, and I agree: 64 of my pages sat there with the full text server-rendered and nothing wrong with any of them.
“Crawled, currently not indexed” means Google fetched the page, read it, and chose not to keep it. That is an evaluation, not a queue. UltimateWB’s comparison points out that the two are scheduling versus quality, and I agree with the framing as far as it goes. Where I would push back is the word quality. Google judged my five crawled pages in late August with zero inbound links from any indexed page, and a page with no links is judged as a page nobody vouches for, whatever its text says. The French twins of those five pages, same template, same length, are indexed. The difference was never the writing.
So the instruction per status is different. Discovered: give Google a reason to come, then wait and check the crawl date. Crawled: change the page or what points at it, then ask for a fresh look. Validate Fix is a third thing, and it only helps one of the two.