NeovaAdvanced SEO Platform

HTTP Status Code Checker: What Each Code Means for SEO and How to Check Them All

Every URL answers with a three digit number before it sends a single word of content. That number decides whether Google indexes the page, follows it somewhere else, drops it or slows down crawling the whole site. An HTTP status code checker reads that number for you, and the table below says what Google does with each one.

Crawling and Indexinghttp status code checkerUpdated November 21, 2026By the Neova team

What an HTTP Status Code Checker Does

An HTTP status code checker requests a URL and reports the status line the server sends back, such as 200 OK or 301 Moved Permanently. A good one also follows redirects hop by hop and shows where each one ends, and it sends the request the way a search engine would, since some servers answer bots differently from browsers.

Checking a single URL settles a quick question. Checking every URL of a site is where status codes pay off: broken internal links, redirects nobody updated, error pages that answer 200, and server errors that only show up under load.

The Five Classes at a Glance

Status codes are defined in RFC 9110, section 15. The first digit is the class:

ClassMeaningWhat Google doesColor in Neova
1xxInformationalNever a final answerNone
2xxSuccessContent may be indexedGreen
3xxRedirectionFollows up to 10 hopsOrange
4xxClient errorNot indexed, dropped over timeRed
5xxServer errorSlows crawling, drops if persistentRed

The HTTP Status Codes That Matter for SEO

What Google says it does with each code, from its page on how HTTP status codes affect Google Search and its redirects guide:

CodeNameWhat Google doesUse it for
200OKPasses content to indexingEvery live page
202AcceptedWaits briefly, uses what arrivedNot for pages
204No ContentNothing to indexNot for pages
301Moved PermanentlyStrong signal, target shownPermanent moves
302FoundWeak signal, source shownShort changes
304Not ModifiedKeeps its last copyConditional requests
307Temporary RedirectSame as 302Short changes, APIs
308Permanent RedirectSame as 301Permanent moves, forms
401UnauthorizedNot indexedLogin areas
403ForbiddenNot indexedBlocked content
404Not FoundNot indexed, droppedRemoved pages
410GoneSame as 404Removed for good
429Too Many RequestsTreated as server errorBrief rate limiting
500Internal Server ErrorSlows crawl, kept a whileFix fast
503Service UnavailableSlows crawl, kept a while1 to 2 days of downtime

Three points from Google's page worth reading twice. All 4xx codes except 429 are treated the same, so 404 and 410 end the same way. Google warns not to use 401 or 403 to slow its crawling down. And URLs that keep answering 5xx are eventually dropped from the index. SEO ProCheck's HTTP status codes reference for SEO covers the rarer codes too.

A 200 Is Not Always Good News

A checker that only counts 200s misses the worst cases: pages that answer 200 when they should not. An error page that answers 200 becomes a soft 404, and an http page that answers 200 is a second copy of your https page. We found both kinds of wrong answer on our own site.

Request on neova.appAnsweredShould answerFixed
http:// pages200301 to https✓
Unknown addresses503404✓

That was our own SEO pass on November 20, 2026. The http pages answered 200, so every page existed twice. Unknown addresses answered 503 from a coming soon page, which tells Google the server is failing rather than that the page does not exist; a real 404 page fixed it. Neither showed up in a browser, which follows redirects and shows the page whatever the code.

How to Check a Status Code by Hand

For one URL, curl is the fastest status code checker there is:

# status line and headers
curl -sI https://example.com/page

# just the number
curl -s -o /dev/null -w '%{http_code}\n' https://example.com/page

# every hop of a redirect
curl -sIL https://example.com/old | grep -iE '^(HTTP|location)'

# a URL that should not exist: want 404
curl -s -o /dev/null -w '%{http_code}\n' https://example.com/no-such-page-8213

In a browser, open the developer tools, select the Network tab, turn on Preserve log and reload. The first document request shows the status. Some servers answer a HEAD request (-I) differently from a GET; if the result looks odd, drop -I and use -D - to print the headers of a real GET.

Check Status Codes for a Whole Site

  1. Crawl from the home page to get the status of every linked URL, with the pages that link to each one.
  2. Crawl a list of URLs no link reaches: old sitemaps, top backlinked pages, URLs from a previous site.
  3. Read Search Console. The Page indexing report sorts URLs by reason: Not found (404), Server error (5xx), Soft 404, Page with redirect, Blocked due to access forbidden (403).
  4. Read your server logs. They show the codes Googlebot actually got, including 5xx bursts a crawl at another hour never sees. The log file analysis guide explains how.
  5. Crawl again and compare the counts per class.

Scale matters here. Our own crawl of seoprocheck.com on October 17, 2026 fetched 10,222 URLs in 61 minutes, of which 4,561 were HTML pages that answered 200. Checking codes one URL at a time does not reach that far. For 5xx errors in depth, see SEO ProCheck on diagnosing and preventing 5xx server errors.

Which Status Code to Send, Case by Case

SituationSendNot
Page moved for good301 or 308302
Short promotion swap302 or 307301
Deleted, no replacement404 or 410301 to home
Deleted, close replacement301 to it200 error page
Planned maintenance503 with Retry-After200 notice
Bots overloading the server429 or 503401 or 403
Members only401 or login redirect200 login page
Old http address301 to https200

Google's advice on pausing a site is to use 503 for 1 to 2 days at most, and never for robots.txt, since a 503 there blocks all crawling. For redirects in more depth, read 301 vs 302 redirect and redirect chains.

Check Status Codes With Neova

Neova records every URL's status code and colors it the same everywhere: 2xx green, 3xx orange, 4xx and 5xx red, with No Response named apart. Status Codes sits in All URLs and on the Overview, the Crawler Log shows each code live as the crawl runs, and List Crawl fetches only the URLs you paste or upload. A URL with no response gets 3 attempts before it counts as No Response.

Crawl Map in Neova colored by status code: 611 URLs answering 2xx, 1 answering 4xx, none 3xx, 5xx or No Response
Crawl Map in Neova colored by status code: 611 URLs answering 2xx, 1 answering 4xx, none 3xx, 5xx or No Response

The checks behind it include:

The Free plan crawls 1,000 URLs a crawl with every check. Download Neova for Mac, Windows or Linux.

Questions

How do I check the HTTP status code of a URL?

Run curl -sI with the URL to see the status line, or open your browser's developer tools, select Network and reload. For every URL of a site, use a crawler, which also shows the pages that link to each error.

What is the difference between 404 and 410?

404 means not found and 410 means gone for good. Google says it treats all 4xx codes except 429 the same, so both lead to the URL being dropped. Use 410 when you want to be explicit that a page will not return.

Do 5xx errors hurt SEO?

Briefly, they slow Google's crawling of the site. If a URL keeps answering 5xx, Google keeps it in the index for a while and eventually drops it. Fix server errors quickly and use 503 with Retry-After for planned downtime.

Is a 304 Not Modified response bad for SEO?

No. It tells Googlebot the page has not changed since its last visit, so Google keeps its copy and saves a full download. It only appears when the crawler sends a conditional request.

Which status code should a deleted page return?

404 or 410 if nothing replaces it. If a close replacement exists, 301 to that page. Avoid redirecting every deleted page to the home page, which Google may treat as a soft 404.

Take this with you

The assistant links open with a question about this page already written.

Crawl your site with NeovaThe Free plan runs every check on Mac, Windows and Linux. No credit card required.

Keep Reading