Skip to content
Pre-order BookBook a Consultation

Follow the journey

Every redirect tells a story. Follow yours.

An old link should still take someone somewhere useful. Trace the HTTP journey, see where it ends and find the detours worth investigating.

Trace a URL

Redirect Checker

Start with the link people actually use.

Paste the original URL from a campaign, old page or navigation link. The report follows up to five HTTP redirects and shows the response at each step.

01 / Start with a URL

Follow every redirect.

Check one public URL, following up to five HTTP redirects. No sign-in needed.

What this check covers

We make server-side GET requests without browser cookies. JavaScript and meta-refresh redirects are not followed. Results can vary by location, user agent and access controls.

Request duration is measured from our server for a bounded response. It is not page load time or a Core Web Vitals measurement.

02 / The route it takes

Your redirect report

Enter a URL to see the chain, status codes and destination.

Understand the report

A move, a detour or a dead end?

Read the route before changing it. These are illustrative paths, not live results from your website.

301 / 308

A permanent move

Check that the destination is the closest useful replacement. A homepage is not automatically the right place for every retired URL.

302 / 307 / 303

A different kind of handover

Temporary redirects can be intentional. A 303 commonly points to a separate response after an action. Review the purpose before changing the status.

4xx, loops or incomplete checks

Investigate the stop

Check the URL, access restrictions and redirect rules. An incomplete fetch is not proof that every visitor sees a broken page.

Illustrative example

One destination. Fewer handovers.

A protocol change followed by a renamed page can create two redirects. If both moves are permanent, review whether the original URL can go straight to the final page.

  1. Original link

    http://example.com/old-service

    301 · Move to HTTPS

  2. Intermediate stop

    https://example.com/old-service

    301 · Move to the new page

  3. Final page

    https://example.com/services/new-service

    200 · Page responds

Suggested route to test: original URL → final page. Keep old external links working and update internal links to the intended destination.

Before you move on

Turn a trace into a useful fix.

  1. Record the exact starting URL

    Keep the query string. Campaign parameters and URL variants can change the route.

  2. Agree on the intended destination

    Check the page is relevant, usable and still carries the information the visitor expected.

  3. Retest after the change

    Check the original link again, then inspect it in a browser. This tool does not run JavaScript or follow meta-refresh redirects.

Your questions

Know what the check can tell you.

Is the request time a page-speed score?

No. It is the duration of this server request, not a full browser load or a Core Web Vitals measurement.

Why can my browser and this tool disagree?

Cookies, location rules, authentication, bot protection and JavaScript can produce different experiences. Compare the exact URL and test the real visitor journey too.

Will it preserve my campaign tracking?

It shows the URLs and Location headers in the route. Review the final query string; use the Campaign Link Checker for a more focused campaign-link check.

Found a route that needs untangling?

Send us the starting URL, the report and where the visitor should finish. We can help turn scattered redirects into a clearer journey.

Send an enquiry

Let’s talk

Start the conversation.

Your details will be used to respond to your enquiry. Privacy policy

The Margarita Funnel

Your cart 0

Loading your cart…