Google Not Indexing Your Pages? A Troubleshooting Guide

You published a page three weeks ago and it is still not in Google. You search for the exact title, the exact URL, even a quoted sentence from the first paragraph. Nothing. The page exists. It loads fine. But as far as Google is concerned, it does not.

The root cause is almost always one of ten things. The trick is knowing where to look first. This guide walks through each cause in order of likelihood, starting with the most common, with exact diagnostic steps and fixes.

Before you start: open Google Search Console for your property and paste the missing URL into the URL Inspection tool. That single action will immediately confirm or rule out the first three causes.

1. A Noindex Tag Is Blocking the Page

A noindex directive explicitly tells Google to keep the page out of search results. It hides in two places: a <meta name="robots" content="noindex"> tag in the HTML, or an X-Robots-Tag HTTP response header.

Diagnose: The URL Inspection tool in Search Console shows "Excluded by noindex tag" if this is the cause. You can also view page source and search for noindex, or check response headers in your browser's Network tab for X-Robots-Tag.

Fix: Remove the directive from your template, CMS settings, or server configuration. Then click "Request Indexing" in the URL Inspection tool. Re-indexing typically takes one to two weeks.

The most common way this happens: a developer adds noindex during staging and it gets merged into production. In WordPress, also check Settings > Reading for the "Discourage search engines" checkbox.

2. Robots.txt Is Blocking Crawlers

If your robots.txt disallows the URL path, Googlebot never crawls the page. No crawl, no index.

Diagnose: The URL Inspection tool shows "Blocked by robots.txt." You can also visit https://yoursite.com/robots.txt directly and look for Disallow rules matching your page path. Watch for broad rules like Disallow: /*? that unintentionally catch production pages.

Fix: Edit robots.txt to remove or narrow the disallow rule. Use an Allow directive for specific paths if needed. Then request indexing through the URL Inspection tool.

Important nuance: if the page was blocked for a long time, Google may have never crawled it. Even after allowing access, you need to submit the URL through URL Inspection to prompt discovery.

3. The Canonical Tag Points Elsewhere

A <link rel="canonical"> tag pointing to a different URL tells Google your page is a duplicate. Google indexes the canonical target and ignores yours.

Diagnose: In the URL Inspection tool, check the "Google-selected canonical" and "User-declared canonical" fields. If either shows a different URL, that is the problem. Common patterns: canonical pointing to the homepage, trailing slash mismatches, or HTTP/HTTPS mismatches.

Fix: Set the canonical to the page's own URL (a self-referencing canonical). If your CMS generates incorrect canonicals, check SEO plugin settings. Request re-indexing after correcting.

4. Thin or Low-Quality Content

Google may crawl a page and decide not to index it. In Search Console, these show up as "Crawled - currently not indexed" or "Discovered - currently not indexed."

Diagnose: Check the Pages report in Search Console (under Indexing) for your URL in either of those buckets. "Crawled - currently not indexed" means Google visited and rejected the page. "Discovered" means Google has not even prioritized crawling it.

Be honest with yourself: does the page offer substantial, original value? Product pages with only a title and price, blog posts under 200 words, or category pages with no content all struggle here.

Fix: Add depth. Provide original information, data, or perspective that visitors cannot find elsewhere. If the page is intentionally thin (a tag page, a filter page), consider adding noindex and focusing crawl budget on pages that deserve to rank.

5. Orphan Pages With No Internal Links

Google discovers pages by following links. If nothing on your site links to the page, Google may never find it or may treat it as low priority.

Diagnose: Check whether any indexed pages on your site link to the missing page. In Search Console, the Links report shows internal linking data. A quick check: run site:yoursite.com "page title" in Google to see if any of your pages reference it.

Fix: Add internal links from relevant, already-indexed pages. Related blog posts, category pages, and navigation are all good placement options. Every page you want indexed should be reachable within three clicks from the homepage.

6. Crawl Budget Issues on Large Sites

Sites with tens of thousands of pages have a finite crawl budget. If that budget gets spent on low-value URLs (faceted navigation, sort parameters, session-based URLs), important new pages may never get crawled.

Diagnose: In Search Console, go to Settings > Crawl Stats. If your crawl rate is high but important pages sit in "Discovered - currently not indexed," the budget is going elsewhere. Look for patterns in the crawled pages list: hundreds of filter/sort/pagination URLs are the usual culprit.

