Item logo image for HopTrace — Redirect & SEO Analyzer

HopTrace — Redirect & SEO Analyzer

ExtensionTools4 users
Item media 5 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 1 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 2 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 3 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 4 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 5 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 1 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 1 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 2 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 3 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 4 (screenshot) for HopTrace — Redirect & SEO Analyzer
Item media 5 (screenshot) for HopTrace — Redirect & SEO Analyzer

Overview

Trace redirect chains hop by hop. Inspect status codes, security headers, robots.txt, canonicals, cookies and timing.

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 shows comes from what your browser already saw. HOW TO USE IT 1. Browse as you normally would. HopTrace observes navigations in each tab in the background. 2. Click the HopTrace icon. The popup opens on the trace for the tab you are looking at. 3. Switch between Chain, Security, SEO, Page and Cost. Expand a hop to see its headers. 4. Use the reload button to trace the page again, for example after you change a server rule. 5. Copy the trace, or export it, to paste into a ticket, a pull request or a chat with your host. Each new tab starts a fresh trace. Navigations within a tab are chained together, which is how multi-step redirects are reconstructed, so open a new tab when you want a clean run for a different URL. WHO USES IT Developers checking that a deploy, a new route or a CDN rule redirects the way it was meant to. SEO specialists auditing migrations, canonicals, 301 versus 302, and robots rules for a specific crawler. Site owners and agencies who want a readable security header report without running a scanner. Performance marketers and affiliates following a tracking link through every server it touches, and seeing what each hop costs. Support and QA teams who need to describe exactly where a link went wrong. PRIVACY No account. No tracking. No advertising. No analytics. HopTrace observes navigations using the webRequest and webNavigation events Chrome provides to extensions. It does not modify, block, redirect or inject into any request or page. It registers no blocking listener. Traces are stored in a local database in your own browser profile. They are never uploaded to us or to anyone else. The 500 most recent traces are kept and anything older than 30 days is deleted automatically. One button in Options deletes everything, and uninstalling removes it too. Cookie values are never stored, only cookie names and their security attributes. The extension makes two kinds of outbound request. Both are optional and can be switched off in Options, and HopTrace works fully without them: robots.txt is fetched from the site being traced, as a plain request with no added headers, cookies or body, so crawl rules can be evaluated. The IP address of a server in the chain is sent to ipwho.is over HTTPS to label it with a country and network operator. Only that server IP is sent. Your own IP address, the URL, your cookies and your headers are not. The full privacy policy is at https://rpiem.com/hoptrace/privacy PERMISSIONS, AND WHY EACH ONE IS NEEDED webRequest: to read the status code, Location header, response headers, cookies and timing of each request in a navigation. Read only. webNavigation: to know when a navigation starts, commits and finishes, so hops can be grouped into one trace, and to tell a server redirect from a client-side history change. tabs: so the popup can show the trace for the tab you are looking at, and so hops are attributed to the right tab. storage: to remember your preferences and keep your trace history on your device. Access to all sites: redirects cross domains by nature. A link on one site can pass through three others before it lands, and HopTrace has to be able to see each of those hops. It reads them. It never changes them. REQUIREMENTS Google Chrome 114 or later, or another Chromium browser that supports Manifest V3 extensions. Free, with no sign-in, no subscription and no companion app. SUPPORT Questions, bug reports and feature requests: https://rpiem.com/hoptrace/support When reporting a problem, the URL you traced, your Chrome version and a screenshot of the popup help us reproduce it quickly. HopTrace is developed and published by Aucuparia Holdings LTD under the RPIEM name.

Details

  • Version
    1.0.30
  • Updated
    November 18, 2026
  • Offered by
    rpiem
  • Size
    101KiB
  • Languages
    English
  • Developer
    Email
    nick@rpiem.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization

HopTrace — Redirect & SEO Analyzer has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

HopTrace — Redirect & SEO Analyzer handles the following:

Web history
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Search
Clear search
Close search
Google apps
Main menu