Changing your permalink structure — how your URLs are formatted site-wide — changes every single page’s address at once, and doing this without a complete, tested redirect map is one of the most damaging technical mistakes a site can make, since it can instantly turn every indexed page into a 404 simultaneously.
Permalink structure change with redirect safety
A permalink structure change tested on staging first, with full redirect coverage before cutover.
- 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 your current and desired new permalink structure
- A staging environment, or agreement to have one created, for testing before the live change
- Your preferred timing for the actual cutover, ideally during lower-traffic hours
This or something else?
| You want to change your site’s permalink structure safely, with full redirect coverage | This fix covers it |
| You just want a few specific URL slugs cleaned up, not the whole site’s structure | Structured URL & slug standardisation, in the Technical SEO Implementation category |
| You’ve already made this change without proper redirects and now have widespread 404s | 404 mapping & redirect implementation, to recover from the situation |
| You’re changing your domain or moving to HTTPS, not the permalink pattern itself | Host-to-host migration, or HTTP to HTTPS full migration, in the Backups, Staging & Migration Ops category |
What we do
- Confirm your current and intended new permalink structure
- Test the change thoroughly on a staging copy first
- Generate a complete redirect map covering every existing URL under the old structure
- Implement the permalink change and redirect map together at the planned cutover time
- Verify a comprehensive sample of old URLs correctly redirect to their new equivalents
- Monitor Search Console following the change for any unexpected coverage issues
What is included
- A safely tested permalink structure change with complete redirect coverage
- Staging environment testing before the live change
- Verified redirect accuracy across a comprehensive sample
- Post-change monitoring for unexpected issues
Not included
- Individual slug cleanup without a full structural change, a separate, more contained fix
- Recovering from an already-executed, unprotected permalink change elsewhere — a different, remediation-focused fix
- Domain or protocol changes, separate, related fixes
- Ongoing monitoring beyond the immediate post-change period
Questions about this fix
How risky is this if done without proper precautions?
Very — changing permalink structure without a complete redirect map can turn every indexed page into a 404 simultaneously, which is why staging testing and a complete redirect map aren't optional steps here.
Will I lose my search rankings from this change?
Not if done correctly — a complete, accurate redirect map preserves most ranking signal by transferring it to the new URLs, though some temporary fluctuation during re-crawling and re-indexing is normal and expected.
Why do I need this instead of just changing the setting myself?
WordPress will apply the setting change instantly, but it does nothing to redirect the old URLs on its own — the redirect map is the part that actually protects you, and building it comprehensively and correctly is the bulk of this fix's actual work.
How long does the whole process typically take?
Testing on staging and building a comprehensive redirect map takes real time upfront, though the actual live cutover itself is planned to be quick, minimising the window where anything could be inconsistent.
What if I only want to change part of my URL structure, not everything?
That's worth clarifying upfront, since a partial change still needs the same careful redirect coverage for whatever's actually changing, even if the scope is narrower than a full site-wide restructure.
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.