Redirect Tracer
Paste a URL to follow its entire redirect chain. The tool shows every hop with the HTTP status code (301, 302, 307, etc.) and the final destination. Essential for SEO auditing, affiliate link debugging, and verifying that your redirects resolve correctly.
returns
- data.final_url
- Where the redirect chain ends up.
- data.hops
- Each hop with its URL, status code and next location.
- data.total_hops
- Number of requests in the chain, including the last one.
- data.original_url
- The URL you started from.
Run it from your code
A temporary key takes one request and lasts seven days at 20 calls a day. Register and it becomes 75 a day, still free.
$ curl -s "https://apixies.io/api/v1/trace-redirects?url=https://github.com" \ -H "X-API-Key: $APIXIES_KEY" | jq '.data.final_url' "https://github.com/"
questions
What's the difference between 301 and 302 redirects?
A 301 is a permanent redirect — search engines transfer SEO value to the new URL. A 302 is temporary — search engines keep indexing the original URL. Using the wrong type can hurt your search rankings.
How many redirects are too many?
Google recommends no more than 3-5 hops. Each redirect adds latency and dilutes PageRank slightly. Long chains also risk being cut off by browsers or bots that enforce redirect limits.