Official site — always check you are on kripicard.comVerify
SEO tools
Follow a URL through every hop it takes, with the status code, timing and server for each one. The destination is easy to see in a browser — the path it took, and whether that path is costing you, is not.
Try the http:// version of a site to see the upgrade chain most sites have.
| Code | Meaning | Effect on indexing |
|---|---|---|
| 301 | Moved permanently | Destination replaces the original in the index |
| 302 | Found (temporary) | Original URL stays indexed |
| 303 | See other — forces GET | Treated as temporary |
| 307 | Temporary, method preserved | Same as 302 |
| 308 | Permanent, method preserved | Same as 301 |
Almost nobody sets out to build a four-hop redirect. They accumulate one migration at a time: http upgrades to https, the bare domain moves to www, an old path is renamed, then the site restructures again. Each rule was reasonable on its own, and the result is http://example.com/old taking four requests to reach its destination. The fix is to rewrite the earliest rule to point straight at the final URL rather than adding another layer on top.
301 for anything permanent. It tells search engines to move the indexed URL to the destination and transfer the ranking signals. A 302 says the original URL is still the right one and will be back, so Google keeps the old URL indexed. Using 302 for a permanent move is one of the most common migration mistakes, and it can hold rankings on a URL that no longer exists.
Not meaningfully any more. Google confirmed in 2016 that 30x redirects pass full PageRank. The real costs of a long chain are latency for users and crawl budget, not lost equity.
Google follows up to about five hops in a single crawl attempt, then gives up and tries again later — which delays indexing. Browsers typically allow around twenty before erroring. One hop is ideal, two is acceptable, and beyond three you should point the first URL directly at the final destination.
Usually two rules fighting: one forcing https and another forcing a trailing slash, or a CDN and an application both rewriting the same path. The result is ERR_TOO_MANY_REDIRECTS in the browser and an abandoned URL for crawlers. This tool detects the loop and shows which hop closes it.
307 guarantees the HTTP method is preserved — a POST stays a POST. 302 was ambiguous in the original spec and many clients silently converted POST to GET, which is why 307 exists. For plain page redirects the SEO effect is identical: both are temporary.
Google treats an instant meta refresh much like a 301, but it is a poor substitute. It is slower, it briefly renders the intermediate page, and delayed versions are not treated as redirects at all. Use a server-side status code whenever you can.