trueurl.com

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.

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.

HTTP status codes in a redirect chain tell you why each hop happened and whether it is meant to last. A 301 means a permanent move (search engines should transfer ranking signals to the new URL), while a 302 means a temporary detour. Other 3xx codes (303, 307, 308) also redirect but differ in method handling and permanence. To verify where a link really goes, follow every hop in order, read each status code, and check the final destination URL, its protocol (HTTPS vs HTTP), and the response time of each step. Tools like TrueURL display the complete chain with status codes and timing data, which is exactly what you need to interpret a redirect.

The role of HTTP status codes in redirects

A redirect is the server's way of saying "the resource you asked for is elsewhere." The status code is the instruction that tells the browser (and search engines) how to treat that move.

For most link-checking tasks, the distinction that matters is 301 vs 302, because it changes how search engines and browsers cache the move.

301 vs 302: why it matters

• 301 (permanent): search engines are told to transfer ranking power to the new URL. Browsers may cache it aggressively, so a mistaken 301 can be hard to undo.
• 302 (temporary): signals that the move isn't permanent. Ranking signals stay with the original URL. Useful when the destination may change.

TrueURL's FAQ puts it plainly: for SEO purposes, 301 redirects are usually preferred for permanent changes, while a 302 indicates the move isn't permanent. If you're auditing a site migration, a 302 where you expected a 301 is a red flag worth fixing.

How to read a redirect chain step by step

A redirect chain is the ordered list of hops from the URL you entered to the final page. Reading it correctly means checking three things at each step: the status code, the destination, and the response time.

1. Start with the URL you were given. This may be a shortened link, an affiliate link, or an old page URL.
2. Record the first status code. A 301 or 302 here tells you the first move is permanent or temporary.
3. Follow each hop in order. Each intermediate URL should have its own status code. A healthy chain is usually short (one or two hops).
4. Identify the final destination. This is the URL that returns a 200 (OK) rather than another 3xx. This is where the link really goes.
5. Check the final URL's protocol and domain. Confirm it uses HTTPS and belongs to the domain you expect.

TrueURL follows this same flow: you paste a URL, it tracks every redirect in the chain including status codes, and returns the complete path with timing data and HTTP status codes. It analyzes one URL at a time, so bulk checks require repeating the process per link.

A concrete example

Suppose you check http://example.com/old-page and see:

Reading it: the old page permanently redirects (301) to the HTTPS version of the new page, which loads successfully (200). The chain is healthy: one permanent hop, upgrade to HTTPS, fast responses, and a final destination on the expected domain.

Now compare a suspicious chain:

Here the link bounces through a tracker, lands on an unexpected domain, drops to plain HTTP, and each hop is slow. That combination is a warning sign, not a clean redirect.

Warning signs in a redirect chain

• Loops: a URL that redirects back to an earlier URL in the chain, or to itself. This usually means a misconfigured server rule and results in a browser error.
• Unexpected domains: a shortened or affiliate link that ends on a domain unrelated to the brand you expected. Shortened URLs can hide malicious destinations such as phishing sites, malware downloads, or scam pages, which is why unshortening before clicking matters.
• Missing HTTPS: a final destination on http:// rather than https://. TrueURL's FAQ specifically notes that checking redirects helps ensure sites properly redirect from HTTP to HTTPS for security.
• Excessive hops: long chains add latency and can dilute SEO value. Multiple slow redirects negatively impact user experience.
• Temporary codes on permanent moves: a 302 where a 301 belongs, especially after a site migration.

How status codes and response times work together

Response time shows how long each step in the chain took. Status code and timing together tell you whether a redirect is correct and whether it is fast:

• 301/302 with fast response (tens to low hundreds of ms): normal, healthy redirect.
• 3xx with very slow response (seconds): the redirect works but the server is sluggish; users and crawlers wait at each hop.
• 200 after a short chain: the destination is reachable and the link is clean.
• 4xx or 5xx at the end: the chain leads to a broken or erroring page, even if the redirects themselves were valid.

