My Tool Studio
SEOURL-first

HTTP Status Code Checker

This HTTP status code checker shows what a URL returns when it is requested: 200, 301, 404, 500 or any other code. Paste one URL or up to 100, one per line. Each result shows the status, every redirect hop with its code and Location, where the chain ends and how long the check took. When a server refuses the quick HEAD request with 403, 405 or 501, the tool retries with a normal GET so you see the real answer. It can also follow meta refresh and JavaScript redirects. Filter results by status class, open response headers for any row, and export to CSV or Excel. A separate check compares the http, https, www and non-www versions of a domain.

Always freeNo sign upRuns in your browser

0 URLs entered. Bare domains get https:// added.

All four should end on the same final URL with a 200.

How to use

01

Paste your URLs

Type or paste one URL per line into the box, up to 100 at a time. Addresses without http:// or https:// are checked as https. Click Try sample to see how the results look.

02

Choose options and run the check

Leave the GET retry ticked to avoid false 403 and 405 results, and tick meta refresh and JavaScript redirects if you need them. Click Check status; URLs run four at a time with a running count.

03

Filter, inspect and export

Use the 2xx, 3xx, 4xx, 5xx and Errors buttons to filter, open a row to see each hop and its Location, and click Show response headers. Download CSV or Excel to share the results.

Why HTTP Status Code Checker

HTTP status codes and their SEO impact

These are the codes you will see most often. The SEO notes describe how Google generally handles each one.

CodeMeaningSEO impact
200 OKThe page loaded normallyCan be indexed
301 Moved PermanentlyThe page has a new permanent addressGoogle indexes the target and passes signals to it
302 FoundTemporary moveGoogle may keep the old URL indexed for a while
304 Not ModifiedUnchanged since the last visitSaves crawl resources; no effect on ranking
403 ForbiddenAccess refusedThe page cannot be indexed; often a firewall blocking bots
404 Not FoundNo page at this addressDropped from the index over time; fine for pages that are gone
410 GoneRemoved on purposeLike 404, possibly removed slightly faster
429 Too Many RequestsRate limitedGoogle slows crawling; if it lasts, pages can drop out
500 Internal Server ErrorThe server failedGoogle slows crawling; lasting errors can drop pages
503 Service UnavailableTemporarily downThe right code for maintenance; Google retries later

Reading a redirect chain in the results

Say you check http://example.com/old-page and the row opens to show three hops. The row summary reads 301 for the first status, 2 redirects, and ends in 200.

That works, but each hop is an extra round trip for visitors and crawlers. A better setup sends the first URL straight to https://example.com/new-page in one redirect; the Htaccess Redirect Generator on this site writes rules that do that. If the final code were 404 or 5xx instead, every link pointing at the first URL would lead to an error, and fixing the target matters more than the hop count.

  • #1 301 http://example.com/old-page, the HTTP to HTTPS rule
  • #2 301 https://example.com/old-page, the old page to new page rule
  • #3 200 https://example.com/new-page, the final page

Common questions

Why does the HTTP status checker use a HEAD request instead of GET?
HEAD asks for the status line and headers without the page body, so checks are quick and light on both servers. A few servers answer HEAD with 405 Method Not Allowed, 403 or 501 even though the page loads fine. When that happens the checker retries with a normal GET and shows both results, so you can tell a real error from a server that dislikes HEAD.
How many URLs can the bulk HTTP status checker handle?
Up to 100 per run. Extra lines are skipped with a notice, and duplicate lines are checked once. For thousands of URLs, a crawler such as the Site Audit tool is a better fit.
How is the response time in the HTTP status checker measured?
It is the time from your browser sending the request to the result coming back, which includes our server's trip to the site and every redirect hop. It is useful for comparing URLs in the same run, not as an exact server response time.
What makes a URL return 403 here but load fine in my browser?
Usually a firewall or bot protection that blocks requests which do not look like a browser. The GET retry sends browser-like headers, which gets past many of these rules, and the row then shows what the GET returned. If it still says 403, a stricter firewall such as a Cloudflare challenge is in the way, and some real crawlers may be blocked too.
Can I check the HTTP status of pages behind a login?
You get an answer, but it is the logged-out one, usually 401, 403 or a 302 to the login page. That is useful for SEO work, because crawlers see the same thing. There is no way to add your session cookie to the check.
What does it mean when a status check stops after 10 hops?
The checker follows at most 10 redirects. If the tenth hop still redirects, the chain is either very long or a loop, and browsers and crawlers will give up too. Open the row to see which URLs repeat, then fix the rules so the first URL points straight at the final one.
Can I check the HTTP status as Googlebot?
Not in this tool; the user agent is fixed and cannot be switched to Googlebot, Bingbot or a phone. A site that treats bots differently may give Googlebot another answer. To see exactly what Googlebot gets, use the URL Inspection tool in Google Search Console.
What is the difference between a 404 and a 410 status code?
Both mean the page is not there. A 404 says it was not found, while a 410 says it was removed on purpose. Google has said a 410 may be dropped from the index slightly faster, but in practice both lead to removal.
Does a 200 status guarantee the page is healthy?
No. A 200 only means the server answered without an error. The page could still be empty or show an error message, which Google calls a soft 404. Status checks find server and redirect problems; content problems need a look at the page.
Why check the http, https, www and non-www versions of my domain?
Each of the four addresses can be linked from somewhere, so all of them should end on the one version you want indexed, ideally with a single 301. The version check traces all four at once and says whether they end on the same URL. If they do not, search engines may index two copies of your home page.

More SEO tools

View all

Meta Tag Generator

Build meta, OG and X tags

SEO
URL-first

Meta Tag Analyzer

Audit meta tags for one or 20 URLs

SEO
URL-first

Robots.txt Generator

Build a robots.txt with presets

SEO

Robots.txt Tester and Validator

Test URLs against any robots.txt

SEO
URL-first