Google Search Console’s Pages report can look alarming: a long list of URLs marked “not indexed”, with reasons such as “Crawled – currently not indexed”, “Discovered – currently not indexed”, “Excluded by ‘noindex’ tag” or “Blocked by robots.txt”.
Not every one of those URLs is a problem. Redirects, duplicates and pages you meant to hide should be excluded. The useful work is to sort the list, not to hit “Request indexing” on everything.
The 3-question triage for every URL
Open Indexing → Pages, click a reason, and inspect one example URL with the URL Inspection tool (including “Test live URL”). Then ask:
- Should this URL be in Google at all? If no — a thank-you page, a login, a filtered search, a thin tag page — make sure it is excluded on purpose and move on.
- Is there a better URL for the same content? If yes, the canonical tag, internal links and the sitemap should all point at that URL.
- If it should be indexed: is it reachable, allowed and worth indexing? Fix those in that order. A request to index a blocked or empty page will not help.
Technical blockers you can check on the live page
Some reasons are hard stops. Before you rewrite the content, confirm the live URL:
- HTTP errors (4xx/5xx). Google cannot treat an error page as the content you wanted indexed.
noindexin a meta tag or in theX-Robots-Tagheader. Common leftover: “Discourage search engines” in a CMS, or a staging setting copied to production. If the page should stay hidden, leave the tag alone.robots.txtblocking Googlebot. A leftoverDisallow: /blocks everything. Note that blocking a URL in robots.txt does not remove it from Google; to hide a page, allow crawling and usenoindex.- A canonical tag that points somewhere else. Google may index the canonical URL and leave this one out — which is correct when you meant it.
- The URL is missing from a clean sitemap. A sitemap helps discovery. It does not guarantee indexing, and it should only list canonical, 200-status, indexable URLs.
“Crawled – currently not indexed” and “Discovered – currently not indexed” are different. The first usually means Google fetched the page and judged it (often a quality or uniqueness issue). The second means Google knows the URL but has not crawled it yet, often because of crawl priority or a lot of low-value URLs competing for attention. Requesting indexing once, after you have fixed something real, is enough; repeating the request does not make it faster.
A free technical check, and a short guide for the Search Console list
There is a free checker that reads the live page, robots.txt and sitemap and reports those technical blockers. It cannot see Search Console, and it will not tell you whether Google has already indexed the page:
Open the free Not Indexed Checker
If you want the common Search Console reasons in one place — what they mean, whether to worry, and the fix in a sensible order — the Not Indexed Fix Guide is a €9 one-time PDF (4 pages):
Get the Not Indexed Fix Guide · €9
If you would rather we walk through the setup on one site with you (sitemap, robots.txt, Search Console, a short request-indexing list), the Get Indexed Sprint is €99. We do not promise that Google will index a page:
See the Get Indexed Sprint · €99
No guide can promise that a page will appear in Google. Removing a noindex tag or a robots.txt block only removes a hard barrier. What happens after that still depends on the page and on Google.
What’s the most common “not indexed” reason on sites you look after — a leftover noindex, a robots.txt rule, or “crawled, but not indexed”?
Published 15 November 2026 by PIT Toolkit.