Redirect Chains on Small Blogs: One Hop, Not a Maze
Redirect chains on small blogs: Collapse-Then-Hop. Point A straight at the keeper. Not a 404 page, not a broken-link hunt, not a domain move.

A redirect chain is extra doors in a hallway that already had an exit. The visitor asked for /old-post. They bounced through /old-post-2 before /real-post. You meant to be helpful. Crawlers just spent three requests.
This page is Collapse-Then-Hop. It is not 404 page UX. It is not broken links SEO. It is not move the blog to a new domain. Canonical vs 301 is hint versus one move—not hop counting.
Point every outdated URL straight at the final keeper. Delete the middle hops. One 301 beats a polite maze.
Official: Redirects and Google Search.
Table of contents
- Collapse-Then-Hop
- Where small blogs grow chains
- How to flatten without a crawl tool budget
- Who fires first: host, CDN, plugin
- Loops vs chains
- FAQ
- Flatten one slug today
Collapse-Then-Hop
COLLAPSE-THEN-HOP
List every 301/302 you own
Follow until the address bar stops
Rewrite first URL → final URL
Delete the middle rules
If B only exists to catch A, and B already goes to C, A should go to C. Keep B→C only if people still type B.
Where small blogs grow chains
- HTTP rule, then www rule, then trailing-slash rule (three plugins, three hops)
- Yoast/Rank Math redirect + host-level redirect + Cloudflare page rule
- Renamed slug twice:
/a→/b→/c - “Temporary” 302 left on for a year
SSL mixed content is padlock cleanup, not this hop map. Still: pick HTTPS once, then 301 HTTP directly to the final HTTPS URL.
How to flatten without a crawl tool budget
- Export redirects from your SEO plugin or host panel.
- For each “from,” open it until the bar stops. Note the final URL.
- Change the rule to from → final.
- Search the list for destinations that appear as sources. Those are middles.
- Update internal links to the keeper so you are not manufacturing new hops.
URL Inspection is for index status, not a chain linter. Your eyes on the address bar are enough for a 50-redirect site.
AdSense and reviewers also hate maze navigation. If you just got a not approved note about redirects, flatten before you resubmit.
Who fires first: host, CDN, plugin
Chains often come from three systems each doing one “helpful” hop:
- Host / nginx — HTTP→HTTPS or www
- CDN (Cloudflare page rules, Hostinger hcdn) — slash or geo
- SEO plugin — old slug → new slug
Pick one owner per problem. If HTTPS already happens at the host, delete the plugin’s HTTP rule. If the CDN already forces the trailing slash, do not also 301 slash variants in Rank Math.
Order matters: a plugin 301 to http://www… that the host then upgrades to HTTPS-apex is two extra hops you can delete. Flatten until the first response Location header is the keeper.
SSL mixed content still belongs on mixed-content pages. After HTTPS is clean, this hop audit is the leftover list.
Loops vs chains
A loop never lands. Fix it by naming one keeper and making every alias 301 there—never back.
A chain lands, slowly. Fix it by skipping the middle.
Both are configuration, not “Google being mean.”
FAQ
What is a redirect chain?
A chain is A → B → C when the visitor only needed A → C. Each extra hop costs time and can confuse crawlers. Google’s redirect documentation asks for clear, direct redirects to the final URL.
Is this the same as fixing broken links?
No. Broken-link SEO finds 404s and decides repair vs hospitality. This URL is hops among URLs that already redirect. 404 page UX is a third owner.
How do I find chains on a small WordPress site?
Paste old slugs into a browser and watch the address bar. A redirect checker or your host’s log helps. SEO plugins that list redirects often show “to” targets that are themselves redirected.
What about http to https to www to slash?
That is a classic four-hop mess. Collapse to one rule: one host, HTTPS, one slash policy, then 301 everything else straight there.
Is a chain the same as a redirect loop?
A loop is A → B → A (or a cycle). Browsers show “too many redirects.” Chains are a line; loops are a circle. Both need a single keeper URL.
Does this replace a domain migration?
No. New-domain moves need a site-wide map plus Search Console. This page is leftover hops on one host.
Should I 302 a chain “for now”?
Temporary 302s stacked on old 301s are how mazes grow. If the destination is permanent, use 301 from the first hop to the keeper.
Where is Google’s redirect help?
Redirects and Google Search. Canonical vs 301 (hint vs move) is a different CashPilot URL.
Flatten one slug today
Pick a renamed post. Type the oldest URL you remember. Count hops. Write one 301 to the live permalink. Remove the middle rule. That is the whole job.
Keep learning
More guides in the same topic lane.
WordPress Canonical URL Settings: Field, Then Self
WordPress canonical URL settings: Field-Then-Self in Yoast or Rank Math. Set the keeper URL; do not fight the plugin with a second tag. Not a canonical explainer.
WordPress Application Passwords: App Access Without Sharing wp-admin
WordPress application passwords: App-Then-Revoke. Give a plugin or REST client a token, not your real password. Not two-factor login, not a client password vault.
RSS Feeds for Small Blogs: The Subscribe Job a Sitemap Cannot Do
RSS feeds for small blogs: Feed-Then-Inbox. Let readers and tools subscribe. Not an email ESP, not an XML sitemap, not a newsletter monetization guide.