Faster response times generally indicate better server performance, so a chain of several slow hops is a performance problem even when every status code is technically correct.

Practical takeaways

• Treat 301 as permanent and 302 as temporary; verify the code matches the intent, especially after migrations.
• Always read the final destination, not just the first hop, before clicking shortened or affiliate links.
• Watch for loops, unexpected domains, HTTP-only destinations, and slow hops as signs of a broken or risky link.
• Use a redirect checker that shows status codes and timing per hop; TrueURL does this for one URL at a time and states it does not store the URLs you check.

A 301 redirect is a permanent HTTP redirect: the server tells the browser (and search engines) that the requested URL has moved for good and that the new URL is the canonical destination. You verify one by requesting the old URL and reading the status code and Location header at each hop until you reach the final page. Use a 301 when a URL change is permanent, such as an HTTP-to-HTTPS migration, a domain move, or a renamed page; use a 302 when the change is temporary.

301 vs. 302 and Other Redirect Codes

The status code is the server's statement about permanence, and that statement is what search engines act on.

For SEO, TrueURL's FAQ notes that a 301 tells search engines to transfer ranking power to the new URL, while a 302 signals the move isn't permanent. That is why 301 is usually preferred for permanent changes. The distinction matters most when the old URL has accumulated links or rankings you want carried over.

How to Verify a 301 Redirect

You can check a single URL with command-line tools or trace the full chain with a redirect checker.

Check the status code directly

Send a request without following redirects and read the response headers:

curl -I https://example.com/old-page

Expected result: a line like HTTP/1.1 301 Moved Permanently followed by a Location: header pointing to the new URL. If you see 200 OK instead, the old URL is serving content directly and no redirect exists. If you see 302, the move is marked temporary.

Trace the full chain

A single request only shows the first hop. To see every step, follow redirects and print each response:

curl -IL https://example.com/old-page

Each block of headers represents one hop. Read them in order: the first status code and Location, then the next, until a 200 appears. That final 200 URL is where the link really goes.

Use a redirect checker

TrueURL follows and analyzes every redirect in the chain, including status codes, and shows the complete path with timing data. The workflow is: paste the URL into the search box, let the tool follow each redirect, then review the results for the status code at each step and the final destination. This is useful for shortened links, where the visible URL hides the true target. TrueURL's FAQ states it doesn't store or save checked URLs and analyzes one URL at a time, so bulk checks require running each URL individually.

What to Look For in the Results

• First-hop code: Confirm the old URL returns 301, not 302 or 200.
• Final destination: The last 200 URL should be the page you intend, on the domain you intend.
• Chain length: Each extra hop adds latency. A long chain of redirects is a sign of accumulated, unmanaged rules.
• Response time per hop: TrueURL reports timing for each step; multiple slow redirects can hurt user experience.
• Protocol: For HTTP→HTTPS migrations, the chain should end on an https:// URL.

Common Causes of Redirect Problems

Redirect loops. Two rules point at each other (A→B and B→A), so the browser gives up with an error. Spot it when the chain never reaches a 200 and repeats the same URLs.

Long chains. Old redirects were never updated after later changes, so A→B→C→D. Collapse them by pointing the original URL directly at the final destination.

Unexpected 301s. A page you thought was live returns 301 because a CMS or server rule still maps the old path. Checking the status code directly confirms whether the redirect is intentional.

Temporary moves marked permanent. A 302 used for a permanent change, or a 301 used for a temporary one, sends the wrong signal. Match the code to the intent.

Practical Checks for Common Migrations

• HTTP to HTTPS: Request the http:// version and confirm a 301 to the https:// equivalent, not a 302 and not a direct 200 on both.
• Domain migration: Confirm the old domain's key URLs return 301 to the corresponding new URLs, and that the chain ends on the new domain.
• Renamed pages: Verify the old path 301s to the new path, and that the new path itself returns 200.

If a check shows the wrong code or an unexpected destination, the fix belongs in the server or CMS redirect rules, not in the link itself. Re-run the same check after the change to confirm the chain now ends where intended.