If Google has crawled a page and decided not to index it, nothing else you do to that page matters. No amount of keyword optimisation, internal linking or backlink building will help a URL that is not in the index. And “Crawled — currently not indexed” is now one of the most common statuses in Search Console.
Here is how to work out why it is happening on your site, in the order I actually check things during an audit.
First, confirm what Google thinks
Open Search Console and go to Indexing > Pages. Do not skip to the fixes — read the reasons Google gives you first, because they narrow the problem enormously:
- Crawled — currently not indexed. Google found it, looked at it, and chose not to index it. This is a quality, duplication or value judgement, not a technical block.
- Discovered — currently not indexed. Google knows the URL exists but has not spent crawl budget on it. Usually a crawl-priority or internal-linking problem.
- Excluded by noindex tag. A technical block. Fast to fix, and embarrassingly common after a staging launch.
- Duplicate, Google chose different canonical. Google thinks another URL is the better version of this content.
- Alternate page with proper canonical tag. Working as intended, usually.
- Blocked by robots.txt. A crawl block, not an index block — and the two are frequently confused.
Then run URL Inspection on a specific affected page and use “Test live URL”. That tells you what Googlebot receives right now rather than what it saw last month.
The seven causes I find most often
1. The page is orphaned
Nothing on the site links to it except a paginated archive Google rarely crawls deeply. Internal links are how Google discovers pages and infers their importance — a page with zero internal links is telling Google it does not matter. This is by far the most common cause on blogs, and the fix costs nothing. More on that in internal linking.
2. A stray noindex tag survived launch
Staging sites are usually set to noindex, and it does not always get removed. Check the raw HTML, not the plugin’s settings screen, and check the HTTP headers too — X-Robots-Tag: noindex is invisible in the page source.
3. robots.txt is blocking the crawl
A blocked URL cannot be crawled, so it usually cannot be indexed. Worse, blocking resources like CSS and JavaScript can stop Google rendering the page properly, which makes it look empty and therefore not worth indexing.
4. The content is too thin or too similar to something else
If you have forty pages that are 80% identical — location pages with the city swapped, product variants, tag archives with one post — Google will pick one and ignore the rest. This is the honest explanation behind most “Crawled — currently not indexed” reports, and no technical fix will solve it. The content has to genuinely differ.
5. Canonical tags pointing somewhere else
Self-referencing canonicals are the default for a reason. A canonical pointing at the homepage, at a parameterised version, or at a page that itself redirects, tells Google to index something other than the URL you care about.
6. Crawl budget spent on rubbish
Faceted navigation, session parameters, internal search results, calendar archives and attachment pages can generate thousands of low-value URLs. Google crawls those instead of your new content. This is mostly a large-site problem, but WordPress sites with unmanaged archives hit it too — see WordPress SEO.
7. The site is too new or has no authority yet
On a brand-new domain with no external links, Google is conservative. There is no trick here. Publish genuinely useful pages, link them internally, get the sitemap submitted, and earn a few real links.
The one that catches everyone
Check which sitemap is actually submitted in Search Console. Yoast generates /sitemap_index.xml; other setups use /sitemap.xml or /wp-sitemap.xml. Submitting the wrong filename produces a sitemap that reports “Success” while discovering zero pages — so it looks fine and does nothing. I have found this on live client sites more than once, including on this one.
A fix order that works
- Remove hard blocks first: noindex tags, X-Robots-Tag headers, robots.txt disallows
- Fix canonicals so every indexable page self-references
- Submit the correct XML sitemap and confirm the discovered-page count is not zero
- Build real internal links to the affected pages from relevant existing content
- Consolidate or genuinely differentiate near-duplicate pages
- Reduce crawl waste from parameters and low-value archives
- Only then request indexing, and only for pages you have actually changed
What not to do
Do not mass-submit URLs through the indexing request tool and treat that as a strategy. It is a nudge, not a fix — if the underlying reason is thin content or no internal links, the page will drop out again. Do not use indexing services that promise instant inclusion, and do not add the same page to your sitemap fifteen times.
Frequently asked questions
Why does Google say “Crawled — currently not indexed”?
Google fetched the page, evaluated it, and decided it was not worth adding to the index. That is usually a judgement about thin, duplicative or low-value content, or a signal problem — the page has no internal links and nothing indicates it matters. It is rarely a technical block, because a technical block gets its own status.
How long does it take for a page to get indexed?
A well-linked page on an established site can be indexed within hours to a few days. On a new domain with little authority it can take weeks, and some pages are never indexed. Requesting indexing in Search Console can speed up discovery but will not overcome a content or internal-linking problem.
Does requesting indexing in Search Console guarantee it?
No. It asks Google to prioritise crawling that URL. Whether it gets indexed still depends on whether Google judges it worth indexing.
Can too many pages hurt indexation?
Yes, indirectly. Large numbers of thin or near-duplicate URLs consume crawl budget and dilute the perceived quality of the site, which makes Google more selective about what it indexes from your domain.
How do I know if a page is orphaned?
Crawl the site with a tool that reports internal inlink counts and look for pages with zero. In Search Console, pages that only appear via the sitemap and never via internal links are a strong hint. Ahrefs Site Audit reports this directly as “Orphan page”.
Need this diagnosed on your own site?
Indexation problems are usually cheap to fix once you know which of the seven causes above applies. If you would rather not guess, that is exactly what a technical SEO audit is for — or just send me the domain and I will tell you what I can see.
