Guides for Rankpilot
Page Not Indexed: Fixing “Crawled – Currently Not Indexed” and “Discovered – Currently Not Indexed”
You published a page, waited, and it still doesn’t show up in Google. In Search Console it sits under “Why pages aren’t indexed” with a status like “Crawled – currently not indexed” or “Discovered – currently not indexed”. Neither status tells you directly what to do, and the help texts are short.
This guide explains what each status means, how to check a single URL, which fixes actually help and when a page is better left out of the index. Everything works with the free Google Search Console and a browser.
Where to find out why a page isn’t indexed
Two reports in Google Search Console give you the answer. Under Indexing → Pages you see how many URLs are indexed and, below the chart, a table “Why pages aren’t indexed” with one row per reason. Click a row to see example URLs.
For a single page, paste its full URL into the URL Inspection bar at the top. It tells you whether the URL is on Google, how Google found it, when it was last crawled, whether indexing is allowed and which canonical URL Google selected. With Test live URL you can check the current version, for example right after a fix.
“Crawled – currently not indexed”
Google has fetched the page but decided not to index it, at least for now. There’s no technical error behind it – it’s a choice. Sometimes it’s just time: new pages can sit here for a while and then get indexed. If it stays for weeks, the reason is usually that Google doesn’t see enough value in the page compared with what’s already in the index.
What helps:
- Make the page clearly useful on its own: specific information, original details, a real answer – not a short text that repeats other pages.
- Check for near-duplicates. Tag pages, filter URLs, print versions or several very similar product pages compete with each other; merge them or point them to one canonical URL.
- Link to the page from relevant, already indexed pages of your site, with a descriptive anchor text.
- Make sure the main content is in the HTML or renders reliably – the screenshot in Test live URL shows what Google sees.
- After a real improvement, use Request indexing once. Repeating the request without changing anything doesn’t help.
“Discovered – currently not indexed”
Here Google knows the URL – from a sitemap or a link – but hasn’t crawled it yet. Search Console notes that Google often reschedules the crawl because crawling the site was expected to overload the server. On small sites, the more common reason is low priority: the page has few internal links, sits deep in the structure, or the site has many URLs of mixed quality.
What helps:
- Link the page from your navigation, category pages or related articles so it isn’t only reachable via the sitemap.
- Keep your sitemap clean: only indexable, canonical URLs that return 200, with no redirects or noindex pages.
- Check Settings → Crawl stats for server errors, slow response times or a host status problem.
- Reduce crawl waste: endless filter combinations, session parameters or auto-generated pages make Google spend time on URLs that don’t matter.
Other statuses and what to do
Not every status needs fixing. Many of them simply confirm that your setup works as intended:
| Status | What it means | What to do |
|---|---|---|
| Excluded by ‘noindex’ tag | The page tells Google not to index it. | Fine if intended; otherwise remove the noindex. |
| Blocked by robots.txt | Google may not crawl the URL. | Remove the rule if the page should rank. |
| Alternate page with proper canonical tag | Google indexes the canonical version you set. | Usually nothing. |
| Duplicate without user-selected canonical | Google sees duplicates and picked one itself. | Set a canonical or merge the pages. |
| Duplicate – Google chose different canonical than user | Google ignored your canonical. | Make signals consistent: links, sitemap, redirects. |
| Soft 404 | The page looks empty or like an error. | Add real content or return a real 404. |
| Page with redirect | The URL redirects elsewhere. | Fine; link to the target URL directly. |
| Not found (404) | The page doesn’t exist. | Fine if deleted; redirect if it moved. |
| Server error (5xx) | Your server failed to answer. | Fix the server, then validate. |
Do it with RankpilotLearn more →noindex vs. robots.txt: a common trap
robots.txt controls crawling, not indexing. A URL blocked in robots.txt can still appear in Google – without a description – if other pages link to it. To keep a page out of the index, use a noindex meta tag or X-Robots-Tag header.
The catch: Google has to crawl the page to see the noindex. If you block it in robots.txt at the same time, Google never reads the tag. So for pages you want removed, allow crawling and set noindex:
<meta name="robots" content="noindex">Request indexing and validate the fix
After fixing a single important page, open URL Inspection, run Test live URL and click Request indexing. The daily quota is limited, so use it for pages that matter, not for hundreds of URLs. A request doesn’t guarantee indexing; it only puts the URL in the crawl queue.
For a fix that affects many pages, open the affected row in the Pages report and click Validate fix. Google then rechecks the URLs, which can take days to weeks. Submitting an up-to-date sitemap under Sitemaps also helps Google find changed pages. For Bing and other engines, IndexNow can announce changes quickly – Google doesn’t use it, though.
Not every unindexed page is a problem
Most sites have far more URLs than pages worth indexing: parameters, pagination, old redirects, thin tag pages, login pages. It’s normal for these to appear as not indexed. Focus on the pages you actually want people to find – your main products, services and articles – and check those first.
If an important page is fine technically but stays in “Crawled – currently not indexed”, see it as feedback on the content, not as a bug. A broader website SEO check helps you spot thin or duplicate pages across the site.
Keep an eye on your index with Rankpilot
Rankpilot is an iPhone and iPad app that is coming soon to the App Store. Connected to Google Search Console, its index watch warns you when pages drop out of the index, so you notice it without opening the Pages report every week. The website check finds technical problems with concrete fixes, and the internal links tool helps you check how your pages link to each other.
For Bing and other search engines, Rankpilot can submit URLs via IndexNow and checks your key file. The app is free; the optional Rankpilot Pro subscription adds background monitoring with alerts and history.
Frequently asked questions
What does “Crawled – currently not indexed” mean?
Google has crawled the page but decided not to index it for now. It often points to thin, duplicate or low-value content, but new pages can also simply need more time.
What does “Discovered – currently not indexed” mean?
Google knows the URL but hasn’t crawled it yet. Common reasons are low priority, weak internal linking or Google postponing crawling to avoid overloading the server.
How long does it take Google to index a new page?
It varies from a few days to several weeks. Good internal links, a clean sitemap and a request in URL Inspection can help, but there is no guaranteed time.
Does robots.txt keep a page out of Google?
No. robots.txt blocks crawling, not indexing, so a blocked URL can still be indexed if it’s linked. Use a noindex tag and keep the page crawlable so Google can see it.
Should I request indexing over and over?
No. Requesting indexing again without changing the page doesn’t speed things up, and the daily quota is limited. Improve the page first, then request it once.