HTTP Status Code Checker: find broken pages in seconds.
Paste up to 20 URLs and see the HTTP status code each one returns: 200, 301, 404, 500 and more. You also get redirect counts, final URLs and response times, with filters and a CSV export for your fix list.
- 100% free, unlimited use
- Bulk check up to 20 URLs + CSV export
- Built by 300+ marketing specialists
Check status codes
Paste URLs or domains, one per line. We'll add https:// where it's missing.
Summary
| # | URL | Status | Status text | Redirects | Final URL | Time |
|---|
Status shows the first response for the URL you entered. If it redirects, the arrow shows where the chain ends. Filters group each URL by its final result.
What is an HTTP status code, and why check it?
Every time a browser or search engine requests a page, the server answers with a three-digit HTTP status code before sending anything else. That code says whether the page loaded, moved, can't be found or failed.
You rarely see status codes, but search engines act on every one. A page that returns 404 eventually drops out of the index. A 301 passes its signals to a new URL. A run of 500 errors makes Google crawl your site less. Checking status codes is the quickest way to find broken pages, wasted redirects and server problems before they cost you traffic.
This HTTP status code checker requests each URL from our server, follows any redirects, and reports the code, the final URL and the response time.
Check status codes in bulk in 4 steps
Collect your URLs
Start with the pages that matter most: top landing pages, URLs from ads and emails, and old URLs from a previous site.
Paste up to 20
One per line. Full URLs or bare domains both work. Duplicates are removed automatically.
Filter the results
Use the chips to see only 4xx, 5xx or failed URLs. Those are your fix list.
Export and fix
Download the CSV, share it with your developer, and re-check once the fixes are live.
Common HTTP status codes and their SEO impact
The codes you'll meet most often when auditing a website, what each means, and how search engines respond.
| Code | What it means | SEO impact |
|---|---|---|
| 200 OK | The request worked and the page content is returned. | The normal, indexable state. Make sure error pages don't also return 200 (a "soft 404"). |
| 201 Created | A new resource was created, usually after a form or API POST. | Rarely seen on web pages. No SEO effect for normal URLs. |
| 204 No Content | Success, but there is no content to return. | Nothing to index. Google may report the URL as a soft 404, so don't use it for pages. |
| 301 Moved Permanently | The page has moved for good to the URL in the Location header. | Strong signal to index the new URL. The right choice for permanent URL changes. |
| 302 Found | The page is temporarily at another URL. | Weak signal. The original URL usually stays indexed. Use 301 if the move is permanent. |
| 304 Not Modified | The page hasn't changed since the crawler's last visit, so it can use its cached copy. | Healthy. It saves crawl resources and bandwidth. No action needed. |
| 307 Temporary Redirect | Temporary move that keeps the request method (e.g. POST stays POST). | Treated like a 302. Browsers also show it for HSTS upgrades. |
| 308 Permanent Redirect | Permanent move that keeps the request method. | Treated like a 301. |
| 400 Bad Request | The server could not understand the request (malformed URL or headers). | Not indexed. Often a broken link or a bad parameter. Find where it is linked. |
| 401 Unauthorized | Login required. | Not indexed. Fine for private areas. A problem if public pages return it. |
| 403 Forbidden | The server refuses access, often due to permissions, a firewall or bot protection. | Not indexed. Check your firewall/CDN isn't blocking search engines by mistake. |
| 404 Not Found | No page exists at this URL. | Dropped from the index over time. Harmless on its own. Redirect it if the URL has links or traffic. |
| 410 Gone | The page was removed deliberately and isn't coming back. | Handled much like a 404, and states clearly that the removal is intentional. |
| 429 Too Many Requests | The client is sending too many requests. The server is rate limiting it. | Google slows its crawling. If it lasts, pages can drop out of the index. |
| 500 Internal Server Error | Something broke on the server (code, plugin or database error). | Crawling slows, and pages that keep failing get dropped. Fix it fast. |
| 502 Bad Gateway | A proxy or CDN got an invalid answer from the origin server. | Same as other 5xx errors. Usually a hosting or CDN configuration issue. |
| 503 Service Unavailable | The server is overloaded or down for maintenance. | The right code for planned maintenance (add Retry-After). Don't let it run for days. |
| 504 Gateway Timeout | A proxy or CDN waited too long for the origin server. | Same as other 5xx errors. Check server speed and timeouts. |
A "soft 404" is a page that says "not found" but returns 200. Search engines spot these and treat them as errors anyway, so always return a real 404 or 410 for missing pages.
How to find and fix broken pages
- Find them. Check the Pages report in Google Search Console for "Not found (404)" and "Server error (5xx)", then run those URLs through this tool to confirm the current status.
- Prioritise by value. Fix URLs with backlinks, traffic or internal links first. A 404 nobody links to is low priority.
- Choose the right fix. Moved or replaced? 301 it to the closest match. Gone for good with no replacement? Let it return 404 or 410.
- Fix the links, not just the page. Update menus, internal links and sitemaps so they point to live URLs, not redirects or errors.
- Hand 5xx errors to your developer or host. Server errors usually come from code, plugins, database load or CDN settings. The time column can hint at overload.
- Re-check. Paste the same list again after deploying and confirm every URL is now 200 or a single 301.
6 tips to keep your status codes healthy
Small habits that stop broken pages and wasted redirects from building up.
Check after every release
Redesigns, plugin updates and CMS changes are the top causes of sudden 404s and 500s. Keep a list of key URLs and re-check it after each deploy.
Keep sitemaps clean
Your XML sitemap should list only final URLs that return 200: no redirects, no 404s, no noindex pages.
Don't block crawlers by accident
Firewalls and bot protection sometimes return 403 or 429 to search engines. Test with the Googlebot option and check your CDN settings.
Redirect with purpose
Only redirect a missing page when there's a genuinely relevant replacement. Irrelevant redirects are treated like soft 404s.
Make your 404 page useful
Return a real 404 code, but give visitors search, popular links and a way back, so a dead end doesn't become a lost lead.
Monitor, don't just audit
Uptime monitoring and a regular Search Console review catch 5xx spikes early, before rankings are affected.
How our technical SEO engineers use it every day
We built the HTTP Status Code Checker for our own team first. Here is where it earns its place in real client work.
- 01Site migrations
Every redirect is mapped and tested before launch, then re-crawled after go-live.
- 02Monthly health checks
We crawl client sites for broken pages, chains and status errors every month.
- 03Domain due diligence
Before buying or merging domains we review age, history and backlinks.
Broken pages cost you leads. We'll find every one.
This tool checks 20 URLs at a time. Our technical SEO audit crawls your entire site, maps every error and redirect, and hands you a prioritised fix plan, or we fix it for you.
- Full-site crawl for 4xx, 5xx and redirect issues
- Search Console error review and clean-up
- Prioritised fix list your developer can act on
Keep optimising with related tools
Redirect CheckerTrace every hop in a redirect chain and spot SEO problems.Open tool 
Domain Age CheckerLook up when a domain was registered, its age and expiry.Open tool 
Google SERP Preview ToolPreview your title and meta description as they appear on Google.Open tool 
Readability CheckerScore how easy your writing is to read, with fixes.Open tool HTTP Status Code Checker: common questions
Still unsure what your results mean? Our team will walk you through them for free.
Ask a specialistHow do I check the HTTP status code of a URL?
Paste the URL into the box above and press "Check status codes". Our server requests the page and shows the code it returns (200, 301, 404, 500 and so on), plus any redirects, the final URL and the response time. You can check up to 20 URLs at once.
What is the difference between a 404 and a 410?
Both mean the page isn't available. A 404 says "not found", with no promise either way. A 410 says the page was removed on purpose and won't return. Search engines handle them very similarly. Use 410 when you want to be explicit that the removal is deliberate.
Do 404 errors hurt SEO?
A 404 on a page that should not exist is normal and doesn't hurt the rest of your site. The damage comes when important pages return 404: you lose their rankings, and any links pointing to them are wasted. Redirect those to the most relevant live page.
Why does a URL show 403 or 429 here but load in my browser?
Firewalls, CDNs and bot protection often treat automated requests differently from browsers. Try the Desktop or Googlebot options. If search engines get blocked too, that's an SEO problem worth fixing with your host or CDN.
Why does the checker show "Failed" for a URL?
It means there was no usable HTTP response. The domain may not resolve, the server may have timed out, the SSL certificate may be invalid, or the redirects loop. The error message in the table tells you which.
Can Elite Information Tech fix broken pages on my site?
Yes. Our technical SEO team crawls every URL on your site, not just 20, finds 4xx, 5xx and redirect problems, and fixes them in your CMS or server config, with a before and after report. Get your free audit.
Get a free technical SEO audit
Our specialists will review your results, show you where you are losing money or traffic, and give you a clear 90-day plan to fix it.
- Personalised audit of your ads, SEO or website
- Competitor snapshot and quick wins
- 90-day action plan with a recommended budget