Why Is My Page Not Indexed on Google? 12 Causes and Fixes

Last updated July 16, 2026 · Ranked from most to least common, with the fix for each.

A page that is not in Google's index cannot rank for anything, no matter how good it is. Before you touch anything, confirm the page is actually unindexed, then walk this list from the top. It is ordered by how often each cause turns out to be the real one.

First: check properly

Open Google Search Console, paste the full URL into the URL Inspection bar at the top, and read the verdict. That is the authoritative answer, straight from Google's index. The site: search operator is a rough approximation at best; it misses indexed pages and shows stale ones, so never diagnose from it alone.

Search Console will usually name the status directly, and two of them are so common they have their own guides: "Crawled - currently not indexed" (Google read the page and declined, a content problem) and "Discovered - currently not indexed" (Google has not even crawled it, a priority problem). If you see either, go to those guides; otherwise, continue here.

The 12 causes

1. The page is too new and was never submitted

Google discovers pages by recrawling links and sitemaps on its own schedule. A new page on a small site can wait weeks just to be noticed. Fix: submit it: URL Inspection tool for one page, sitemap with an accurate lastmod for the site, or an automatic indexing service that submits every new page within minutes of publishing.

2. Thin or duplicate content

Google read the page and decided it adds nothing the index does not already have. This is the #1 verdict-type cause. Fix: add unique substance or consolidate weak pages into one strong one. Details in the Crawled-not-indexed guide.

3. No internal links (orphan page)

If nothing on your own site links to the page, you have told Google it does not matter. Fix: link to it from your homepage or strongest relevant pages with descriptive anchors.

4. A noindex tag

One meta tag, <meta name='robots' content='noindex'>, silently removes a page from consideration. Theme settings, SEO plugins, and staging leftovers plant these constantly. Fix: view source, search for "noindex", remove it, resubmit. URL Inspection reports this explicitly as "Excluded by noindex tag".

5. Blocked by robots.txt

A Disallow rule stops Googlebot from crawling the page at all. Fix: check yourdomain.com/robots.txt and Search Console's robots.txt report. Note the trap: robots.txt blocks crawling, not indexing, so a blocked URL can appear in results with no description; for true exclusion use noindex, and for inclusion remove the block.

6. Canonical points elsewhere

If the page's canonical tag names a different URL, you asked Google to index that one instead. CMSs and page builders set stray canonicals more often than people think. Fix: make the canonical self-referencing on pages you want indexed. URL Inspection shows "Google chose different canonical" when Google overrode you.

7. Redirects or soft 404s

A URL that redirects, returns an error, or renders a near-empty "nothing here" page will not be indexed as itself. Fix: make the URL return a real 200 page with substance; URL Inspection's live test shows what Googlebot actually received.

8. Site is too new, with no authority

Brand-new domains index slowly across the board because nothing links to them yet. Fix: a few legitimate external links (business profiles, directories, partners, social profiles) plus direct submission accelerate the cold start dramatically.

9. Crawl budget consumed by junk URLs

Faceted navigation, filters, and parameter pages can generate millions of URLs that soak up Googlebot's time on large sites. Fix: block the generators in robots.txt, noindex the leftovers, keep the sitemap canonical-only. See the Discovered-not-indexed guide.

10. JavaScript-only content

If the page is blank until a JS app boots, indexing depends on Google's second rendering pass, which is slower and less forgiving. Fix: server-side render or pre-render pages that matter for SEO; test with URL Inspection's "View crawled page" to see the HTML Google got.

11. Slow or unreliable server

Googlebot backs off from sites that respond slowly or error under crawl load, delaying everything. Fix: get response times into the low hundreds of milliseconds; check Crawl Stats in Search Console for average response time and error trends.

12. Manual action or legal removal

Rare, but terminal until resolved. Fix: Search Console's Manual actions and Security issues reports tell you if this is the case. If they are clean, your issue is on this list somewhere above.

The general recovery sequence

  1. Diagnose with URL Inspection, not guesses.
  2. Fix the named blocker (tag, robots, canonical, content).
  3. Strengthen internal links to the page.
  4. Resubmit the page and update the sitemap lastmod.
  5. Verify the status a few days later. Repeat only after changing something real.
Honesty box: no tool can force Google to index a page, and anyone promising guaranteed inclusion is describing submission, not indexing. What automation legitimately buys you: instant submission the moment you publish, coverage of every page without manual work, and verified status so you know the truth instead of assuming.

Automate the boring parts

Zeneth Indexer handles causes #1 and the verification loop end to end: it watches your sitemap every 10 minutes, submits new and changed pages through the official Google Indexing API (plus Bing, Yandex, Naver, and Seznam free via IndexNow), verifies each page against Google Search Console data, and alerts you when a page indexes or gets stuck for 7 days. The content and technical fixes above stay your job; everything mechanical becomes ours.

Know the real status of every page

Auto-submit in 10 minutes, verify with Search Console data, get alerted on stuck pages. Credits from $3, no subscription.

Get Started →

Related reading