Change any page's URL. Nothing breaks.
WordPress decides where your pages live. WPCentrify lets you decide instead, from one dashboard, across every site you manage. The old address keeps working automatically.
No plugin to install. Works on every site already connected to WPCentrify.
WordPress puts your page where it wants to
A service page nested under a parent lives at /services/emergency-plumbing/. Your client wants it at /emergency-plumbing/. WordPress has no setting for that. So it becomes a job: log into the site, install a plugin, change the slug, and remember to add a redirect, or every link anyone ever shared stops working and the ranking you built goes with it. Then do it again on the next site.
Slow
One address change is a login, a plugin and five minutes. Multiply that by every client you look after.
Risky
Forget the redirect and every existing link returns a 404. Nobody tells you, and the ranking quietly drains away.
Invisible
Nothing records what you changed or why, so a month later nobody can say what moved, or put it back.
How to change a page URL in WordPress
The short version, the way everyone does it by hand: set the structure in the Permalinks screen, change the one page in the editor, then add a redirect so the old address still works. Three jobs, and the last one is the one people forget.
Set the structure for the whole site
In WordPress, open Settings → Permalinks and choose a structure. Post name is the one to pick for SEO, so a page lives at /emergency-plumbing/ rather than /?p=42. Save. This sets the pattern for every URL on the site, and on its own it creates no redirects.
Change one page's address
Open the page or post, and edit the slug in the URL box in the editor. WordPress will forward an old post address to its new one on its own, but it does not do this for pages, for a moved parent, or for a structure change, which is where links start to break.
Add the redirect yourself
Install a redirect plugin such as Redirection, or add a rule by hand, so the old address returns a permanent 301 to the new one. Miss this step and every link anyone ever shared returns a 404, and the ranking the page built up drains away. Then repeat the whole thing on the next site.
That is a login, a plugin and a redirect you have to remember, on every site. The rest of this page is what happens when you do not have to.
Three steps. About ten seconds.
No login to the client site, no plugin to add, no separate redirect to remember.
Find the page
Open any website in WPCentrify and go to the Permalinks tab. Every page and post is listed with its current address. Search for the one you want.
Type the new address
Change /services/emergency-plumbing/ to /emergency-plumbing/ and save. We check the new address is free first, and warn you if something is already there.
The redirect happens by itself
The old address now points at the new one, permanently. Visitors, Google and every link ever shared all still arrive in the right place. You did not have to think about it.
Built for people who manage more than one site
Any address you like
Move a page anywhere. Out of a parent folder, into a new one, or to a completely different name.
Redirects on autopilot
Every move leaves a permanent 301 redirect behind. You never have to remember it, and you never add it by hand.
A list you can undo
Every redirect we created is listed in your dashboard against the page it belongs to. Remove one whenever you want.
Catches manual edits too
If your client edits a slug inside WordPress, we notice and add the redirect anyway. It does not matter which door the change came through.
Bulk changes, previewed first
Set a pattern for a whole post type, see exactly which pages would move and where, then approve it before anything happens.
No plugin to install
It is part of the connection you already have. Nothing new on the client's site to maintain or update.
We do not touch anything we do not have to
The audience for this has been burned by URL plugins before, so here is the quiet part out loud. This is a delivery layer over the connection you already have, not a rewrite of your client's WordPress.
It changes where an address points and records what it did. It does not edit your content, your slugs or your database to get there, which is exactly why undoing a change is clean.
Three promises
- Nothing is rewritten inside WordPress. Your page keeps its original slug and its original database record. Undoing a custom address puts everything back exactly as WordPress had it.
- You are warned before a clash. If another page already answers at the address you typed, we tell you what is in the way before anything changes.
- Bulk changes are a preview, not a leap. You see the full list of what would move and where, and you tick what you want. Pages that cannot move tell you why.
Questions about changing WordPress URLs
No. Every address change leaves a permanent 301 redirect behind automatically, so old links, bookmarks and search results all still land on the right page. That is the whole point: you move the page and the redirect is created in the same step, not as a thing you have to remember.
It protects it. When a URL changes without a redirect, the authority the page built up is lost and the ranking drops. The automatic 301 passes that authority to the new address, so the page keeps the position it earned instead of starting over.
No. If the site is already connected to WPCentrify, this works, because it rides the connector you already have rather than adding anything new to the client's site. Make sure the connector is on version 2.14.0 or newer, which updates from your dashboard.
Yes. Reset a page and it goes straight back to the address WordPress would give it, with its original slug and database record untouched. The redirects are listed separately, each against the page it belongs to, and you can remove them one at a time.
We notice and add the redirect anyway. It does not matter which door the change came through, whether you moved the address from the dashboard or your client edited the slug in the WordPress editor, the old URL still ends up pointing at the new one.
Yes. Set a pattern for a post type, preview every page it would affect and where each one would move to, then approve the ones you want. It is a preview you tick, not a change you hope worked, and pages that cannot be moved tell you why instead of failing silently.
The slug is the last, editable part of the address, the 'emergency-plumbing' in example.com/emergency-plumbing/. The permalink, or URL, is the whole address the visitor sees. Changing a slug changes part of the URL; WPCentrify lets you change the whole address, including moving a page out of a parent folder, and adds the redirect either way.
Post name, so a page reads as /emergency-plumbing/ rather than a date or an id. It is short, it describes the page, and it is what search engines and people both prefer. Changing to it on a live site is safe only if every old URL redirects to its new one, which is the step this feature handles for you.
Not on its own. Changing the site-wide structure in WordPress creates no redirects at all, and WordPress only forwards an old address automatically for individual posts, not pages, moved parents or structure changes. That gap is exactly where links break, and it is why every change made through WPCentrify leaves a 301 behind whether it was a slug, a move or a bulk pattern.
Open the site in WPCentrify, go to the Permalinks tab, find the page in the list of every page and post with its current address, type the new address and save. The change and its redirect apply to that site, and you can do the same on any other site you manage without logging into any of them.
Stop logging into WordPress to move a page
Change addresses across every site you manage, from one screen, with the redirects handled for you.
Free during early access. No credit card required.