Why pages aren't indexed in Google Search Console

“When Google tried to index the page it encountered a 'noindex' directive and therefore did not index it.”

Fix it when the page should rank. The directive is a robots meta tag or an X-Robots-Tag header, added by a CMS setting, a template, the server or the CDN.

“This page was blocked by your site's robots.txt file.”

Fix it when the page should rank: find the Disallow rule that matches the URL. robots.txt stops crawling, not indexing, so don't use it to hide a page.

“The page was blocked to Googlebot by a request for authorization (401 response).”

Right for a staging site or a members' area behind a login. If the page is meant to be public, remove the authentication from that path.

“HTTP 403 means that the user agent provided credentials, but was not granted access.”

On a public page this is often bot protection or a firewall rule answering Googlebot with 403. Check the security rules for anything that matches crawlers, and test the URL with the URL Inspection live test.

“Your server returned a 500-level error when the page was requested.”

Look in the server or hosting logs for Googlebot's requests at the time of the crawl. Errors that come and go under load still count.

“Google experienced one of the following redirect errors:”

Google lists a chain that is too long, a loop, a URL that exceeds the maximum length, and a bad or empty URL in the chain. Point every old URL straight at its final address.

“This page returned a 404 error when requested.”

A 404 for a page that no longer exists is correct. Redirect it when the URL had traffic or links and an equivalent page exists. A migration that leaves old URLs on 404 is the case to fix.

“The page request returns what we think is a soft 404 response.”

The page answers 200 but looks empty or missing to Google. Return a real 404 or 410 for pages that are gone. Google also warns that redirecting many old URLs to one unrelated page, such as the home page, can be treated as a soft 404.

“The server encountered a 4xx error not covered by any other issue type described here.”

Inspect the URL to see the exact code, then treat it like the ones above. A 410 for a page you removed on purpose is fine.

“This page correctly points to the canonical page, which is indexed, so there is nothing you need to do.”

Google's own words. This is the canonical tag working as intended.

“This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed.”

Expected for every URL that redirects. Update internal links and the sitemap to the final URLs, so Google spends less time on the redirects.

“This page is a duplicate of another page, although it doesn't indicate a preferred canonical page.”

Add a canonical tag on the version you want indexed, or redirect the duplicates to it. Often caused by URL parameters, trailing slashes, or www and non-www both answering.

“Google has indexed the page that we consider canonical rather than this one.”

Your canonical tag is a hint, and Google picked another URL. Make the other signals agree with your choice: internal links, the sitemap and redirects should all point at the URL you named.

“The page was crawled by Google but not indexed. It may or may not be indexed in the future; no need to resubmit this URL for crawling.”

Not a technical fault, so there is no switch to flip. If the page should rank, make it more useful than the pages that do, and link to it from pages that are indexed. Google says resubmitting it does not help.

“The page was found by Google, but not crawled yet.”

Usually a matter of waiting. If it lasts for weeks and covers pages that matter, link to them from pages Google already crawls and list them in the sitemap. That advice comes from practice, not from the help page.

“The page was indexed despite being blocked by your website's robots.txt file.”

Google indexed the URL from links without crawling it. To keep it out, allow crawling and add a noindex. To have it indexed properly, remove the Disallow rule.

“This page appears in the Google index, but for some reason Google could not read the content.”

Run the URL Inspection live test and look at what Google actually received. An empty response, a block page from a firewall, or content Google can't render are the causes to rule out first.