A page usually stays unindexed for one of five reasons: a noindex tag, a robots.txt block, a canonical tag pointing elsewhere, Google judging it duplicate or thin, or Google simply hasn’t crawled it yet because no other page links to it. Run it through Search Console’s URL Inspection tool first, the exact exclusion reason is listed right there, no guessing required.
Start With URL Inspection, Not Guesswork
Paste the exact URL into Search Console’s URL Inspection tool. It returns one of a short list of official statuses. Match yours against the table below before reading further, it points you straight to the right fix.
| Search Console Status | What It Means | Jump To |
|---|---|---|
| Excluded by “noindex” tag | You (or a plugin/setting) told Google not to index it | Reason 1 |
| Blocked by robots.txt | Crawlers can’t even reach the page | Reason 2 |
| Alternate page with proper canonical tag | Google is indexing a different URL instead | Reason 3 |
| Duplicate, Google chose different canonical / Crawled, not indexed | Google sees it as low-value or duplicate content | Reason 4 |
| Discovered, currently not indexed | Google knows it exists but hasn’t crawled it yet | Reason 5 |
Reason 1: A Noindex Tag Is Telling Google to Skip It
View the page’s source code (or check your SEO plugin’s page-level settings) for a meta name="robots" content="noindex" tag. This is the single most common cause on freshly launched or migrated sites, a “discourage search engines” setting under WordPress → Settings → Reading gets left on after launch, or a page-level noindex toggle gets flipped by accident during editing.
Reason 2: Robots.txt Is Blocking the Crawler
Visit yourdomain.com/robots.txt directly and look for a Disallow rule matching the page’s path. A single misplaced line can quietly block an entire folder. See our full breakdown in robots.txt explained for how to read and fix this file safely.
Reason 3: The Canonical Tag Points to a Different URL
If the page’s canonical tag names a different URL, you are explicitly telling Google “index that one instead, not this one.” This is common after a URL structure change, an HTTP-to-HTTPS migration, or a www/non-www inconsistency where the canonical was never updated. Read what a canonical tag actually does and how to check it for every important page.
Reason 4: Google Sees It as Duplicate or Thin Content
Google indexes what it judges worth showing. A page that closely mirrors another page on your site, or that is too short and generic to answer a real query, often gets crawled but deliberately left out of the index. This shows as “Crawled, currently not indexed” in Search Console, technically fine, editorially not good enough yet. Fixing this is about depth and distinctiveness, not word count for its own sake, see duplicate content: what causes it and how to fix it and content depth vs content volume for what “good enough” actually looks like.
Reason 5: The Page Is an Orphan With No Internal Links
Google mostly discovers new pages by following links from pages it already knows about. A page with zero internal links pointing to it, sometimes called an orphan page, can sit undiscovered for weeks even if it’s technically perfect. Link to it from at least one relevant, already-indexed page, and make sure it’s included in your XML sitemap. Our guides on internal linking strategy and what a sitemap does cover both fixes.
How Long Indexing Actually Takes
For an established site with reasonable authority, a new page is typically indexed within a few days to two weeks once it’s crawlable, linked internally, and included in the sitemap. Brand-new domains with little authority can take longer, sometimes a month or more, simply because Googlebot visits less often. That is a crawl-frequency issue, not a quality problem, patience combined with internal links speeds it up more than repeated indexing requests do.
Requesting Indexing Manually
Once the underlying cause above is fixed, use the “Request Indexing” button inside the same URL Inspection tool. It nudges Google to recrawl sooner, but it will not override a noindex tag, a robots.txt block, or a canonical pointing elsewhere, those have to be fixed first or the request simply repeats the same result. For a full pre-publish checklist that prevents this from happening again, see our technical SEO checklist and on-page SEO checklist.
Still stuck after working through all five reasons? That usually points to a deeper technical or crawl-budget issue worth a proper audit, our SEO services start there.
If your pages are discovered but not indexed and you suspect the sitemap itself is the bottleneck, see our dedicated guide on why a sitemap sometimes will not crawl at all for the fetch-error and crawl-budget checks specific to that report.