Notes · 5 November 2026

We followed the redirects of 15 big sites: 12 of 30 start URLs took two hops or more

After a migration, people check that old URLs “redirect”. That is a weaker test than it sounds. To see what a real result looks like, we ran a plain HTTP request (curl, following redirects, 15 s timeout) on 5 November 2026 against the http:// and http://www. forms of 15 well-known domains: 30 start URLs.

What came back

ResultStart URLs (of 30)
One 301, ending on a 20012
Two to three hops before the final page12
First hop was a 302 (temporary)2 (mozilla.org, www.bbc.com)
Blocked with a 403 on the first request3 (weebly.com, www.weebly.com, www.nytimes.com)
Redirected, then a 403 on the final page2 (medium.com, www.medium.com)

The 12 two-hop cases are mostly www.example.com → example.com → https://…, or http → https → www: the host and the protocol are fixed in separate steps. Notion took three hops from notion.so to notion.com, and stripe.com ended on a localized /fr page, chosen by the server from where we were, not by the URL we asked for.

What this means for a migration check

Limits of this sample

Fifteen large sites, one request each from one server, one day. Big sites are not small migrated blogs, and results from a CDN can vary by location. We did not test deep URLs, only domain roots. It is a way to see what the common shapes look like, not a survey.

Run it on your own list

The free redirect checker follows each old URL and flags missing redirects, temporary (302) redirects, and landing pages that don't return 200. Paste your list (CSV, _redirects, .htaccess) and the new address. For a Wix move the usual gaps are described in the Wix 301 limits and the URLs your redirect map forgets.