What is a redirect chain on a local URL?
A chain is more than one redirect between the URL someone requests and the page that finally returns 200, for example an old location path that hops through a renamed folder before the live branch page.
A single permanent redirect to the equivalent new URL is the intended pattern after a move. This article is about leftover extra hops, not the whole post-launch migration checklist: why Local SEO can drop after a website redesign.
Problem
A → B → C → live page Extra hops add latency. Googlebot follows a limited number of redirects in a chain.Common local hops
http, www, slash, old CMS paths Location and service URLs collect leftover rules from redesigns and plugin changes.Fix
A → live page in one hop Google advises redirecting to the final destination directly, and keeping any remaining chain short.Align
Links, canonical, sitemap, GBP Anything that still points at A or B keeps the chain alive for users and crawlers.Recheck
Trace important URLs again Confirm one permanent hop and a 200 on the final location or service page.
Do chains actually hurt?
They add latency for users. Not every browser or user agent handles a long chain. Googlebot can follow up to ten hops, but Google advises redirecting to the final destination directly, and keeping any unavoidable chain ideally to no more than three and fewer than five.
Long redirect chains also have a negative effect on crawling efficiency. Sources: Site moves with URL changes and Troubleshoot crawling errors. Do not treat “PageRank leakage” folklore as a current Google ranking rule.
How do I confirm the hops?
Trace the URL. Record each status code and destination until you reach 200, 404 or a loop.
Mix-ups to log: 301 then 302 then 301; HTTP to HTTPS to www to slash; a CMS plugin hop through a temporary URL. Inspect the final URL in Search Console. If Google selected a different canonical, that is a related but separate diagnosis: why Google chose a different canonical for a location page.
Where do local chains come from?
Location and service URLs collect rules from redesigns, trailing-slash plugins, HTTPS migrations, store-locator path changes and closed-location redirects that later moved again.
Multi-location sites often redirect an old /stores/city/ to /locations/city/ to
/locations/city-name/ because each project added a rule without collapsing the previous one.
How should I collapse them?
Point every old address straight at the final live location or service URL with a server-side permanent redirect (301 or 308). Then update the intermediate rules so they also target that final URL.
Google recommends HTTP permanent redirects when you can. Temporary 302 or 307 redirects are for temporary moves. A chain that mixes types makes it harder to see which URL should be canonical. Source: the site-move documentation above and how to specify a canonical URL.
What else must point at the final URL?
Internal links, rel=canonical, the XML sitemap and Google Business Profile website fields should name the live URL, not a hop.
Linking consistently to the URL you consider canonical helps Google understand that preference. Sitemaps are a weaker canonical signal than redirects or rel=canonical, but listing redirecting URLs still wastes the hint.
Hop diagnostic table
| Chain pattern | Typical local cause | Collapse to | Also update |
|---|---|---|---|
| http → https → www → slash | Host rules stacked over years | One hop from any variant to the live URL | Canonical and internal links |
| Old folder → new folder → current slug | Repeated CMS migrations | Old folder → current slug | Sitemap and GBP landing page |
| Location → homepage → location | Broken catch-all plus a later fix | Location → correct location only | Remove the homepage hop |
| 301 → 302 → 301 | Temporary rule left in place | Single 301/308 to the final page | Confirm the move is permanent |
| Loop | Two rules pointing at each other | Break the loop; one destination | Test in a tracer until 200 |
What should I not do?
Action checklist
- Crawl or sample important location, service, contact and GBP landing URLs.
- Record hop count, status codes and the final 200 URL.
- Rewrite rules so each old address hits the final URL in one permanent hop.
- Change internal links, canonicals and sitemaps to the final URL.
- Update Google Business Profile website links that still use a hop.
- Re-trace after deploy. Confirm no loops and no 404 at the end of a chain.
When professional help makes sense
Help is useful when rules live in several layers (CDN, server, CMS, plugin), when a franchise has years of stacked location paths, or when GBP links, sitemaps and canonicals still name hop URLs. Collapsing hops does not guarantee recovered rankings.
Sources and further reading
- Google Search Central: Site moves with URL changes
- Google Search Central: Troubleshoot crawling errors
- Google Search Central: Specify a canonical URL
Location and service URLs still hopping through old paths?
Otepsphere can map redirect hops on the URLs that matter for Local SEO, collapse them to the live pages, and check that profile links, sitemaps and canonicals name the same destinations.
Contact OtepsphereWho writes this
This page is published by Otepsphere, a specialist Local SEO consultancy. A named founder biography, photograph and professional profiles will be added here only when they have been verified. Until then, treat Otepsphere as the responsible organisation rather than a fictional expert.