2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Inventory affected URLs
Identify current paths from published content, navigation, sitemaps, and important incoming links. Separate one-page edits from site-wide structure changes.
Map valid destinations
Pair each old address with its corresponding replacement. Avoid treating the homepage as a universal destination for unrelated content.
Prepare supported routing
Use the site's documented redirect mechanism and test in an appropriate environment. Check status, destination, and unintended redirect chains.
Verify published signals
Review links, canonicals, sitemaps, and representative public URLs after the change. Monitor relevant indexing and not-found reports.
Worked scenario
See the plan in practice.
Changing a journal path affects article links in newsletters and old social posts. Include those addresses even if current navigation has been updated.
Review your result
Your acceptance checklist
Old URLs mapped- Redirects tested
- Public links checked
Use these checks to identify gaps in your permalink change map. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
- WordPress permalinkThe lasting URL structure WordPress uses for individual content and other public views.
- 301 redirectAn HTTP status indicating that a resource has moved permanently to another URL.
- Canonical URLThe preferred representative URL selected or indicated for a set of duplicate or closely similar pages.
Primary references
For the underlying concepts and current platform details:
