Trace redirect chains hop by hop. Inspect status codes, security headers, robots.txt, canonicals, cookies and timing.
Users
1
store count
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
total ratings
Store rank
#364K
#299K among extensions
Version
1.0.30
updated 18 Nov 2026
Publisher and listing changes
From our daily record of this listing since 18 Nov 2026
No change of publisher name, contact email, website, privacy policy or listing name since 18 Nov 2026.
About HopTrace — Redirect & SEO Analyzer
HopTrace shows you the full path a URL takes before it lands. Open any page, click the toolbar icon, and you get every redirect in order: the status code, the exact Location header, how long each leg took, and which server answered. Then it tells you what the final page says to browsers and crawlers, and what the detour cost you.
It is built for developers, SEO practitioners, site owners, marketers checking campaign links, and anyone who has typed one address and ended up somewhere else without knowing why.
WHY REDIRECTS DESERVE A CLOSER LOOK
Browsers hide redirects. You type http://example.com, the address bar settles on https://www.example.com/en/, and nothing tells you that three servers were involved on the way. Most of the time that is fine. Some of the time it is the cause of a problem you are trying to find:
A migration left an old 302 in place, so search engines never moved ranking to the new URL.
A hostname redirect and an HTTPS upgrade run as two separate hops, adding a round trip to every first visit.
A tracking link passes through a shortener, an ad server and a consent wall before it reaches the landing page, and the UTM parameters are gone by the end.
A canonical tag points to a URL that itself redirects.
A loop only shows up for users without a cookie.
A security header is set on the redirect but missing on the page that actually loads.
You can find all of this with DevTools, curl and a robots.txt tester. HopTrace puts it in one popup, for the tab you are already on, without leaving the page or retyping anything.
THE FIVE VIEWS
CHAIN
Every hop from the URL you asked for to the page you landed on. Each is numbered, timed and labelled with its status code. A waterfall at the top shows where the time went at a glance.
Server redirects (301, 302, 303, 307, 308) are told apart from client-side ones such as meta refresh and JavaScript navigation, and from history changes made with pushState that never left the page.
HTTP to HTTPS upgrades are marked, including internal 307s produced by HSTS, so you can see whether the browser or the server did the upgrade.
Redirect loops are called out at the hop where they start.
Mixed-content downgrades, where an HTTPS page sends you to plain HTTP, are flagged.
Each hop shows the server IP and, optionally, the country and network operator that host it.
Expand any hop to read its full request and response headers.
SECURITY
The security headers on the final response, scored out of 100 and given a letter grade. Each check shows the value the server sent. Failed or weak checks explain why the header matters and what to set instead, so the result is something you can hand to whoever runs the server.
Checks include:
HTTPS
Strict-Transport-Security, including max-age, includeSubDomains and preload
Content-Security-Policy
X-Frame-Options
X-Content-Type-Options
Referrer-Policy
Permissions-Policy
Cross-origin isolation headers
Cookies set anywhere along the chain, with their Secure, HttpOnly and SameSite flags
SEO
What the destination page tells search engines, and whether the crawler you care about is allowed to fetch it.
Index and follow status from the robots meta tag and X-Robots-Tag
The canonical URL, and whether it is self-referencing, points elsewhere, or is missing
robots.txt fetched from the site and evaluated for this exact URL, per crawler: Googlebot, Bingbot, YandexBot, Baiduspider, DuckDuckBot and the wildcard agent
The sitemap declared in robots.txt
Title, meta description, heading structure and Open Graph tags
PAGE
How the landing page loaded and what it contains.
Navigation timing: DNS, connection, TLS, time to first byte, DOM interactive, DOM content loaded
Transfer size and HTTP protocol version
Link inventory: total, internal, external, follow and nofollow
Language, character set, title and description
COST
Every extra hop is a round trip that some visitors do not wait for. The Cost view estimates what the chain costs in visitors and revenue, per hop, per month and per year. Enter your own monthly sessions and RPM (ad revenue, affiliate or blended) and the figures update.
The model is deliberately conservative and shown in full in the popup: roughly 8 percent abandonment per server-side redirect, roughly 12 percent per client-side redirect because of the longer perceived delay, and a further 0.7 percent per 100ms of hop latency. Your real numbers will differ by audience, device and connection. The point is to put a rough figure next to a redirect before deciding whether collapsing two hops into one is worth a ticket.
WHAT IT LOOKS LIKE ON A REAL SITE
The screenshots on this listing are the shipped extension running on tomshardware.com. They are real traces, not mock-ups.
Type tomshardware.com into the address bar and the server answers with a single 301 that goes straight from http://tomshardware.com/ to https://www.tomshardware.com/, upgrading the scheme and adding www in one step. This is how it should be done. Many sites split that into two hops, one for HTTPS and one for the hostname, and pay an extra round trip on every visit that starts from a bare domain. HopTrace makes the difference visible in one glance at the Chain view.
The security headers grade C, 60 out of 100. HTTPS, HSTS with includeSubDomains, and X-Frame-Options are in place. X-Content-Type-Options is missing, and HopTrace explains what that allows and the one-line header that fixes it. The Content-Security-Policy is present but only sets frame-ancestors; HopTrace notes that object-src and base-uri are unrestricted and what to set for each. Referrer-Policy is not set, so the browser default applies.
The SEO view shows a self-referencing canonical, a robots.txt that allows every major crawler, and the main, UK and news sitemaps the site declares. The Page view shows a 10ms time to first byte, 364 KB transferred over HTTP/3, and 532 links on the home page.
None of this needs access to the site's servers or analytics. Everything HopTrace s…
Version history
1 versions recorded
No update since 18 Nov 2026 changed the permissions or site access.