About the Bulk HTTP Status Code Checker
Status codes tell search engines whether a URL works (200), has moved (301 or 302), is missing (404 or 410) or failed on the server (5xx). This bulk HTTP status code checker requests up to 50 public URLs and reports the status, every redirect hop, the final destination, response time and content type for each.
It is handy after a migration to confirm old URLs return 301s to the right pages, when cleaning up a list of URLs from Search Console, or when checking that pages in your sitemap all return 200. Filter by status class to focus on errors, then export the results as CSV to share with a developer. URLs that redirect several times or end on an error are the first to fix.
How to use it
- Paste up to 50 URLs, one per line.
- Run the check and wait for each URL to be requested.
- Filter by status class (2xx, 3xx, 4xx, 5xx) to focus on problems.
- Export the results as CSV and fix redirects or errors at the source.
Frequently asked questions
What is the difference between a 301 and a 302 status code?
A 301 means the URL has moved permanently, which tells search engines to transfer signals to the new URL and eventually show it instead. A 302 means a temporary move, so search engines may keep the original URL indexed. Google treats a long-standing 302 much like a 301 over time, but a 301 states your intent clearly for permanent changes.
Is a 404 or a 410 better for removed pages?
Both tell search engines the page is gone, and Google treats them very similarly. A 410 states the removal is intentional and permanent, which may lead to slightly faster dropping from the index. If the content has a close replacement, a 301 redirect to that page is usually better for visitors than either error.
Why does a URL show a different status here than in my browser?
Servers can respond differently depending on the user agent, cookies, location or request rate. Your browser may also show a cached page. Some firewalls block automated checkers with 403 or 429 responses. If results differ, test again later and confirm with Google Search Console's URL Inspection tool, which shows what Googlebot received.