Common reasons Google isn't indexing your pages

What each "Page Not Indexed" status in Google Search Console means and whether action is needed.

Overview

Seeing "Page Not Indexed" in Google Search Console doesn't always mean something is wrong — but it does mean Google is not including that URL in search results. Some statuses require action; others are expected behavior. This article explains each one.

Indexing issue reference

Server error (5xx)

Your server returned a 500-level error when Google tried to access the page. This prevents indexing until the server error is resolved. Use a web debugging tool such as Google Lighthouse to diagnose the issue.

Redirect error

Google encountered a redirect problem — a chain that was too long, a redirect loop, a redirect URL that exceeded the maximum URL length, or a bad or empty URL in the chain. Debug using a web tool such as Lighthouse to identify where the chain breaks. See [How to fix 404 Page Not Found errors on your website in Presence®] for guidance on setting up redirects correctly.

URL marked "noindex"

Google found a noindex directive on the page and respected it. If you don't want this page indexed, no action is needed. If you do want it indexed, remove the noindex directive.

Soft 404

The page returns a user-friendly "not found" message but not an actual 404 HTTP response code. Google treats this as a soft 404 and won't index it. For pages that are genuinely not found, return a proper 404 response code. Use the URL Inspection tool in Google Search Console and click View Tested Page to see how Google is rendering the page.

Blocked due to unauthorized request (401)

The page requires authorization to access and Google was blocked. If you want Google to index this page, remove the authorization requirement or explicitly allow Googlebot access. Verify by visiting the page in an incognito browser window.

Not found (404)

The page returned a 404 error. Google may have discovered the URL from a link on another page or from a page that previously existed. 404 responses are not always a problem — if the page was intentionally removed, no action is needed. If the page has moved, set up a 301 redirect to the new location.

Blocked due to access forbidden (403)

The server returned a 403 error, which typically means credentials were provided but access was denied. Since Googlebot never provides credentials, this error usually means your server is incorrectly blocking non-authenticated users. Allow non-signed-in access or explicitly permit Googlebot requests to resolve this.

URL blocked due to other 4xx issue

A 4xx error not covered by the other categories above. Use the URL Inspection tool in Google Search Console to debug the specific error.

Blocked by page removal tool

The page is currently blocked by a URL removal request submitted through Google Search Console — either by a site manager or an approved visitor request. Use the URL Removals tool to see who submitted the request. Removal requests expire after approximately 90 days — after that, Google may re-index the page. To permanently prevent indexing, use noindex, require authorization, or remove the page entirely.

Crawled — currently not indexed

Google crawled the page but chose not to index it. This may or may not change in the future. No action is required — do not resubmit the URL for crawling.

Discovered — currently not indexed

Google found the URL but hasn't crawled it yet. This typically means Google wanted to crawl it but determined it might overload the server and rescheduled. No immediate action is needed — Google will crawl it in time.

Alternate page with proper canonical tag

This page correctly points to a canonical version (such as an AMP page pointing to its desktop canonical, or a mobile version pointing to its desktop version). The canonical page is indexed. This is expected behavior — no action needed.

Page with redirect

This is a non-canonical URL that redirects to another page. The redirecting URL itself will not be indexed — the target URL of the redirect may or may not be indexed depending on how Google evaluates it. To check the index status of the target URL, use the URL Inspection tool and inspect the canonical URL directly.

FAQs

Do I need to fix every "Page Not Indexed" status?

No. Several statuses — such as Crawled (currently not indexed), Discovered (currently not indexed), and Alternate page with proper canonical tag — are expected behaviors that don't require action. Focus on statuses like server errors, redirect errors, and unintentional noindex directives.

How do I check why a specific page isn't indexed?

Use the URL Inspection tool in Google Search Console. Enter the URL to see its current index status, how Google last crawled it, and any issues detected. You can also run a live test to see how Google currently renders the page.

What's the difference between a 404 and a soft 404?

A 404 returns a proper HTTP 404 response code telling Google the page doesn't exist. A soft 404 returns a "not found" message to the visitor but sends a 200 (success) response code to Google — causing confusion. Google treats soft 404s as indexable pages with poor content rather than removed pages.

How do I permanently prevent a page from being indexed?

Add a noindex directive to the page, require authorization to access it, or remove the page entirely. URL removal requests through Search Console are temporary and expire after approximately 90 days.