Why Isn't My Page Indexed by Google? 9 Common Reasons

Your page is not indexed because Google either could not crawl it, was told not to index it, or decided it was not worth keeping. Those three buckets cover nearly every case. This guide walks through nine concrete reasons, how to confirm each one, and what to change. Once you fix the cause, URL Indexer can submit the corrected URL to Google so it gets re-crawled instead of waiting in line.

Start by checking the page in Google Search Console's URL Inspection tool. It tells you the current index status, the canonical Google chose, and whether crawling was allowed. Most of the fixes below are confirmed or ruled out in that one report.

Is a meta noindex tag blocking your page?

A meta noindex tag is the single most common reason a crawlable page stays out of the index, because it explicitly tells Google to drop the page. Google can crawl the page fine, read the tag, and then leave it out on purpose. Check the page source for <meta name="robots" content="noindex"> or an X-Robots-Tag: noindex HTTP header. In WordPress, this is often the 'Discourage search engines' setting or an SEO plugin toggle left on after launch.

Fix it by removing the noindex directive, then reload the page and confirm the tag is gone. Remember that noindex must be crawlable to work both ways: if you also block the page in robots.txt, Google may never see that you removed the tag.

Is robots.txt blocking the crawl?

A robots.txt rule that disallows the URL stops Google from crawling it, which usually keeps it out of the index. robots.txt blocks crawling, not indexing, so a blocked URL can still appear in results with no description if other pages link to it, but most blocked pages simply never get indexed. Visit yourdomain.com/robots.txt and look for a Disallow line that matches the path.

Remove or narrow the Disallow rule so the page is allowed, then test the path in Search Console's robots.txt report. Do not use robots.txt to keep a page out of the index. Use meta noindex for that, and leave the page crawlable so Google can read the directive.

Is your canonical tag pointing somewhere else?

A canonical tag that points to a different URL tells Google to index that other URL instead of this one. If your page declares <link rel="canonical"> aimed at the homepage, a parameter-stripped version, or a near-duplicate, Google may index the target and skip the page you care about. URL Inspection shows both your declared canonical and the canonical Google actually selected, so compare the two.

Set the canonical to the page's own URL when it should stand on its own. If Google picked a different canonical despite your tag, it judged another page more representative, which usually means the two pages are too similar. Differentiate the content or consolidate them. Our guide to noindex, robots.txt, and canonical conflicts covers how these three signals interact when they disagree.

Is the content thin or duplicate?

Google routinely declines to index pages it sees as thin or duplicate, because they add nothing already in the index. This shows up in Search Console as 'Crawled, currently not indexed' or 'Duplicate without user-selected canonical'. Boilerplate template pages, near-identical product variants, and short auto-generated pages are the usual culprits.

• Add substantive, specific content that answers a real query rather than restating a heading.
• Consolidate near-duplicates into one strong page and redirect or canonical the rest to it.
• Give each page a distinct title, intro, and purpose so it is not interchangeable with siblings.

If you keep seeing 'Crawled, currently not indexed', read our breakdown of what crawled currently not indexed means for the full diagnostic path.

Is the site brand new?

A brand-new site or page often takes time simply because Google has not crawled it yet and has little trust signal to prioritize it. New domains have no crawl history, few or no inbound links, and no track record, so discovery and indexing can lag by days or weeks. This is normal and not a defect.

Submit and verify an XML sitemap, earn a few real internal and external links to the page, and request indexing. Crawlers often visit within a few days once they find the URL, and confirmed indexing can take days to a couple of weeks. Submitting the URL directly speeds up discovery instead of waiting for the next organic crawl.

Could crawl budget be the problem on a large site?

Crawl budget is rarely the issue for small sites, but on large sites with tens of thousands of URLs Google may not reach every page often enough. If low-value, duplicate, or parameter URLs eat the crawl, important pages get visited slowly or skipped. You can spot this in the Crawl Stats report and in server logs showing where Googlebot spends its time.

Reduce crawl waste: block or canonicalize faceted and parameter URLs, fix redirect chains, keep your sitemap clean and current, and improve internal links to priority pages. A leaner site lets Google spend its crawl on the URLs that matter.

Is the page an orphan with no internal links?

An orphan page has no internal links pointing to it, so Google has no path to discover or re-crawl it. If the only way to reach a URL is by typing it directly, crawlers may never find it through normal browsing. Run a site crawl with a tool like Screaming Frog and compare crawled URLs against your sitemap to surface orphans.

Link to the page from relevant existing pages, your navigation, or a hub page, and include it in your sitemap. Internal links also pass relevance signals, so a well-linked page is both easier to find and more likely to be judged worth indexing.

Is Google treating the page as a soft 404?

A soft 404 is a page that returns a 200 OK status but looks empty or like an error to Google, so it is not indexed. Thin search-results pages, empty category pages, 'no products found' states, and pages that say 'not available' commonly trigger this. Search Console flags them under the 'Soft 404' issue in the Pages report.

Either give the page real content so it earns indexing, or return a proper 404 or 410 status if it genuinely has nothing to offer. Do not serve a near-empty 200 page and expect Google to keep it.

Are blocked resources or JavaScript hiding your content?

If your main content only appears after JavaScript runs and Google cannot fetch the scripts or data it needs, the rendered page can look empty and stay unindexed. Crawling, rendering, and indexing are distinct steps: Google may crawl the HTML but render a blank page if the JS, CSS, or API calls are blocked by robots.txt or fail to load. Use the URL Inspection 'View crawled page' and screenshot to see what Google actually rendered.

Make sure robots.txt does not block your JS, CSS, or content APIs, and serve meaningful content in the initial HTML where you can through server-side rendering or static generation. If Google can read your content without running scripts, you remove an entire class of indexing failure.

What to do after you fix the cause

1. 1Confirm the fix is live by reloading the page and re-checking the source, headers, and robots.txt.
2. 2Run URL Inspection again in Search Console to verify the page is now crawlable and indexable.
3. 3Request indexing or submit the URL so Google re-crawls the corrected page instead of waiting for the next organic visit.
4. 4Track the outcome over the following days, since confirmed indexing can take days to a couple of weeks even after a clean fix.

Fixing the cause is step one. Getting Google back to the page is step two. URL Indexer submits a corrected URL (or a whole batch pasted as a list) and tracks which ones get indexed on a live per-batch status page, with follow-up email reports at 3, 7, and 30 days. The free tier covers up to 10 URLs a day with no signup and no credit card. Google still makes the final call on what gets indexed, but a clean page plus a fresh submission gives it every reason to say yes.