Open the Pages report in Search Console and look under “Why pages aren’t indexed.” Most of what you find there is harmless: redirects, alternate versions, pages you excluded on purpose. But four of those statuses mean something different. They mean Google is aware of your content and has decided, for now, not to include it.
I read these reports for a living, and the single most expensive mistake I see site owners make is treating all four the same way, usually by pressing Request Indexing on everything and waiting. Each status is a different failure at a different point in the pipeline, and each one has a different fix.
| Status | What it means | The usual cause |
|---|---|---|
| URL is unknown to Google | No processed record of the URL exists | Discovery failure, wrong property, or a record Google let go |
| Discovered, currently not indexed | Google knows the URL but has not crawled it | Crawl priority: weak internal links, low site standing |
| Crawled, currently not indexed | Google fetched the page and chose not to store it | Thin or duplicate content, low perceived value |
| Dropped out of the index | A previously indexed page was removed | Site changes, server trouble, quality reassessment |
Each of these has a full guide behind it, because the fix genuinely changes depending on which one you are looking at. Here is the short version of all four.
Status 1: URL is unknown to Google
The most unsettling one, because everything else about the page seems fine. It loads, you can send the link to a friend, and Search Console says Google has never seen it.
Before assuming the worst, check that you are inspecting the URL under the right property. Http and https, www and non-www are different properties, and property mismatches cause more false alarms here than real discovery failures do.
If the property is right, this status means one of two very different things: a new page Google has not discovered yet, or an old page Google crawled long ago and has since let go of. The Performance report separates them. If the URL ever recorded impressions, Google knew it and forgot it, and you are fixing crawl demand, not discovery. The full test order is in the unknown-to-Google guide.
Status 2: Discovered, currently not indexed
Google has your URL in a queue and keeps deciding other things matter more. People reach for crawl budget as the explanation, and on most sites it is the wrong one: below hundreds of thousands of URLs, Google is not short of capacity, it is short of reasons to prioritize your pages.
What actually holds pages here is weak internal linking and low overall trust in the domain. A page nothing links to sends a signal that nobody, including you, thinks it is important. The mechanics and the fixes are in the discovered guide.
Status 3: Crawled, currently not indexed
This one stings more, because Google did not skip your page. It visited, read the content, and decided against storing it. Crawling and indexing are two separate decisions, and this status is the proof: your page passed the first test and failed the second.
Across the backlogs I open, this is the biggest bucket by far. The causes are thin content, near-duplicates, and pages that do not offer enough beyond what is already indexed on the same topic. Fixing it almost never means resubmitting. It means changing the page, then submitting once. The patterns and what actually moves them are in the crawled-not-indexed guide.
Status 4: pages that dropped out of the index
Indexing is a lease, not a purchase. Google re-crawls and re-judges every stored page, and a page that stops justifying its slot loses it. Nobody gets an email. Traffic sags, a customer mentions they could not find you, and by the time someone opens Search Console the indexed count has been sliding for two months.
The causes follow a predictable order: something changed on the site, the server started struggling, or the content got re-judged against a bar that moves every year. The full checklist is in the dropped-pages guide.
How long does fixing any of this take?
Every article on indexing speed gives the same non-answer: it depends. The honest version: on an established site in good standing, a new or fixed page typically gets picked up within hours to a few days. On a young site, weeks is normal. And a page held back by a real quality problem does not index on any timeline until the cause is fixed. The tracked timelines are in how long Google takes to index.
One thing that does not speed anything up is repeated manual submission. Request Indexing genuinely helps a new or genuinely changed page get fetched sooner. It does nothing for a page Google already evaluated and declined, because it just re-runs the same evaluation. The boundary is drawn precisely in the Request Indexing guide.
Why store owners see these statuses most
Product catalogues are the least favorable shape for indexing: many URLs, similar templates, descriptions pasted from a manufacturer feed. Google samples a catalogue rather than committing to all of it, and keeps a fraction.
Two catalogue jobs from my case studies show both ends of that arc: a pet products store now at 75 of 75 URLs indexed and a college dorm store at 295 of 295, and neither started anywhere near full coverage. The store-specific version of this diagnosis, including the settings that quietly block Google, is in the Shopify indexing guide.
Read the trend before you panic
Not every scary chart in Search Console reflects reality. Google confirmed a logging error that inflated impression counts from 13 May 2025 to 27 April 2026, almost a year of distorted data, and the correction rolling out in April made many accounts drop 20 to 40 percent of their impressions overnight, as documented by SEO Sherpa and Vizup. Clicks were never affected. So an impressions-only dip around those dates is bookkeeping, not lost visibility.
Some drops are real. If clicks on a page you care about fall to zero and stay there, inspect that URL the same day: deindexation, a broken canonical, or a technical error are the usual finds. For more than a handful of URLs, run the list through the free bulk index checker and get Google’s own verdict on each one instead of guessing from a chart.
Match the fix to the status
The whole point of naming these four: a discovery problem needs links and a sitemap, a quality rejection needs a better page, an unknown URL needs the property checked first, and a dropped page needs whatever changed found and reversed. A generic checklist applied to the wrong status wastes weeks.
That diagnosis is the first step of every indexing job I take, and on messier sites it grows into a full audit. If you would rather skip straight to knowing which status is yours and why, send me the site. The diagnosis is free, usually within a day, and it comes back in plain English.