HTTP status checker
Check the HTTP status code of up to 20 URLs at once, with any redirects followed to the end and the response time of each request. Pick Googlebot's user-agent string to see what a crawler gets.
Up to 10 checks a minute. Pages are fetched from IndexCyborg's servers; private and local addresses are refused.
A bulk HTTP status checker
Paste URLs one per line, up to 20 at a time. Each one is requested without following redirects, so you see the status code the URL itself returns, then the chain is followed to its final status. Times are measured from IndexCyborg's servers per request: a guide to how quickly the server answers, not a page-speed score.
The user agent can be IndexCyborgBot, Googlebot Smartphone, Googlebot Desktop or desktop Chrome. Only the string changes; sites that verify Googlebot by IP address can still tell the request isn't from Google.
What status codes mean for indexing
| Status | What Google does |
|---|---|
| 200 | Processes the content. It can still be a soft 404 if the page looks like an error. |
| 301, 308 | Follows the redirect; a strong signal that the target is canonical. |
| 302, 303, 307 | Follows the redirect; a weak canonical signal. |
| 404, 410 | Doesn't use the content; indexed URLs are dropped and crawled less over time. |
| 429 | Treated as a server error: the server is overloaded. |
| 500, 502, 503 | Slows crawling; URLs that keep failing are removed from the index. |
Source: How HTTP status codes, and network and DNS errors affect Google Search. HTTP status codes for SEO goes through each class, and 410 vs 404 covers removed pages.
In Search Console
These codes surface in the Page indexing report as “Not found (404)”, “Server error (5xx)”, “Soft 404” and “Page with redirect”. See Not found (404), Server error (5xx) and Soft 404.
How IndexCyborg handles this
IndexCyborg records the HTTP status and redirect chain of every new and changed page it finds in your sitemaps. Error responses raise a critical issue with the status as evidence, unreachable pages too, and non-200 pages are never sent for Request indexing. When the page recovers, the issue closes on the next check. It's part of the technical SEO checklist it keeps running.
Frequently asked questions
- How do I check the HTTP status code of a URL?
- Paste it into the checker. It requests the URL from IndexCyborg's servers and shows the first response's status code, then follows any redirect to the final status.
- Can a page return 200 and still be treated as an error?
- Yes. If a page returns 200 but looks like an error or an empty page, Search Console reports it as a soft 404. The status code is right, the content isn't.
- Is there a difference between 404 and 410 for Google?
- Google treats both the same way: it doesn't use the content, drops the URL from the index if it was indexed, and gradually crawls it less often.