Separate routine editing from a deliberate URL migration
A harmless-looking title, parent or permalink change can move a public route. URL Change Lockdown records the established route and rejects ordinary writes that would change it.
Protect the complete route
Lock post, page and taxonomy slugs, hierarchy and global permalink drivers across normal write paths.
Preview the impact
See the requested route change and affected descendants before authorizing migration.
Migrate with recovery
Require confirmation, create permanent redirects, verify the result and roll back on failure.
Choose it when the problem is this specific
- Published URLs must not drift during routine editing or automation.
- Page hierarchy or permalink settings need the same protection as slugs.
- A real route change needs an audited migration rather than a temporary bypass.
Know the boundary
The plugin protects public route identity. It does not lock links inside content or arbitrary post meta, and current releases do not use constant-based bypasses for ordinary changes.
Start with the smallest safe setup
- Install and activate the current release before further route edits.
- Audit existing canonical route contracts and resolve unexpected drift.
- For an intentional change, preview and confirm the dedicated migration, then verify its redirect.
Check requirements and ownership
- Administrative permission for route audits and confirmed migrations.
- Rank Math available when its redirect adapter is used.
- A backup and rollback plan for intentional public URL changes.
The release page is the authority for current package and compatibility details. The public source shows the behavior you are installing.
Make a public URL change an explicit migration
Keep routine writers safe, then move a route only with impact evidence and a verified redirect.