What is the highest-value redirect fix?
Flattening chains. A redirect pointing at another redirect costs a full request round trip per hop, loses a little each time, and long chains may not be followed at all. Point every original URL directly at the final destination, and fix the protocol and trailing-slash rules first.
Get the full list into one place
Redirects hide in several layers, and a cleanup that only looks at one of them misses most of the problem:
- Server configuration —
.htaccess, nginxrewrite, or equivalent - Application-level routing
- A redirect plugin or CMS module
- CDN or edge rules
- DNS-level forwarding for alternate domains
- Meta refresh and JavaScript redirects in page templates
Export every layer to a single spreadsheet before touching anything. The overlaps between layers are usually where the worst problems are, because two layers can fight and produce loops.
Find the chains
A chain is a redirect to a redirect. Each hop loses a little and slows the response, and long chains can stop being followed altogether.
Test by following redirects and counting hops:
curl -sIL -o /dev/null -w '%{num_redirects} %{url_effective}\n' https://example.com/old-page
Anything above one hop should be flattened so the original URL points directly at the final destination. This is the single highest-value fix in most cleanups.
Find the loops
Loops usually come from two rules written years apart that each redirect to the other, or from a rule that fires on both the source and the destination pattern. They return an error to the visitor and are worth searching for explicitly.
Question every rule that is still there
For each redirect, ask three things:
Does the source still receive traffic? Check server logs and Search Console. A rule for a URL nothing has requested in three years can go.
Does the destination still exist? Redirects to pages that are now 404 are worse than no redirect.
Is the destination genuinely equivalent? Redirecting a discontinued service page to the homepage is a soft 404 in practice, and unhelpful to the person who clicked.
What to keep indefinitely
Keep redirects that carry real value:
- Rules from a domain change or migration
- URLs with external links pointing at them
- Anything still appearing in Search Console reporting
- Printed or offline URLs — vehicle wraps, signage, ads
That last category matters more in a trade-heavy market like Houston than people expect. A URL printed on a truck stays in circulation for years after the site changes.
Order and specificity
Most systems evaluate rules in order and stop at the first match. A broad pattern near the top can swallow everything below it. Put specific rules first, wildcards last, and test after reordering rather than assuming.
Deploy carefully
Make changes in a staging environment, run a crawl before and after, and compare the status of every known URL. Keep the old ruleset so it can be restored. Then watch 404 reporting for a month — a redirect removed in error shows up as traffic loss with a lag.
Frequently asked questions
Where do redirects hide?
Server config, application routing, CMS plugins, CDN or edge rules, DNS forwarding for alternate domains, and meta refresh or JavaScript in templates. Export all six layers before changing anything.
What is the highest-value fix?
Flattening chains. Every extra hop slows the response and loses a little, and long chains may stop being followed. Point each original URL directly at the final destination.
Which redirects should I keep permanently?
Anything from a domain migration, URLs with external links pointing at them, URLs still appearing in Search Console, and any URL printed offline — signage, vehicle wraps, ads stay in circulation for years.
Can I redirect a removed page to the homepage?
You can, but it functions as a soft 404 and is unhelpful to the person who clicked. Redirect to the closest genuinely equivalent page, or return 410 if nothing fits.
Why does rule order matter?
Most systems evaluate in order and stop at the first match, so a broad pattern near the top swallows everything below it. Put specific rules first and wildcards last, then test rather than assume.