This is the most frustrating status in Search Console, because unlike most indexing problems it does not point at anything you can fix directly. There is no broken tag, no blocked URL, no server error. Google fetched your page successfully, read it, and decided it was not worth adding to the index. That is a judgment call, and the report gives you no reasoning. Understanding what typically drives that decision is the only way to respond usefully.
What the Status Means
Google found the URL, crawled it without any technical obstacle, and chose not to index it. The page is not blocked, not broken, and not noindexed — it simply did not clear the bar.
It is worth distinguishing this from its neighbour in the report:
- Discovered – currently not indexed — Google knows the URL exists but has not crawled it yet. Usually a crawl budget or scheduling issue.
- Crawled – currently not indexed — Google has read the page and declined. Usually a quality or duplication issue.
The word “currently” is genuine. Pages do move out of this status without you doing anything, particularly on newer sites, and equally pages can fall into it months after being indexed normally.
The Real Causes, In Rough Order of Frequency
1. The Content Is Not Distinct Enough
By far the most common cause. Google’s index is not obliged to contain every page on the web, and it increasingly declines pages that add nothing to what it already has.
This catches:
- Thin pages — a few hundred words that restate what a hundred other pages say
- Near-duplicate pages, particularly programmatically generated location or variant pages
- Content assembled from other sources without original contribution
- Pages that answer a question already answered better elsewhere on your own site
The uncomfortable version of this diagnosis: if you published a page mainly because your content calendar said to, rather than because you had something specific to say, this is often the result.
2. The Site Lacks Authority
A new or low-authority domain gets less indexing generosity. The same article on a DR 70 site would be indexed immediately and on a DR 5 site may sit in this status for months.
This is not a content problem and cannot be fixed at the page level. It resolves as the domain accumulates links and trust — which is the slow part of SEO for new websites.
3. Internal Linking Is Too Weak
Orphaned pages — those with no internal links pointing at them, or only a link from a deep archive page — signal low importance. If your own site does not treat a page as worth linking to, Google reads that.
This is the most reliably fixable cause on the list, and usually the fastest win.
4. The Page Competes With Your Own Content
If you have three articles covering roughly the same query, Google may index one and leave the others here. That is keyword cannibalisation expressing itself as an indexing symptom rather than a ranking one. We cover diagnosis and consolidation in how many keywords to target per page.
5. Crawl Budget Is Being Wasted
On large sites, if Googlebot spends its allocation on parameter URLs, filtered variants, and pagination, genuinely valuable pages get deprioritised. Cleaning up crawl waste frees capacity — see our guide to robots.txt for the practical controls.
6. The Page Is Slow or Renders Poorly
Not a primary cause, but a contributing one. If content requires JavaScript execution to appear and rendering is deferred or fails, Google may see a nearly empty page. Test with the URL Inspection tool’s rendered HTML view rather than assuming. Severe performance problems compound this — see Core Web Vitals explained.
Diagnosing Your Specific Case
Work through this in order:
1. Confirm it is not technical. Use URL Inspection → Test Live URL. Check that the page returns 200, is not noindexed, is not blocked, and that the rendered HTML contains your actual content. If any of those fail, you have a different and easier problem.
2. Check the canonical. If Google selected a different canonical than you declared, the page is being consolidated rather than rejected — a different status covered in “alternate page with proper canonical tag”.
3. Search for your own content. Copy a distinctive sentence and search it in quotes. If the identical text appears elsewhere — including on your own site — duplication is your answer.
4. Count the internal links. Crawl your site and check how many internal links point at the affected URL. Zero or one is a red flag.
5. Look for a pattern. Export the full list. If the affected URLs are all tag archives, all paginated pages, or all from one template, the cause is structural rather than about individual page quality.
6. Compare against what ranks. Search the target query and read the top three results honestly. If your page is thinner, less specific, or less useful, that is the finding.
Fixing It
Improve the page substantially. Not by padding word count — by adding something the page did not have. Original data, a worked example, specific detail, first-hand experience, a genuinely useful table. A page that survives this status usually does so because it now contains something not available elsewhere.
Add internal links from strong pages. Find your best-performing existing pages and link to the affected one with descriptive anchor text, where it is genuinely relevant. This is the highest-leverage single action for most sites, and it works quickly.
Consolidate rather than improve. If three thin pages cover one topic, merging them into one strong page and 301-redirecting the others is usually better than trying to rescue all three. Fewer, better pages is a real strategy.
Prune what cannot be saved. Some pages should not exist. Returning 410 for deliberately removed low-value content is a legitimate and often effective move — see 410 vs 404 vs 301 for deleted pages.
Request indexing — once. URL Inspection → Request Indexing. This helps most on genuinely new pages. Repeatedly requesting indexing for a page Google has already declined achieves nothing; the queue is not the bottleneck, the assessment is.
Reduce crawl waste. Block parameter URLs and low-value paths so Googlebot’s budget goes to pages that matter.
Be patient where patience is the answer. On a new site, pages sitting here for weeks is normal and is not a signal that anything is wrong with them.
What Does Not Work
- Resubmitting the sitemap repeatedly. Google already knows the URL exists.
- Requesting indexing daily. The status is a quality decision, not a queue position.
- Adding words to hit a word count. Length is not the variable being assessed.
- Spinning or rewording existing content. If the substance is unchanged, the assessment will be too.
- Third-party “instant indexing” services. The Indexing API is officially limited to job posting and livestream structured data. Services claiming otherwise are unreliable at best.
Treat It as Feedback
The most useful reframe: this status is Google telling you, without diplomacy, that a page does not currently justify a place in the index. That is unwelcome but genuinely informative — it is a signal most sites never get about their weakest content.
On an established site, a handful of pages in this status is normal noise. On a new site, most of your pages may sit here for a while, and the fix is domain authority rather than page edits. The case worth acting on is when a page you believe is genuinely strong is being declined — that usually traces back to internal linking, duplication with your own content, or the page being less distinct than you thought.
Fix the linking first, because it is fast. Then be honest about the content.
If you have pages that will not index and you cannot work out why, our SEO services include full indexing diagnostics and content assessment. Get in touch with the team at blogthememachine.com, and subscribe to our newsletter below for more technical guides like this one.
