A page that was in Google and is now not is a different problem from a page that was never accepted, and the two get treated as one thing constantly.
If the page was never indexed, you are asking whether it is good enough, which is the crawled, currently not indexed conversation and it is a question about quality. If it was indexed and dropped out, something changed. Those are different investigations and the second one is usually faster, because a change has a date attached to it.
Start with what changed, not with the page
This is the part people skip. They open the page, read it, decide it is fine, and then start rewriting it anyway.
Before touching the content, get the date it dropped from Search Console and ask what happened that week. A release. A theme update. A plugin. A migration. A robots.txt edit. A new SEO plugin with opinionated defaults. On the sites I get called into, the answer is in that list far more often than it is in the writing.
I have seen a whole section vanish because a staging Disallow shipped with a release, and the client had spent three weeks improving the content on those pages first.
The order I check
Is it accidentally noindexed? View the raw source, not the rendered page, and search for noindex. Then check the HTTP headers, because X-Robots-Tag does the same job invisibly and almost nobody looks there. An SEO plugin with a category-level setting can do this to a thousand URLs without anyone touching a page.
The numbers say how rarely this is deliberate. The 2025 Web Almanac found meta robots tags on 47.9% of mobile pages but an actual noindex directive on only 2.4%. Half the web emits the tag; almost nobody uses it to make a decision. So when a noindex does turn up on a page that was ranking, the overwhelming likelihood is that a setting produced it rather than a person.
Is it blocked in robots.txt? If so, and it also carries a noindex, the two are fighting. Blocking wins and removal loses, because Google cannot read a directive on a URL it is not allowed to fetch.
Does the canonical point somewhere else? A page canonicalising to another page is asking to be dropped. This is the one that surprises people, because the page looks completely normal.
Did the URL change? A slug edit with no redirect deindexes the old URL and starts the new one from nothing. On a CMS this is a two-click accident.
Is it still linked from anywhere? A page that quietly became an orphan during a redesign has stopped being part of the site, and Google eventually treats it that way.
Did the server have a bad week? Sustained 5xx errors during a crawl will do it. Crawl Stats, Host status.
When none of that is it
Then, and only then, it is a quality judgement, and it usually arrives with company: a group of pages rather than one, often after a core update.
I would be honest with yourself at that point about whether the page was ever earning anything. Ahrefs looked at 14 billion pages and found 96.55% get no traffic from Google at all. A page dropping out of the index after years of no clicks is not a mystery to solve. It is the index catching up.
The pages worth fighting for are the ones that were doing something. For those, the work is the same work as any thin page: make it the best answer to something, or accept it was not going to be.
What I would not do
- Mass re-submission. Requesting indexing on four hundred URLs does not fix a cause and it does not speed anything up. Submit one, watch what happens, and use it as a test rather than a treatment.
- Rewriting first. If the cause is a noindex header, a month of content work changes nothing and you will conclude that content does not matter.
The short version
- Dropped out is not the same as never accepted. Get the date first.
- Ask what shipped that week before you read the page.
- Check noindex in the source and in the headers. X-Robots-Tag is invisible on the page.
- Then robots.txt, canonical, URL changes, internal links, server errors, in that order.
- Only then treat it as quality, and be honest about whether the page was ever earning.
- Do not mass-resubmit. It treats a symptom and tells you nothing.
If a site should be ranking and it isn’t, that’s the work I do. Technical SEO covers the crawling and indexing layer. If you’re not sure which of several plausible problems is costing you, that’s what an SEO audit is for.
