Free SEO tool

Bulk HTTP Status Checker

Paste a list of URLs, one per line, and this bulk HTTP status checker fetches each one once and reports its final status code, final URL and redirect count. It flags error responses and redirect chains with the same rules as a full audit, lists invalid lines, and exports the results as CSV.

How to Check HTTP Status Codes in Bulk

Paste the URLs, submit the list and read one row per URL; the CSV button saves the same rows.

Paste the URLs into the field, one per line, up to the limit shown under it. A line without http:// or https:// is checked with https://.
Select Submit. Each URL is requested once, and redirects are followed for up to five hops.
Read the results table: the final status code, the final URL, the number of redirects and the verdicts of the two rules for each URL.
Open a URL under "Rule verdicts for URLs with a problem" to see the evidence, or start a full audit of that page.
Select Download CSV to save the same rows, with the invalid lines and the URLs that were not checked (the first 100 of each, and a count of the rest).

What the HTTP Status Codes in Your Results Mean

The status column shows the code of the final response, after every redirect was followed. The two rule columns say whether that answer is a problem for search engines.

Common HTTP Status Codes

A 200 means the URL answered normally, which lets Google consider the content but does not guarantee indexing. A 404 or 410 means the URL no longer exists, and Google does not index the content of a 4xx page. A 500 or 503 is a server error: Google slows down crawling and eventually drops the URL if the error lasts. Any other 4xx or a 5xx final answer fails the error status rule; 401, 403 and 429 are reported as access blocked.

Redirect Status Codes and Redirect Count

A 301, 302, 303, 307 or 308 sends the request to another URL, and the checker follows it to the final answer. The redirect count is the number of hops, and the final URL column shows where the chain ends. More than one redirect fails the redirect chain rule; a URL that needs more than five redirects is reported as having no final answer.

Access Blocked, No Answer and Host Busy

A 401, 403 or 429 is shown with its code and marked as access blocked, and the rules are not checked because the site refused the request. No answer means a timeout, a connection error, too many redirects or an address the checker does not request, such as a private network. Host busy means another request to the same host was in progress; submit the list again shortly.

Invalid Lines and URLs Not Checked

A line that is not an http or https URL is never requested, and a repeated URL is checked once, even when the host is written in other letter case. URLs after the limit of one check are reported as not checked. The first 100 lines of each kind are listed with their reason, and the rest are counted. A check also stops starting new requests after 45 seconds, and the URLs it did not reach are marked so you can submit them again.

HTTP Status Checker FAQ

What Is the Difference Between a 301 and a 302?

A 301 says the page moved permanently, a 302 that the move is temporary. Google treats a 301 as a strong signal that the target should become the canonical URL, and a 302 as a weak one. A 308 behaves like a 301 and a 307 like a 302. Use a 301 or 308 when a page has moved for good.

Which HTTP Status Codes Indicate a Broken Link?

A 404 or 410 final answer means the linked page no longer exists, and a 5xx that lasts means the server cannot deliver it. Because the checker follows redirects, a link that redirects to a missing page shows the 404 of its final answer. Fix the link or redirect it to a page that answers 200.

Are HTTP Status Codes Important for SEO?

Yes. Google does not index the content of a URL that answers 4xx, and it stops using a previously indexed URL over time. Lasting 5xx errors slow down crawling and eventually drop URLs from the index. Redirect chains add a request before every visit, so each extra hop delays the page.

How Many URLs Can I Check at Once?

The limit of one check is shown under the field, and URLs after it are listed as not checked. Requests to the same host run one at a time with a short pause between them, so a long list on one site takes longer. URLs not reached within 45 seconds are marked, and you can submit them in a new check.