Redirect chains: why one hop is enough

What each type of redirect tells Google

The HTTP standard (RFC 9110) separates permanent redirects (301 and 308) from temporary ones (302 and 307). Google treats them differently, as its documentation on redirects explains.

• A 301 or 308 says the URL has moved. Google reads it as a strong signal that the new URL should be the one shown in search results.
• A 302 or 307 says the move is temporary. Google keeps showing the old URL in its results.
• A meta refresh is an instruction inside the page itself. Google treats an instant one as permanent and a delayed one as temporary.
• A JavaScript redirect is only seen if Google manages to run the page's script. Google recommends it only when no other method is available.

A 302 left in place after a permanent move breaks nothing for visitors. It just lets search engines keep showing a URL that is no longer the right one.

Where redirect chains come from

Nobody plans a redirect chain. It forms when each change adds its own rule on top of the previous ones instead of replacing them. Moving to HTTPS, then picking the www version, then adding a folder per language can give: http://example.com redirects to https://example.com, which redirects to https://www.example.com, which redirects to https://www.example.com/en/. Three hops where one would do.

Internal links that still point to old URLs, and a canonical URL that points to a redirected page, lengthen the path the same way.

Google's crawlers follow up to ten hops. Its documentation does not put a number on any ranking loss from a chain, but it advises redirecting straight to the final destination. Beyond the time lost on each visit, a chain makes the site fragile: any intermediate rule can be removed or edited by someone who no longer remembers what it connected.

What we find on the sites we audit

This percentage covers about 30 websites we audited between August 14, 2026 and September 24, 2026, the ones where this point could be checked. Many were audited because a defect showed up quickly, so the figure describes our audits, not websites in general.

What the audit checks, and why

The audit follows redirects in a browser, as a visitor would, and records every hop with its status code.

• Your site's entry URLs, over http and https, with and without www: how many hops before the page, whether each one is permanent or temporary, and any loop that stops the page from loading.
• The hops your server sends, and only those. Recent browsers switch from http to https on their own and report it as a redirect, although no server sent one. The audit leaves that hop out, because counting it would flag the most correct setup as a chain.
• Meta refresh and JavaScript redirects used where the server should answer itself.
• Consistency between the www and non-www versions: one should redirect to the other. If both serve the page, your homepage exists twice.
• Each page's canonical URL, the one search engines should keep: it must lead straight to a page that responds, with no redirect, no error and no noindex directive.

The threshold is two hops. One hop, from http to https for instance, is how a redirect normally works and does not count. Two hops mean one rule follows another instead of replacing it.

What is a quick fix, and what takes a project

A chain is fixed at its source: the first rule should lead straight to the final URL. Adding another redirect to patch a path makes the chain longer, not shorter. Internal links and canonical URLs that point to an old URL get updated to the right one.

Turning a 302 into a 301 is usually done in the server or CMS settings, without touching the pages.

It becomes a project when rules have piled up in several places: at the host, in the CMS, in a service placed in front of the site. The first job is to find out which layer sends which hop. It is also what a well-run SEO migration prepares: a map where each old URL leads to its new page in a single hop.

What this check doesn't tell you

By Quentin Mathis, Z29K · updated September 28, 2026