Feature
HTTP Status Checker
Check the HTTP status code a URL returns, including every code in its redirect chain, and what that code means for visitors and search engines.
A page that looks fine in your browser can still return the wrong status code: a “not found” page served with 200, or a working page behind a temporary redirect. The status checker shows the codes the server actually sent.
Codes you’ll see most
- 200 OK: the page loaded
- 301 and 308: moved permanently
- 302, 303 and 307: moved temporarily
- 404 and 410: not found or gone
- 429: too many requests, try again later
- 500 to 504: a server or gateway problem
Final status vs the whole chain
The result shows the final status and each code along the way. A URL that ends in 200 after a 302 is reachable, but if the move is permanent the 302 should become a 301.
Limits to keep in mind
The status code reflects one request at one moment, from one location.
Servers can return different codes to automated checks than to browsers.
Common questions
- Why do I get 403 here but the page opens for me?
- The site is probably blocking automated requests or requires a login. The result reflects what a logged-out, automated visitor sees.
- Can I check status codes for a whole sitemap?
- Yes. Paste the sitemap’s address into the URL checker to import and check up to 5,000 URLs it lists, or crawl the site from its homepage.