Running more than one redirect plugin, or a plugin alongside manually configured server-level rules, creates redundant, sometimes conflicting layers of redirect logic that are harder to audit and more prone to unexpected behaviour — consolidating to one clear, well-organised source makes your redirects easier to manage and trust.
Redirect plugin migration & consolidation
Redirects scattered across plugins and server rules, consolidated into one clear source.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of every current source of redirects (plugins, server-level rules, CDN configuration)
- Your preference for which method should become the single, consolidated source going forward
- Access sufficient to review and migrate rules across the relevant systems
This or something else?
| You have redirects spread across multiple plugins or systems and want them consolidated | This fix covers it |
| You want an existing redirect map imported, not multiple existing sources consolidated | Bulk redirect import from supplied map |
| You have redirect chains or loops, not necessarily multiple management sources | Redirect chain & loop cleanup |
| You want a single new redirect set up, not a consolidation of existing ones | Single redirect setup |
What we do
- Inventory every current source of redirect rules across the site
- Confirm the intended single, consolidated destination method
- Migrate all existing rules to that single source accurately
- Verify no redirect is lost or altered incorrectly during migration
- Deactivate or remove redundant sources once migration is verified complete
- Test a representative sample of redirects following consolidation
What is included
- All existing redirect rules consolidated into a single, chosen source
- Verified accuracy with no redirects lost during migration
- Redundant sources deactivated once migration is confirmed complete
- Testing across a representative sample post-consolidation
Not included
- Fixing individually broken or incorrect redirects — a separate fix if issues are found beyond the consolidation itself
- Building a completely new redirect strategy from scratch
- Bulk import of a new mapping, a separate, related fix
- Ongoing redirect management as a standing service
Questions about this fix
Why would having multiple redirect sources actually cause problems?
Different systems can apply rules in an order that's hard to predict, potentially creating unexpected chains or one rule silently overriding another, which makes troubleshooting future redirect issues considerably more difficult than with a single, clear source.
Will I lose any of my existing redirects during this consolidation?
We verify accuracy specifically to prevent this, checking that every existing rule transfers correctly to the new single source before removing the redundant ones.
Which redirect method should I actually consolidate to?
It depends on your specific setup and needs — a plugin offers easier management for non-technical users, while server-level rules can be more performant; we can advise based on your situation if you don't already have a preference.
How do I know if I even have this problem?
If you've ever installed more than one redirect-related plugin, or have both a plugin and remember configuring server-level rules manually at some point, that's worth reviewing — we can also just check directly rather than you needing to remember your own history.
Will this cause any downtime while redirects are being migrated?
We verify each migrated rule before deactivating its original source, which minimises the risk of a gap — the process is managed carefully rather than switching everything over all at once.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.