How to Check a URL Redirect Chain and Verify Where a Link Really Goes

Updated

Paste the URL into a redirect checker such as TrueURL, run the check, and read the result as a list of hops: each hop shows the HTTP status code (301, 302, and so on) and the address it points to, ending at the final destination. This works for any public link, including shortened ones, and lets you see where a link goes before you click it. The tool analyzes one URL at a time, so for several links you check them individually.

What a URL redirect is

A URL redirect is an automatic forward from one page to another. Sites use them when content moves, domains change, or traffic needs to be managed. The browser is told where to go next by an HTTP status code, most commonly 301 or 302.

Status Meaning Effect
301 Permanent redirect Search engines are told to transfer ranking signals to the new URL; preferred for permanent moves
302 Temporary redirect Signals the move is not permanent; ranking signals stay with the original URL

A single link can pass through several redirects in sequence. That sequence is the redirect chain, and the last address in it is the real destination.

Check a URL step by step

  1. Copy the full URL you want to inspect, including any shortened form (for example a bit.ly-style link) or an old address you suspect has moved.
  2. Paste it into the checker's search box and start the check. TrueURL performs the analysis in real time.
  3. Follow each hop in the results. The tool follows and analyzes every redirect in the chain and reports the status code for each step.
  4. Read the final destination. This is the page a visitor would actually land on.
  5. Check the timing data. Response time shows how long each step took; several slow hops can hurt user experience.

Expected result: a complete path from your input URL to the final URL, with an HTTP status code and timing for each step.

How to read the results

  • One hop, 301: the page moved permanently. Normal and usually fine for SEO.
  • One hop, 302: a temporary forward. Fine for short campaigns or A/B routing, but not ideal for a permanent move.
  • Several hops: each extra step adds latency. Look for chains that bounce between domains or repeat the same URL.
  • Final URL on HTTPS: a common and desirable pattern is an HTTP-to-HTTPS redirect for security.
  • No redirect: the URL resolves directly, with no forwarding.

Reveal where a shortened link really goes

Shortened URLs hide their destination, which is why they are used in phishing, malware downloads, scam pages, and social media or email scams. A URL unshortener such as TrueURL expands the link and shows the true destination without you clicking it.

To judge the result:

  • Confirm the final URL belongs to a source you trust.
  • Check that it uses HTTPS.
  • Be cautious with links in unsolicited messages, from unknown senders, or promising unrealistic offers.

Troubleshoot common problems

  • Redirect loop: the chain returns to an address it already visited. The site's redirect rules conflict; the link will not resolve for visitors either.
  • Broken link: a hop returns an error status instead of forwarding. The destination page has likely been removed or mistyped.
  • Slow multi-hop chain: several steps with high response times. Consolidate redirects where you control them, since each hop adds delay.
  • Unexpected destination: the final URL differs from what the link text suggested. Treat it as untrustworthy until verified.

Practical notes

TrueURL does not store or save the URLs you check; checks run in real time with no search history kept. It analyzes one URL per check, so bulk verification means repeating the steps for each link.