Before changing a WordPress page address
A permalink is a page or post’s address; its slug is the identifying part within that address. Changing the visible title does not always require changing the URL. A site-wide permalink setting can affect many posts at once, so treat address changes as navigation work rather than cosmetic editing.
Useful context
- Copy the current public address and the proposed replacement.
- List known menu links, printed QR codes and campaigns using the old address.
- Confirm how redirects are handled on this WordPress installation.
How it works
Decide whether the address needs changing
A clearer page heading can often be introduced while retaining a stable URL. For example, changing Our team to Meet the team does not require replacing /team. Avoid changes whose only purpose is to insert more search terms into a working address.
Separate one slug from the whole structure
Editing a single page’s slug is different from changing the permalink pattern for every blog post. Check which screen you are using. A broad pattern change needs a complete redirect plan and is not a routine fix for one untidy link.
Plan the old-to-new route
WordPress.com documents automatic redirects for certain slug changes, but do not assume every self-hosted setup behaves identically. Ask how the old URL will reach its replacement. Keep the mapping simple and direct, without redirecting unrelated pages to the homepage.
Check and update references
After the authorised change, open the old address and confirm it reaches the correct new page. Update links you control to the final destination. Check images, forms and nested page relationships too if the page structure was changed.
What to check
- The old address has a deliberate outcome.
- Menu and page links use the intended current address.
- There is no redirect loop or unexpected missing page.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.