July 23, 2026
Why Isn't Google Indexing My Page? 8 Common Reasons
You publish a page, wait a few days, search for it by name, and it's just... not there. Here are the 8 most common reasons, roughly in the order worth checking them.
1. An accidental noindex tag
The single most common cause. Somewhere in the page's <head>, a tag like this tells Google not to index it:
<meta name="robots" content="noindex">
This happens more often than you'd think — a staging-site setting that never got removed before launch, a CMS default that got left on, or a plugin setting flipped by mistake. Check the page's source code (right-click → View Page Source) and search for "noindex."
2. A noindex header you can't even see in the page source
This one's sneakier: some servers send a X-Robots-Tag: noindex in the HTTP response header itself, completely invisible in the page's visible HTML. You won't find this by viewing source — you need to check the actual response headers, or use a crawler that reads them for you.
3. robots.txt is blocking the page
Your site's robots.txt file can disallow entire folders or specific URLs from being crawled at all. If Google can't crawl a page, it generally can't index it either. Check yoursite.com/robots.txt directly and look for a Disallow rule that matches the page's path.
4. The canonical tag points somewhere else
A canonical tag tells Google "this other URL is the real, authoritative version — index that one instead." If a page's canonical tag points to a different URL (sometimes by mistake, sometimes left over from a template), Google will often index the canonical target instead of the page itself.
5. The page is an orphan — nothing links to it
If no other page on your site links to it, and it's not properly submitted through your sitemap, Google may simply never find it. Pages that exist only because someone knows the direct URL are much less likely to get crawled, let alone indexed.
6. Google sees it as thin or duplicate content
Google doesn't index every page it crawls. If a page has very little unique content, or looks substantially similar to another page on your site, Google may crawl it, decide it's not worth including, and quietly leave it out of the index. This is a judgment call on Google's end, not a technical block — which makes it one of the harder ones to diagnose.
7. The page returns an error, or redirects in a loop
A 404, a 500 server error, or a redirect chain that never resolves cleanly all prevent indexing for the obvious reason: Google can't index a page it can't successfully load.
8. It just hasn't been crawled yet
Sometimes the honest answer is patience. Brand-new pages, especially on smaller or newer sites, can take days to weeks to get crawled at all — Google prioritizes crawling based on a site's overall authority and how often it's updated. If the page is genuinely new, this may resolve itself.
How to actually check which one it is
Google Search Console's URL Inspection tool is the most direct way to ask Google exactly what it thinks about a specific URL — whether it's indexed, and if not, why. Paste in the URL and it will usually tell you plainly: blocked by robots.txt, marked noindex, or "discovered, not indexed" (often a sign of the thin-content or crawl-priority issue).
For checking an entire site at once rather than one URL at a time, a full crawl will flag noindex tags, robots.txt blocks, broken canonical targets, and orphan pages all in a single pass — worth running before you spend time guessing page by page.
More from the blog
What Are Orphan Pages? Why They're Quietly Hurting Your SEO
Technical SEO Checklist: 15 Things to Check Before You Hit Publish
How to Fix a Broken Canonical Tag (Step-by-Step)
What's a Good Core Web Vitals Score in 2026? (LCP, INP, CLS Explained)
10 Claude AI Tips That Actually Change How You Work (2026 Guide)