Server error (5xx)
Any content Googlebot received from URLs that return a 5xx status code is ignored.
- 500 (internal server error)
- 502 (bad gateway)
- 503 (service unavailable)
Googlebot decreases the crawl rate for the site. The decrease in crawl rate is proportionate to the number of individual URLs that are returning a server error. Google's indexing pipeline removes from the index URLs that persistently return a server error.
To Do:
- Reduce excessive page loading for dynamic page requests.
- Make sure your site's hosting server is not down, overloaded, or misconfigured.
- Check that you are not inadvertently blocking Google.
- Control search engine site crawling and indexing wisely.
URL blocked by robots.txt
This page was blocked by your site's robots.txt file.. You can verify this using the robots.txt tester. Note that this does not mean that the page won't be indexed through some other means. If Google can find other information about this page without loading it, the page could still be indexed (though this is less common). To ensure that a page is not indexed by Google, remove the robots.txt block and use a 'noindex' directive.
Submitted URL marked ‘noindex’
When Google tried to index the page it encountered a 'noindex' directive and therefore did not index it. If you do not want this page indexed, congratulations! If you do want this page to be indexed, you should remove that 'noindex' directive. To confirm the presence of this tag or directive, request the page in a browser and search the response body and response headers for "noindex". If you want this page to be indexed, you must remove the tag or HTTP header.
Soft 404
A soft 404 error is when a URL that returns a page telling the user that the page does not exist and also a 200 (success) status code. In some cases, it might be a page with no main content or empty page.
Such pages may be generated for various reasons by your website's web server or content management system, or the user's browser. For example:
- A missing server-side include file.
- A broken connection to the database.
- An empty internal search result page.
- An unloaded or otherwise missing JavaScript file.
Not found (404)
This page returned a 404 error when requested. Google discovered this URL without any explicit request or sitemap. Google might have discovered the URL as a link from another site, or possibly the page existed before and was deleted. Googlebot will probably continue to try this URL for some period of time; there is no way to tell Googlebot to permanently forget a URL, although it will crawl it less and less often. 404 responses are not a problem, if intentional. If your page has moved, use a 301 redirect to the new location.
Crawled - currently not indexed
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.
Discovered - currently not indexed
The page was found by Google, but not crawled yet. Typically, Google wanted to crawl the URL but this was expected to overload the site; therefore Google rescheduled the crawl. This is why the last crawl date is empty on the report.
Alternate page with proper canonical tag
This page is a duplicate of a page that Google recognizes as canonical. This page correctly points to the canonical page, which is indexed, so there is nothing for you to do.
Duplicate without user-selected canonical
This page has duplicates, none of which is marked canonical. We think this page is not the canonical one. You should explicitly mark the canonical for this page. Inspecting this URL should show the Google-selected canonical URL.
Duplicate, Google chose different canonical than user
This page is marked as canonical for a set of pages, but Google thinks another URL makes a better canonical. Google has indexed the page that we consider canonical rather than this one. We recommend that you explicitly mark this page as a duplicate of the canonical URL. This page was discovered without an explicit crawl request. Inspecting this URL should show the Google-selected canonical URL.
Redirect error
Google experienced a redirect error, either a redirect chain or a redirect loop. By using a web debugging tool, such a Screaming Frog or Httpstatus.io, to learn what causes this redirect error.
Redirect loops are redirects that cause errors because they (eventually) point to themselves, e.g. Page A -> Page B -> Page A. Resolve these by deciding what the correct page is (or should be), and ensure that the final page of the redirect correctly loads.
Redirect hops are multi-step redirects, e.g. Page A -> Page B -> Page C - and sometimes deeper. (NOTE that Google will only follow 5 redirect chain steps before giving up.) Fix this by changing the redirect from Page A to point directly to Page C, or whatever the final, 200 page should be.
Google experienced one of the following redirect errors:
- A redirect chain that was too long
- A redirect loop
- A redirect URL that eventually exceeded the max URL length
- A bad or empty URL in the redirect chain
