Discovered vs Crawled, Currently Not Indexed: What Each Search Console Status Means and How to Fix It
The short answer
Discovered, currently not indexed means Google knows the URL exists but has not fetched it, which is a crawl priority problem. Crawled, currently not indexed means Google fetched the page, read it, and decided not to keep it, which is a page value problem. Submitting the URL again fixes neither.
Ishtiaq Turi
Founder, SwiftIndex
The difference in one sentence
Discovered means Googlebot has not visited yet. Crawled means it visited and was not impressed.
That sounds small and it decides everything you do next. One is about getting Google to show up. The other is about what it found when it did. People see the word indexed in both and try the same fix for both, which is usually resubmitting the URL, and that does nothing in either case.
Discovered, currently not indexed
Google found the URL, usually in your sitemap or a link, and put it in the queue. It has not fetched it. In URL Inspection the last crawl date will be empty.
What causes it
- The page is an orphan. Its only route in is the sitemap. This was our case exactly. Search Console listed the sitemap as the sole referring URL and the page sat uncrawled for weeks.
- The domain has little crawl budget. New sites with few links get a handful of fetches a week, and new pages lose that competition to the homepage.
- Too many similar URLs at once. Publishing hundreds of near identical pages makes Google sample rather than fetch them all.
- Server responses are slow. If the site is slow to answer, Google reduces crawl rate to avoid causing problems.
How to fix it
- 1Link the page from somewhere Google already crawls. The homepage, a category page, or a recent post. This is the single highest value fix and it is usually a five minute change.
- 2Check the Referring page field in URL Inspection afterwards. If it still shows only the sitemap, the link is not being seen, possibly because it only appears after JavaScript runs.
- 3Use Request Indexing on the page once. Not repeatedly.
- 4If it affects hundreds of pages, the issue is domain level crawl budget. That is fixed by earning links and publishing fewer, better pages, not by submission.
Crawled, currently not indexed
Googlebot fetched the page, rendered it, read it, and chose not to put it in the index. There will be a real last crawl date in URL Inspection.
This one stings more, because the mechanics all worked. Nothing is broken. Google looked at the page and judged it not worth keeping.
What causes it
- The page duplicates something. Another page on your site, or somewhere else, covers the same ground. Google keeps one version.
- Thin content. A page that is mostly navigation, a short stub, or a template with one variable changed.
- Doorway style pages. Sets of pages that exist to catch search variants rather than to be read. Google's systems are built to spot this pattern.
- Low site level trust. On a new domain, Google is more willing to skip borderline pages than it would be on an established one.
How to fix it
- 1Ask honestly what this page offers that the top results for its topic do not. If the answer is nothing, no amount of submission will help.
- 2Merge it. Several thin pages on one topic almost always work better as one substantial page with a redirect from the others.
- 3Add what is genuinely missing: specifics, data, images, a real answer to the question the title implies.
- 4Check the rendered HTML in URL Inspection. If your content arrives via JavaScript and Google's render is nearly empty, it judged an empty page.
- 5Then wait. Re-crawling happens on Google's schedule, and it is often weeks before a reassessment shows up.
Every common status, and what to do
| Status | What Google did | Likely cause | Fix |
|---|---|---|---|
| URL is unknown to Google | Never heard of it | Not in any sitemap, no links pointing to it | Add to sitemap, link internally, inspect once |
| Discovered, currently not indexed | Queued, never fetched | Orphan page, or low crawl budget | Link from a crawled page |
| Crawled, currently not indexed | Fetched and declined | Thin, duplicate, or low value | Improve or merge the page |
| Duplicate without user-selected canonical | Chose another page over this one | Near identical content elsewhere | Add a canonical, or differentiate the page |
| Duplicate, Google chose different canonical | Overrode your canonical | Your canonical points somewhere Google disagrees with | Check internal links and sitemap agree with your canonical |
| Excluded by noindex tag | Obeyed your instruction | A noindex meta tag or header on the page | Remove the tag, then request indexing |
| Blocked by robots.txt | Was not allowed to fetch | A Disallow rule matches the URL | Fix robots.txt |
| Soft 404 | Fetched a page that looks empty | Empty results page, or a not found page returning 200 | Return a real 404, or add real content |
| Page with redirect | Followed it elsewhere | URL redirects, so it is not indexable itself | Submit the destination URL instead |
| Submitted and indexed | It is in | Working as intended | Nothing |
Why pushing harder does not move either status
Worth saying plainly, because it is the reflex and I had it too.
We pushed one page to Google's Indexing API around twenty times. Every push was accepted with a 200. That page's status never changed from unknown, and its last crawl date stayed empty the entire time. Re-notifying Google about a URL it has already deprioritised does not raise its priority.
Discovered is fixed by giving the page a route in from somewhere Google already goes. Crawled but not indexed is fixed by making the page worth keeping. Neither is fixed by telling Google again.
The full set of measurements behind that is in our write up of what 30 submissions actually did, and the step by step version of the fixes is in the new site indexing checklist.
Frequently asked questions
What does discovered, currently not indexed mean?
Google knows your URL exists, usually from a sitemap or a link, but has not fetched it yet. The last crawl date in URL Inspection will be empty. It is a crawl priority problem, most often caused by the page being reachable only from the sitemap.
What does crawled, currently not indexed mean?
Googlebot fetched and read your page, then decided not to add it to the index. Nothing is technically broken. It usually means the page is thin, duplicates existing content, or does not add anything to what is already ranking.
How long does discovered, currently not indexed last?
There is no fixed period. Pages can sit in that state indefinitely if nothing changes. Ours stayed there for weeks with repeated Indexing API pushes. Adding an internal link from a page Google already crawls is what changes the outcome.
Should I resubmit a URL that is not indexed?
Once, after you have changed something. Repeated submission of an unchanged URL does not work. We pushed one page around twenty times through the Indexing API with every push accepted, and Google never crawled it.
Is crawled but not indexed a penalty?
No. It is a judgement about the individual page, not an action against your site. Other pages on the same domain can index normally at the same time.
Ishtiaq Turi
Founder, SwiftIndex
I build and run SwiftIndex. Every number in these posts comes from our own production database and Search Console property, not from a survey or a competitor's blog. Where our tool failed to do something, the post says so.