It follows a URL exactly the way a browser or search engine crawler would: request the URL, read the response, and if it's a redirect (a 3xx status with a Location header), follow it and repeat — up to 10 hops. Every hop is recorded with its own status code and redirect type, and the trace stops early if it detects the chain looping back on itself.
How to fix what it finds
- Multi-hop chains — update the original link or server rule to point straight at the final destination URL, skipping every intermediate hop.
- Temporary redirects used for permanent moves — switch the response code to a 301 (or 308 if the request method must be preserved) so search engines transfer ranking signal to the new URL.
- Loops — check your redirect rules (`.htaccess`, `next.config`, CDN/proxy rules, or CMS redirect settings) for two rules that point at each other, directly or through a longer cycle.