Why Isn’t My Page Indexed? 12 Reasons (and How to Fix Them)

Before a page can rank for anything, it has to be indexed. Google’s pipeline has three stages: it discovers a URL (through links or your sitemap), crawls it (fetches the page), and finally indexes it (stores it and makes it eligible to appear in results). A page can fall out at any stage, and when it does, it earns exactly zero search traffic, no matter how good the content is.

Here are the twelve reasons pages actually get stuck, grouped by what’s really going on: you told Google no, Google said no, something technical broke, or Google never found the page at all.

You told Google not to index it

1. A noindex tag

A noindex robots meta tag (or X-Robots-Tag header) is an explicit instruction to stay out of the index, and Google obeys it. These often ship by accident: staging settings carried to production, an SEO plugin toggle, or a theme default. Fix:remove the tag and request indexing. Check templates, not just the page, so the same tag isn’t stamped on a whole content type.

2. Blocked in robots.txt

If robots.txt disallows the URL, Google can’t crawl it. Counterintuitively, the page can still appear in results as a bare URL with no description, and if it’s blocked, Google can’t see a noindex tag on it either. Fix: only block paths with no search value (cart, admin, internal search), and never block pages you want ranked.

3. The canonical points somewhere else

A canonical tag tells Google “the real version of this content lives at that other URL.” If your page canonicalizes to a different page (common after CMS migrations or with tracking-parameter mishaps), Google indexes the target instead. Fix: every indexable page should canonicalize to itself unless you genuinely intend to consolidate.

Google chose not to index it

4. “Crawled, currently not indexed”

The most frustrating status in Search Console: Google fetched the page and decided it wasn’t worth keeping. This is a quality and usefulness judgment. Thin pages, near-duplicates, doorway-style variations, and pages with nothing new to say land here. Fix: make the page more substantial and more distinct, or merge it into a stronger page. Re-requesting indexing without changing the page rarely works.

5. Duplicate content without a clear canonical

When several URLs serve nearly the same content (filtered views, print versions, http vs https, www vs non-www), Google picks one and quietly drops the rest, and it may not pick the one you wanted. Fix: consolidate to one URL per piece of content with canonicals and redirects.

6. Soft 404s

A page that returns HTTP 200 but looks empty or error-like to Google (“no results found,” placeholder templates, near-blank pages) gets classified as a soft 404 and excluded. Fix:give the page real content, or return a proper 404/410 if it shouldn’t exist.

Something technical broke

7. Server errors and timeouts

If the page intermittently returns 5xx errors or times out when Googlebot visits, indexing stalls and previously indexed pages can drop out. Fix: check the Crawl Stats report for error spikes and fix hosting or performance issues.

8. Redirect chains and loops

URLs that bounce through multiple redirects (or loop) often never resolve to an indexable destination, and links pointing at old URLs lose their value along the way. Fix: redirect once, directly to the final URL, and update internal links to point at the destination.

9. The content only exists in JavaScript

Google renders JavaScript, but rendering is delayed, budgeted, and imperfect, and other crawlers (including most AI crawlers) are worse. If your HTML arrives effectively empty and everything meaningful is painted client-side, indexing gets slow and unreliable. Fix: server-render or statically generate any page you want indexed. This is one of the most common issues on AI-built and vibe-coded sites.

Google never found it

10. Orphan pages

A page with no internal links pointing to it is invisible to crawlers following links, and its lack of links also signals it doesn’t matter. Fix: link to every page you care about from related content and hub pages.

11. Missing from the sitemap

A sitemap won’t force indexing, but it’s how Google discovers URLs efficiently and learns when they change. Pages missing from it (or sitemaps that are stale, broken, or never submitted) slow discovery. Fix: generate the sitemap automatically from your CMS and submit it in Search Console.

12. New site, low crawl priority

Young sites with few backlinks get crawled lightly. Google simply hasn’t allocated much attention yet, so pages sit in “Discovered, currently not crawled.” Fix: patience plus fundamentals: earn a few real links, build internal structure, publish substantive content, and submit your sitemap.

How to diagnose any unindexed page in two minutes

• Inspect the URL in Search Console (URL Inspection). It tells you the exact status: whether the page was discovered, crawled, indexed, which canonical Google chose, and any blocking directive it found.
• Read the Page indexing reportfor the site-wide pattern. One unindexed page is a fluke; two hundred in “Crawled, currently not indexed” is a content-quality program.
• Match the status to the fix using the twelve reasons above, change the page, then request indexing once the underlying problem is gone.

The takeaway

“Not indexed” is not one problem; it’s a dozen different ones wearing the same symptom. Diagnose before you fix: check for directives you set yourself, then for quality judgments Google made, then for technical failures, then for discovery gaps. And make coverage a habit, not a crisis response. Sites that audit indexing monthly catch these issues while they’re still cheap to fix.