Redirect Checker

301 and 308 are permanent and pass link signals. 302 and 307 are temporary and tell search engines to keep indexing the original URL. Using 302 for a permanent move is one of the most common and costly redirect mistakes.

One. Every extra hop adds latency and costs crawl budget, and Google stops following after about five. A chain of three should be flattened to one.

Modern Google passes essentially full PageRank through 301s, so the loss is not the issue. Crawl budget, latency and the risk of a broken middle hop are.

A URL that eventually redirects back to itself. Browsers give up after about twenty hops and show an error; crawlers give up much sooner and drop the URL.

Indirectly. Google follows up to about five hops, so a long chain risks the destination never being reached, and every hop adds real latency for users. Flatten chains to one hop.

Both are temporary. A 307 guarantees the request method is preserved, so a POST stays a POST. A 302 historically allowed clients to convert POST to GET, which some still do.

At the edge, before the request reaches your origin. It is faster and it means the redirect still works if the origin is down.

At least a year, and indefinitely if the old URL still has external links. Redirects are cheap; broken links are not.