ShipcheckHTTP status & redirect checker
Paste a public URL. We follow redirects hop by hop (up to a safe limit) and show each status and Location.
What we check
- Each hop’s HTTP status and Location header
- Final status after the chain settles
- HTTP→HTTPS upgrades and host changes
- Temporary redirects used for permanent consolidations
Questions
How many redirects are OK?
One hop is ideal (for example http→https or www→apex). Two is usually fine. Three or more wastes crawl budget and slows users — collapse them.
301 vs 302?
Use 301 or 308 for permanent moves (HTTPS and host consolidation). Use 302 or 307 only when the change is temporary.
Why did a hop fail from this tool but work in my browser?
Some hosts treat our bot differently, or require cookies after a challenge page. The Shipcheck extension follows redirects in your browser instead.
Does this check every link on a page?
No. It checks one URL’s redirect chain. For many links on a page, use the broken link checker.
Related tools
Broken link checker
Find dead links, redirects, and missing pages on any public page.
Open tool →Canonical tag checker
Check rel=canonical for missing tags, www/https mismatches, and paths that do not match the live URL.
Open tool →Free website checker
Paste a public URL for one report from server HTML plus Google PageSpeed. Use the extension for localhost, JS-heavy apps, and the full audit.
Open tool →Related guides
HTTP redirects and status codes: 301, 302, chains, and crawl waste
When to use 301 vs 302, how redirect chains hurt SEO and speed, and how to check a live URL hop by hop.
Read · 8 min →Website not indexing in Google: a practical troubleshooting checklist
Why new or updated pages stay out of Google, how to read Search Console statuses, and which on-page fixes to try first.
Read · 9 min →Canonical tags explained: stop duplicate URLs from splitting your rankings
What rel=canonical does, when it should point to itself, www/https pitfalls, and how to check a live page.
Read · 8 min →