Free tool · 11 / CONNECT
Redirect checker.Every hop a link takes, and what it drops, no signup.
Follows a link hop by hop: every status code, and where UTM tags get dropped.
We look this up and don't keep it.
Try: · ·
3 redirects: the link ends at https://www.yourcompany.example/launch/spring/ (200 OK). utm_source, utm_medium and utm_campaign are dropped on the way.
An example: a made-up campaign link.
- 1
http://yourcompany.example/spring?utm_source=linkedin&utm_medium=paid_social&utm_campaign=spring_launch
→ http to https
- 2
https://yourcompany.example/spring?utm_source=linkedin&utm_medium=paid_social&utm_campaign=spring_launch
→ adds www; new path, /launch/spring; drops the query string; drops utm_source, utm_medium and utm_campaign
- 3
https://www.yourcompany.example/launch/spring
→ adds a trailing slash
- 4
https://www.yourcompany.example/launch/spring/
Tracking parameters in the link
- utm_source is dropped at hop 2 (302 to https://www.yourcompany.example/launch/spring), so the page that loads never sees it.
- utm_medium is dropped at hop 2 (302 to https://www.yourcompany.example/launch/spring), so the page that loads never sees it.
- utm_campaign is dropped at hop 2 (302 to https://www.yourcompany.example/launch/spring), so the page that loads never sees it.
- Hop 2 is a temporary redirect. Google uses a permanent redirect (301 or 308) as a sign the new URL should be canonical, and a temporary one as no such sign, so use a permanent one if the move is for good.
- Every extra hop is another round trip before the page starts loading. Pointing the first link straight at https://www.yourcompany.example/launch/spring/ skips 3 hops.
We follow the link from our servers with a plain request, the way a browser starts. We don't run JavaScript, so a redirect made by a script on the page won't show here, and a site that sends different visitors to different places may send you somewhere else.
Valley finds the people who viewed your company page or engaged with your posts, researches each one and writes to them. See how Valley does it ↗
NEXT STEP
Fed up with tracking clicks instead of starting conversations.Valley messages the people already circling you.
Book a demo ↗$500 a month for your first seat, $200 for each seat after that.
Status codes
What do 301, 302, 303, 307 and 308 redirects mean?What each code says, and how Google reads it.
301 and 308 are permanent redirects and 302, 303 and 307 are temporary. Google treats a permanent redirect as a signal that the new URL should be canonical and a temporary one as no such signal. 307 and 308 must keep the request method; a 301 or 302 may turn a POST into a GET.
| Redirect | Meaning (RFC 9110) | Request method | Google Search reads it as |
|---|---|---|---|
| 301 Moved Permanently | A new permanent URI | May change POST to GET, for historical reasons | Permanent |
| 302 Found | Temporarily under a different URI | May change POST to GET, for historical reasons | Temporary |
| 303 See Other | Redirects to a different resource | Changed to GET (Fetch standard) | Temporary |
| 307 Temporary Redirect | Temporarily under a different URI | Must not change | Temporary |
| 308 Permanent Redirect | A new permanent URI | Must not change | Permanent |
| Meta refresh, instant | Set in the page's HTML, not HTTP | Not applicable | Permanent |
| Meta refresh, delayed | Set in the page's HTML, not HTTP | Not applicable | Temporary |
Google's crawlers follow up to 10 redirect hops; browsers following the Fetch standard stop at 20.
From RFC 9110: HTTP Semantics, §15.4 Redirection 3xx ↗ · Google Search Central: Redirects and Google Search ↗ · WHATWG Fetch Standard: HTTP-redirect fetch ↗ · Google Search Central: How HTTP status codes, and network and DNS errors affect Google Search ↗, read 12 Nov 2026
How it works
How this tool works.And what it can't see.
Paste a link. Our server requests it without following redirects, reads the status code and Location header, and then requests the next address itself, one hop at a time, until a page answers, the chain loops, or it passes 20 hops. A page that answers 200 with a meta refresh counts as one more hop. We don't keep the link or anything we fetched.
For each hop you see the status code and its meaning, the time it took, and what changed on the way to the next address. Every campaign tag and ad click ID in the starting link is checked at each hop, so a dropped utm_campaign or gclid is pinned to the hop that dropped it.
Each next address must be a public website: we don't follow a redirect to an IP address, another port or another scheme, and say so when one does.
What it can't see: redirects made by JavaScript after a page loads, and redirects that depend on who's asking, such as by country, device or cookie. We request as one plain visitor from our servers.
Built by Valley.
Sources
- RFC 9110: HTTP Semantics, §15.4 Redirection 3xx ↗read 12 Nov 2026
- Google Search Central: Redirects and Google Search ↗read 12 Nov 2026
- Google Search Central: How HTTP status codes, and network and DNS errors affect Google Search ↗read 12 Nov 2026
- WHATWG Fetch Standard: HTTP-redirect fetch ↗read 12 Nov 2026
- Google Analytics Help: URL builders, collect campaign data with custom URLs ↗read 12 Nov 2026
- Google Ads Help: About auto-tagging ↗read 12 Nov 2026
Redirects
Get links where they're going.In as few hops as possible, with tracking intact.
A redirect is cheap to add and easy to forget. Here's what the standards and Google say about getting them right.
- 01
Permanent or temporary
RFC 9110 defines 301 and 308 as a new permanent URI and 302 and 307 as a temporary one. Google says it follows both, but only uses a permanent redirect as a signal that the target should be canonical. If a page has moved for good, a 301 or 308 says so.
307 and 308 were added to keep the request method unchanged; for a 301 or 302 a client may turn a POST into a GET. For ordinary links, which are GET requests, the pairs behave the same.
From RFC 9110: HTTP Semantics, §15.4 Redirection 3xx ↗ · Google Search Central: Redirects and Google Search ↗, read 12 Nov 2026
- 02
Keep chains short
Google says its crawlers follow up to 10 redirect hops, and browsers following the Fetch standard give up at 20. Short of those limits, each hop is one more request before the page starts loading. A link that goes http, then https, then www, then a trailing slash makes three requests where one would do: point it at the final address.
From Google Search Central: How HTTP status codes, and network and DNS errors affect Google Search ↗ · WHATWG Fetch Standard: HTTP-redirect fetch ↗, read 12 Nov 2026
- 03
Don't lose your tracking
Google Analytics collects campaign data from utm_ parameters in the link: source, medium, campaign, term, content, ID and three newer ones. A redirect that rebuilds the address without its query string drops them, and the visit arrives with no campaign.
Google Ads says that if a site uses redirects, the GCLID has to be passed through to the final landing page to track conversions. The same goes for other ad platforms' click IDs: the checker follows them hop by hop too.
From Google Analytics Help: URL builders, collect campaign data with custom URLs ↗ · Google Ads Help: About auto-tagging ↗, read 12 Nov 2026
- 04
Meta refresh and JavaScript redirects
Google treats an instant meta refresh as a permanent redirect and a delayed one as temporary. It says to use JavaScript redirects only when server-side and meta refresh redirects aren't possible, because it might never see one if rendering fails. This checker reads meta refresh tags, but doesn't run JavaScript.
A clean link gets people to the page. What turns them into a conversation is who you follow up with. See how Valley does it ↗
From Google Search Central: Redirects and Google Search ↗, read 12 Nov 2026
Questions
Questions people ask.
- What is a redirect checker?
- A tool that follows a link the way a browser does and shows every hop it takes: each address, its status code, and the page it finally lands on.
- How do I check where a link redirects?
- Paste it here. You'll see every hop with its status code, what changed at each step, and the final page.
- What is the difference between a 301 and a 302 redirect?
- A 301 is permanent and a 302 is temporary. Google uses a 301 as a signal that the new URL should be canonical, and a 302 as no such signal.
- What is a 308 redirect?
- A permanent redirect, like a 301, that must keep the request method, so a POST stays a POST.
- How many redirects are too many?
- Google's crawlers follow up to 10 hops and browsers stop at 20. Well before that, every hop adds a request, so one hop is the goal.
- Do redirects remove UTM parameters?
- Only if the redirect drops the query string. This checker shows the hop where each utm_ tag is kept or lost.
- Does a redirect keep the gclid?
- Only if it passes the query string on. Google Ads says the GCLID has to reach the final landing page to track conversions.
- Does Google follow meta refresh redirects?
- Yes. Google treats an instant meta refresh as permanent and a delayed one as temporary.
- Is this redirect checker free?
- Yes. It's free and needs no signup. We follow the link you paste and don't keep it.
Keep going
Try one of these next.
- UTM builderGTM opsBuilds UTM links one at a time or in bulk, and shows the GA4 channel each lands in.Open the tool
- Link preview checkerInbound, content and searchShows how a link previews on LinkedIn, X and Slack, and checks its Open Graph tags.Open the tool
- Robots.txt checker and generatorInbound, content and searchTests any URL against any crawler's robots.txt rules, or builds a new file.Open the tool
- AI crawler checkerInbound, content and searchShows which AI crawlers, GPTBot, ClaudeBot and others, can read a page, and why not.Open the tool