What the checker reports for every URL
- HTTP status code of the first response and of the final destination.
- Redirect chain: every hop, its status code and the URL it points to, so you can spot chains and loops.
- Canonical tag: whether the page declares itself or another URL as the canonical version.
- Meta robots and X-Robots-Tag: catches accidental noindex and nofollow directives.
- Server Last-Modified and page modified dates, where the server or page exposes them.
- Page title, response time and network errors such as DNS failures, timeouts and SSL certificate problems.
How to use it
- Paste your URLs, one per line, or enter your sitemap.xml address to import every URL in it.
- Pick a speed. Balanced suits most sites; choose Gentle for small or shared hosting.
- Press Run. Results fill in live, grouped by status class.
- Click a status group to filter, expand any row for its full redirect chain, then export to CSV.
Status codes and what to do about them
| Code | Meaning | What to do |
|---|---|---|
| 200 OK | The page loaded normally. | Nothing, unless it carries noindex or a wrong canonical. |
| 301 Moved Permanently | Permanent redirect. Ranking signals pass to the target. | Update internal links to point straight at the final URL. |
| 302 / 307 Found | Temporary redirect. The old URL may stay indexed. | Change to 301 if the move is permanent. |
| 304 Not Modified | Server says the cached copy is still current. | Normal for conditional requests. |
| 403 Forbidden | Server refused the request, often a firewall or bot block. | Check it is not blocking Googlebot. |
| 404 Not Found | The page does not exist. | Redirect to the closest live page or restore it; remove internal links. |
| 410 Gone | Deliberately removed. | Fine for retired content; Google drops it faster than a 404. |
| 429 Too Many Requests | Rate limited. | Slow crawl pacing; review server or CDN limits. |
| 500 / 502 / 503 | Server or gateway error. | Fix urgently. Repeated 5xx responses make Google crawl less. |
Why status codes decide whether a page gets indexed
Google only indexes URLs that return a 200 response and allow indexing. Everything else is either followed (redirects), dropped (4xx) or crawled less often (5xx). A single site migration can leave hundreds of internal links pointing at redirected or missing URLs, and none of it shows up while you browse the site normally.
Redirect chains are the most common hidden cost. Each extra hop slows crawling and the page for users. Google follows up to ten hops, but anything past one is worth fixing: point the link straight at the final URL.
If Search Console shows Page with redirect, Not found (404) or Duplicate without user-selected canonical, export the affected URLs, paste them here and you will see exactly which response and canonical Google is getting. Our 47-point technical SEO checklist and crawl budget guide cover the fixes in depth.
Built to check politely
The checker sends lightweight HEAD requests first and falls back to GET only when a server refuses HEAD, stopping the download right after the headers. Requests to the same domain are spaced out with random jitter, and a 429 or 503 response pauses that domain and honours its Retry-After header. Requests to private or internal network addresses are blocked.
Frequently asked questions
What does a bulk HTTP status checker do?
It requests every URL in your list and reports the status code the server returns (200, 301, 404, 500 and so on), the full redirect chain, the final destination, the canonical tag and any meta robots directive. It is the fastest way to find broken links, redirect loops and pages that are quietly blocking indexing.
Is this tool really free?
Yes. There is no sign-up, no email gate and no credit card. The free version checks up to 2,000 URLs per day per visitor, in batches of up to 100 URLs. If you need a larger crawl, email hello@justmarketo.com and we will run it for you.
Can I check an entire sitemap?
Yes. Paste your sitemap.xml address into the sitemap import and the checker pulls every URL from it, including nested sitemap index files, then checks them all.
Why does the checker say a URL redirects when it loads fine in my browser?
Browsers follow redirects silently. A page that loads can still sit behind one or several 301 or 302 hops, for example http to https, then non-www to www, then a trailing slash. Each hop wastes crawl budget and dilutes link signals, so the checker shows every step.
What is the difference between a 301 and a 302 redirect?
A 301 tells search engines the move is permanent and to transfer ranking signals to the new URL. A 302 says the move is temporary, so the original URL may stay in the index. Most site migrations and URL changes should use 301.
Which status codes block Google from indexing a page?
Any 4xx code (404, 410, 403) and any 5xx server error prevents indexing. A 200 page can still be excluded if it carries a noindex meta robots tag or X-Robots-Tag header, or if its canonical points to a different URL. The checker reports all three.
Will checking my URLs overload my server?
No. Requests are paced per domain with a gap between hits and random jitter. If a server returns 429 or 503, the checker pauses that domain, honours the Retry-After header and slows down before continuing.
Can I export the results?
Yes. Filter by status class and export the results as CSV to share with developers or import into a spreadsheet.
Need a full technical audit?
The checker shows what is broken. Our technical SEO team fixes it: redirects, canonicals, crawl budget, Core Web Vitals and indexing.
See technical SEO services