This matters for local SEO more than most owners expect. After a site move, a new service page or a city page rename, one wrong redirect can send both visitors and Google to a dead page.
The checker follows up to 10 hops and works on any public URL.
How to use the HTTP status code checker
Quick answer
Enter the full URL, including https://, and press Check redirects. The tool requests the page and follows each redirect, listing every step with its status code. Read the list from top to bottom: the last row is the page a visitor actually lands on.
Check the old address, not the new one. If you moved a page from /plumbing to /services/plumbing, test /plumbing and confirm it ends on the new page with a single permanent redirect.
The tool allows 10 checks per minute. If you hit the limit, wait a minute and run the rest.
What each status code means
Quick answer
A 200 means the page loads. A 301 or 308 is a permanent redirect, and 302, 303 and 307 are temporary redirects. A 404 means not found, 410 means gone for good, and any 5xx code is a server error. Use permanent redirects for pages that moved for good.
Google treats permanent redirects as a strong signal that the new URL should replace the old one in its results. Temporary redirects tell it the original may come back.
| Code | Meaning | Typical use |
|---|---|---|
| 200 | OK | Normal page |
| 301 / 308 | Permanent redirect | Page moved for good |
| 302 / 303 / 307 | Temporary redirect | Short-term move, A/B test |
| 404 | Not found | Deleted page with no redirect |
| 410 | Gone | Page removed on purpose |
| 500 / 503 | Server error | Hosting or code problem |
301 vs 302 redirects for local pages
Quick answer
Use a 301 when a page has moved permanently, such as renaming a service page or switching a city page URL. Use a 302 only when the move is temporary, like sending visitors to a seasonal offer. Mixing them up is one of the most common technical mistakes on small business sites.
A common case: a plumber's site builder wraps every redirect as a 302 by default. The old URL keeps showing in search results for months because Google keeps expecting the original page to return.
Find and fix redirect chains
Quick answer
A redirect chain happens when URL A redirects to B, which redirects to C. Each extra hop slows the page and wastes crawler effort. Point A straight at C. The checker shows every hop, so you can spot chains of two or more redirects at a glance.
Chains usually pile up after several redesigns: http to https, then non-www to www, then an old page to a new page. Fix them by updating the first redirect rule to send people to the final address.
Google's documentation says Googlebot follows up to 10 redirect hops, but a shorter path is faster for every visitor.
- Update old redirect rules to point straight at the final URL
- Update internal links so they do not use redirected URLs at all
- Re-check the chain after each change
What to do when the result is a 404 or a 5xx
Quick answer
A 404 at the end of a chain means the redirect points to a page that no longer exists, so fix the target or restore the page. A 5xx means the server failed, so check your hosting or ask your developer. Re-run the checker after each fix to confirm.
For a deleted page with a close replacement, redirect it to that replacement. For a page with no relevant replacement, a plain 404 or 410 is fine. Redirecting everything to the home page confuses visitors.
Check redirects after a site move or redesign
Quick answer
After any move, test your top pages: the home page, every service page, every location page and any page with backlinks. Each old address should end on the right new page with a single permanent redirect.
Make a list of the old URLs before the move and test them one by one afterwards. Use Google Search Console to find the pages that matter most.
Fix any old address that ends in a 404, loops or lands on the home page when a closer page exists.
HTTPS and www redirects
Quick answer
Your site should load at one preferred address only. The http version and the other of www or non-www should redirect permanently to it.
Test all four variants: http with and without www, https with and without www. Three of them should end on the fourth with one hop.
This also keeps your analytics and links clean, because every visit and link counts for one address.
Redirect loops and how to read them
Quick answer
A loop happens when two or more URLs send visitors to each other forever. Browsers show an error and the page never loads. The checker stops at 10 hops and shows you the repeating pattern.
Loops often come from conflicting rules, such as a plugin forcing www while the server removes it.
Remove one of the conflicting rules, clear your cache and test again.
Redirects and your Google Business Profile link
Quick answer
The website link on your Google Business Profile should go straight to a live page, not through a chain. Test it and use the final URL if it redirects.
Extra hops slow the visit and can break tracking parameters.
Also check the links in your citations and social profiles, which are often the oldest ones to go stale.
Keep reading
Sources: Google Search Central: Redirects and Google Search, Google Search Central: Googlebot