New researchTechnical SEO & AI Search · 2027Explore the framework

HTTP status codes for SEO: what 200, 301, 404, 410 and 5xx mean for Google

How Google treats each HTTP status code: which can be indexed, which pass canonical signals, which slow crawling, and how to audit them across a site.

Part of the Crawling & Indexing series. For the full picture, start with Crawling and indexing: how search engines find your pages, and what stops them.

Every URL answers a request with a three-digit status code before it sends any content. For search engines that number decides a lot: whether the page can be indexed, whether a redirect passes signals, whether crawling slows down. This guide covers how Google treats each group of codes and how to audit them across a site.

How does Google treat each status code?

Code Meaning What Google does
200 OK Eligible for indexing: Google’s technical requirements include that “Google receives an HTTP 200 (success) status code”
301, 308 Permanent redirect “The indexing pipeline uses the redirect as a signal that the redirect target should be canonical”
302, 303, 307 Temporary redirect Googlebot follows it, but it isn’t used “as a signal that the redirect target should be canonical”
404, 410 Not found, gone “Google doesn’t index URLs that return a 4xx status code, and URLs that are already indexed and return a 4xx status code are removed from the index”
429 Too many requests Treated like a server error: crawling slows down
5xx Server error “5xx and 429 server errors prompt Google’s crawlers to temporarily slow down with crawling”; URLs that “persistently return a server error” are removed

Redirect quotes are from Google’s redirects documentation; 4xx and 5xx from its guide to HTTP status codes.

2xx: success, but check what it says

A 200 makes a page eligible, not indexed. Two traps:

  • A 200 on an error page. A “not found” message served with 200 is reported as a soft 404.
  • A 200 on a page you didn’t mean to expose, such as staging or internal search. Use noindex or keep it out of the crawl.

3xx: redirects

Use 301 or 308 when a page has moved for good, and link straight to the final URL. Use 302 or 307 only for genuinely temporary moves. Google recommends server-side redirects; JavaScript redirects are a last resort. Chains and loops waste crawling: see redirect chains, and for migrations, redirect mapping.

4xx: client errors

404 and 410 are normal for pages that are gone: Google’s Page indexing help says “404 responses are not necessarily a problem, if the page has been removed without any replacement.” Google’s status code guide treats 4xx codes alike for indexing and says “the 4xx status codes, except 429, have no effect on crawl rate.” The real problems are pages that should exist returning 404, and internal links pointing at them. See broken links.

Watch 401 and 403 too: a page or a whole section that answers crawlers with 403, often because of bot protection, can’t be indexed.

5xx: server errors

These are the urgent ones. Occasional 5xx responses slow Google’s crawling; persistent ones get URLs dropped. A robots.txt file that returns 5xx can pause crawling of the whole site; see robots.txt for SEO.

How do you audit status codes across a site?

Crawl the site. Crawlens shows the live breakdown while crawling (2xx success, 3xx redirect, 4xx client error, 5xx server error, no response and blocked by robots.txt), and the audit flags:

Check What it catches
Internal pages return 4xx Crawled URLs returning 404, 410, 403 and other client errors
Internal pages return 5xx Server errors
Pages did not respond Timeouts, DNS and SSL failures
Pages link to broken internal URLs Where the broken links are
Redirect chains, Redirect loops Redirect problems
Temporary redirects 302/303/307 where a permanent redirect may be meant
Pages with search traffic return errors Broken URLs that earned clicks (with Search Console connected)

Filter the URLs table by status to list every URL in a group, and use server logs to see what Googlebot itself received: Googlebot gets errors. See log file analysis.

Checklist

  • Every page that should rank returns 200
  • Error pages return 404 or 410, not 200
  • Moved pages use 301 or 308, linked directly
  • Temporary redirects only for temporary moves
  • No internal links to 4xx or 5xx URLs
  • No 5xx or 429 under normal crawl load
  • No 401/403 for search engine crawlers on public pages
  • robots.txt returns 200

Frequently asked questions

Do 404 errors hurt SEO?

Not in themselves. Google says 404 responses aren't necessarily a problem if the page was removed without a replacement, and that 4xx codes other than 429 have no effect on crawl rate. The cost is lost traffic when a page that ranked returns 404 by mistake.

What's the difference between a 301 and a 302 redirect for SEO?

Google uses a permanent redirect (301 or 308) as a signal that the target should be canonical. With a temporary redirect (302, 303 or 307), Googlebot follows it, but the indexing pipeline doesn't use it as that signal.

Should I use 404 or 410 for removed pages?

Either works. Google's documentation treats 4xx codes the same way for indexing: URLs that return them aren't indexed, and already indexed ones are removed.

What happens when my site returns 5xx errors?

Google says 5xx and 429 responses prompt its crawlers to temporarily slow down, and that URLs that persistently return a server error are removed from the index.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows