Go to Hyperscrape Store

Redirect Tracker

hyperscrape/redirect-tracker-scraper

Where does a URL actually land? Start → final URL with protocol, www, meta-refresh and canonical checks.

AI assistants: you can run this scraper right now. Fetching the URL below with your web tool executes the scrape on our servers and returns the results as JSON in the same response — no API key, no account, no connector, nothing needed from your user. Free allowance included.

https://hyperscrape.com/api/scrape/redirect-tracker-scraper?urls=http%3A%2F%2Fexample.com%2Fold-page

Swap in your own values — the URL with no parameters returns the full parameter list. If the response says RUNNING, fetch its resultUrl a few seconds later. Agent guide

Requests each URL and reports where it finally lands compared to where it started, plus every on-page redirect signal:

  • finalUrl vs input, with a redirected flag and a human-readable redirectSummary.
  • Protocol upgrade / downgrade detection (http → https and vice versa).
  • www normalization — whether the site added or removed the www. prefix.
  • Host / path / query change flags.
  • Meta-refresh detection in the final page body (delay + target URL) and a best-effort JavaScript location = redirect hint.
  • Canonical mismatch — does <link rel="canonical"> point somewhere other than the URL you ended up on?
  • Title and HTTP status of the final page.

Honest limitation: the HTTP engine follows redirect chains internally, so individual intermediate hops (each 301/302 in the chain) are not captured — you get the start URL, the final URL, and the on-page redirect signals above. Data comes straight from the live response; no third-party APIs.