Fix: Block low-value URL patterns with robots.txt or noindex. Consolidate parameter-based duplicates with canonical tags. Improve server response time so Google can crawl more pages per visit.

For sites under 10,000 pages, crawl budget is rarely the issue. Look at the earlier causes first.

7. Manual Actions or Security Issues

A manual action is a penalty from Google's webspam team that can suppress your entire site or specific sections from search results.

Diagnose: In Search Console, go to Security & Manual Actions. Active penalties are listed with their reason (unnatural links, thin content, cloaking, spam). Also check Security Issues for malware or hacked content warnings.

Fix: Address the specific violation, then submit a reconsideration request. Google reviews these manually, typically within two to four weeks. For security issues: clean compromised pages, patch the vulnerability, then request a review.

8. Sitemap Not Submitted or Has Errors

A sitemap is your most direct way to tell Google what pages exist. A missing or broken sitemap will not prevent indexing on its own, but it slows discovery and can undermine Google's confidence in your site.

Diagnose: In Search Console, go to Sitemaps (under Indexing). Check that your sitemap is listed, its status shows "Success," and your new page is actually included. Common problems: sitemap returns 404, contains URLs that redirect or error, or has malformed XML.

Fix: Submit the sitemap if you have not already. Remove broken URLs, fix XML errors, and confirm your new page is listed. Verify that a Sitemap: directive in your robots.txt points to the sitemap location.

9. Page Too Slow or Returning Server Errors

If Googlebot consistently gets 5xx errors or the page times out, Google stops trying. Even intermittent server errors — the kind that uptime monitoring catches — signal unreliability.

Diagnose: The URL Inspection tool shows the last crawl result, including errors. Check Crawl Stats under Settings for overall error rates and response times. Server response times consistently over 5 seconds can prevent successful crawling.

Fix: Check server logs for the specific errors. Common causes: memory limits, database timeouts, redirect loops. Optimize server response time before worrying about front-end performance. After fixing, request a fresh crawl through URL Inspection.

10. Duplicate Content Across Your Site

When multiple pages have substantially identical content, Google picks one to index and ignores the rest. The one it picks may not be the one you want.

Diagnose: In the URL Inspection tool, check the "Google-selected canonical." In the Pages report, look for "Duplicate without user-selected canonical" or "Duplicate, Google chose different canonical than user." You can also search a unique sentence from your page (in quotes) to see which URL Google returns.

Fix: Make duplicate pages genuinely distinct, or consolidate them with canonical tags pointing to the version you want indexed. For URL variants (trailing slashes, www vs non-www), set up 301 redirects to the preferred version.

The Checklist

Work through these in order as part of your technical SEO audit. Do not skip ahead.

1. URL Inspection in Search Console. Blocked by noindex? Remove the tag.
2. Robots.txt blocking the path? Edit the rules.
3. Canonical pointing elsewhere? Correct it to self-reference.
4. Crawled but not indexed? Improve content quality and depth.
5. No internal links pointing to the page? Add them.
6. Large site with crawl budget issues? Block low-value URL patterns.
7. Manual action active? Address it and request reconsideration.
8. Sitemap missing the page or has errors? Fix and resubmit.
9. Server errors or timeouts? Fix the underlying issue.
10. Duplicate content on other pages? Differentiate or consolidate.

Most indexing problems fall into the first three categories. The URL Inspection tool alone rules them in or out within a minute.

Catching Problems Before They Cost You

Indexing issues are silent. The page still works for direct visitors. The only signal is absence: traffic from Google that never arrives. A noindex tag deployed on Monday might not show symptoms in Search Console until Thursday. By the time someone notices the traffic dip the following week, you have lost ten days of visibility.

SEO Monitor closes that gap by continuously checking your pages for noindex tags, robots.txt blocks, canonical mismatches, and sitemap presence. When a previously indexable page suddenly has a noindex directive or a canonical change, it flags the issue immediately instead of waiting for the traffic drop to surface in analytics. Catching these problems within hours rather than weeks is often the difference between a quick fix and a painful recovery.

Whatever SEO monitoring approach you take, the principle is the same: do not wait for Search Console to report the damage. By the time it shows up in the data, you are already behind.