Change URL WordPress: Keep Your SEO Intact
beginner guide, checked 11 Nov 2026Hi there, friend. To change a URL in WordPress without losing SEO, you set up a permanent redirect from the old address to the new one, update your links, and check it works. Here is the safe way, step by step.
- 301 redirects
- backup first
- tested before and after
| old URL | new URL | status |
|---|---|---|
| /2023/05/sourdough-class/ | /sourdough-class/ | 301 |
| /menu-page/ | /menu/ | 301 |
| /?p=214 | /wedding-cakes/ | 301 |
| /old-sale/ | / | bad |
| /news-2019/ | (none) | 404 |
// example data. Green rows are correct redirects. The last two are the mistakes this guide helps you avoid.
Can You Change a URL Without Losing SEO?
Yes, if the old address sends visitors and Google to the new one with a permanent redirect. Without that redirect, the old page’s links and rankings point at a dead end.
A URL is the web address of a page. When you change it, the old address stops working unless you tell the server where the page went. Visitors see an error, and Google sees a page that disappeared. A redirect is that message. A permanent one says “this page moved for good, use the new address.”
Google’s documentation says to use permanent redirects “when you’re sure that the redirect won’t be reverted.” With a permanent redirect, the new target is what shows in search results, and Google treats the target as the canonical, meaning the main version of the page. So the plan is not complicated. It just needs to be done carefully, with a list.
One honest warning first. WordPress’s own permalink screen says permalinks “should be permanent and never change.” The best URL change is the one you did not need. If your current address works and reads fine, leave it alone. Changing URLs for fun is how weekends disappear.
When Changing a URL Is Worth It
Change a URL when it is broken, misleading, or clearly harmful, such as a page address full of numbers or a wrong product name. Skip it for small cosmetic reasons.
Good reasons include a page that moved to a new topic, a messy structure like /?p=214, a typo in the slug, a rebrand, or a site move. For a full site move, read the website migration checklist, and consider my website migration SEO service if the site is large.
Bad reasons include “the new slug is two words shorter” or “someone said dates in URLs are bad.” Google’s starter guide says keywords in a URL have “hardly any effect” beyond breadcrumbs, so a tiny slug trim will not move rankings. It will, however, create risk. Weigh that.
The Safe Process, Start to Finish
Back up, list every URL, map old to new, change the address, add the redirect, test, and then monitor. Follow the order and nothing gets lost.
Google’s guide for site moves with URL changes uses nearly the same pattern: prepare the new URLs, prepare a mapping from old to new, start the move by redirecting, and monitor traffic on both. A single post is a small version of the same job.
The yellow dot in the flow shows where you are. Do not jump to step five because it feels fun. The first three steps are what protect you.
Back up
files and database
List URLs
every page you will touch
Map
old to new, one by one
Change
edit the slug or permalink
Redirect
permanent, server-side
Test
old URL lands on new URL
Monitor
Search Console, 4 weeks
// my order of work, based on Google’s site move guidance.
How to Change a URL in WordPress, Step by Step
Seven steps, in order. The first covers one page; the same steps repeat for many pages.
Step 1: Back Up the Site
Make a copy of your files and database through your host or a backup plugin. If a redirect rule goes wrong, a backup lets you roll back in minutes. Do this even for one page, because a mistake in a rules file can take down the whole site.
Step 2: List the URLs You Will Change
Write down each old address exactly as it appears in the browser. For one page, copy the address bar. For many pages, export your sitemap or crawl the site, and add pages that have links or traffic in Search Console. Do not trust memory. Old URLs hide in menus, emails, and social posts.
Step 3: Decide the New Address for Each
Match every old page to the closest new page, one to one. Google warns against redirecting many old URLs to an unrelated page, such as the new home page. A sourdough class page should go to the sourdough class, not to the home page. If there is no match, a 404 can be more honest than a wrong redirect.
Step 4: Change the Slug or the Permalink Structure
For one page, edit the post, open the permalink field, and change the slug, which is the last part of the address. For the whole site, open Settings, then Permalinks. WordPress lists options like Plain, Month and name, and Post name, and says you must click Save Changes for the new setting to take effect. If you change the whole structure, every old URL needs a redirect, so plan for that before you click.
Step 5: Add Permanent Redirects
Add a 301 redirect from each old address to its new one. You can do this with a redirect plugin, with your host’s tools, or with server rules. Google recommends permanent server-side redirects whenever possible, and says JavaScript redirects are a last resort, because rendering can fail and Google might never see the redirect. For the difference between types, read 301 vs 302 redirects.
Step 6: Test Every Redirect
Open each old address in a private window and confirm it lands on the new page. Then test with the URL Inspection tool in Search Console, which Google suggests for checking redirects. Make sure there is only one hop, since old to middle to new is a chain, which wastes crawling. Fix chains by pointing the old URL straight at the final one.
Step 7: Update Links, Sitemap, and Canonicals
Edit your own menus and internal links so they point to the new address instead of relying on the redirect. Check that the canonical tag on the new page names the new address, and that your sitemap lists the new URL. My guide to canonical tags explains why. Then request indexing of the new URL once, which Google says is a way to ask for a recrawl, and move on.
A Worked Example: Bakery in Portland
The example bakery moves three pages to cleaner addresses and drops one dead page. Each gets a mapped redirect, and the dead page gets an honest 404.
The bakery’s old posts live at addresses with the year and month baked in, such as /2023/05/sourdough-class/. The owner wants short addresses. She exports the sitemap, writes the three pages and their new slugs into a sheet, and checks Search Console to see that two of the three get clicks. Then she backs up the site, changes the slugs, adds the 301s, and tests each one.
She also finds an old sale page with no links, no traffic, and no replacement. Instead of sending it to the home page, she lets it return a 404. Everything here is example data, not a client result.
// example data, to show what to track. Not a client result and not a promise.
The Mistakes That Cost Rankings
The big three are changing the URL with no redirect, redirecting everything to the home page, and creating chains. Each has a quick fix.
No redirect at all. You changed the slug, and the old page now shows a 404 error. Fix: add a 301 from the old address to the new one today. Pages that already have links and visits are the first priority.
Everything goes to the home page. It feels tidy, but Google advises against redirecting many old URLs to an unrelated page. Fix: redirect each page to its closest match, and let truly dead pages return a 404.
Redirect chains. The old page goes to a second page, which goes to a third. Each hop slows visitors and wastes crawling. Fix: point every old address directly at the final URL.
Using a temporary redirect. A 302 tells Google the move is temporary, so the old address may stay in results. Fix: switch to 301 or 308 for permanent moves.
Removing the redirect after a few weeks. Google’s site move guide says to keep redirects “generally at least 1 year.” From a visitor’s view, keeping them indefinitely is fine. Fix: leave them in place, since they cost almost nothing.
Do This, Never That
Redirect one to one, test every address, and keep the rules in place. Avoid shortcuts that hide the problem.
Safe Habits
- Back up first
- Map old to new, one page at a time
- Use 301 or 308 for permanent moves
- Update your own internal links
- Keep redirects for at least a year
Risky Habits
- Change URLs without a redirect
- Send every old page to the home page
- Leave redirect chains in place
- Rely on JavaScript redirects first
- Change URLs just for cosmetic reasons
// based on Google’s redirect and site move documentation, plus my own habits.
How to Check the Change Worked
Test the redirects right away, then watch Search Console for a few weeks. Rankings may wobble before they settle.
Right away, open each old address and confirm it lands on the right new page. In Search Console, inspect the new URL and check it is indexed with the canonical you expect. Over the next weeks, compare clicks for the old and new addresses. Google’s site move guide says to expect temporary fluctuation, and that medium-sized sites can take a few weeks or more before new URLs show in place of old ones.
Google also says the old URL can stay visible as an “alternate name” for a while, which is normal and fades without action. So do not rush to fix what is simply slow. If after several weeks an old page still ranks and the redirect works, that is usually patience, not a bug. See how to track SEO results for a simple routine.
If you would rather not touch server rules, I do this as part of my plans. I am a cheap SEO company of one freelancer, so you talk to the person doing the redirects.
Questions About Changing URLs
Short answers first.
Will changing a URL hurt my rankings?
It can cause a temporary dip, but a correct permanent redirect usually protects most of the value. Google says rankings may fluctuate during a move and settle over time. I cannot promise your exact result.
Should I use a 301 or a 302 redirect?
Use a 301 (or 308) when the move is permanent. Google treats 302 and similar redirects as temporary, so the old address may stay in results. See my guide on 301 vs 302 redirects for examples.
How long should I keep the redirect?
Google’s site move guidance says generally at least one year. You can keep it indefinitely, which costs almost nothing and helps visitors with old bookmarks.
Does WordPress redirect old URLs automatically?
I cannot confirm that from official documentation, so do not rely on it. The Permalinks screen only says to save the setting for it to take effect. Add and test your own redirects.
Can I redirect everything to my home page?
You can, but you should not. Google advises against redirecting many old URLs to an unrelated page, such as the new home page. Send each page to its closest match.
Moving Pages? Let Me Check the Map.
Send me your old and new addresses on WhatsApp and I will tell you what I would fix before you switch anything on.
// one message, no form.
Sources and Last Check
- Google Search Central: Redirects and Google Search (permanent vs temporary, server-side first)
- Google Search Central: Site move with URL changes (mapping, one year, monitoring, fluctuation)
- WordPress.org: Settings Permalinks screen (structures, save to apply, permanent permalinks)
- Google Search Central: SEO Starter Guide (URL keywords have hardly any effect)
// last checked 11 Nov 2026. Example data is labelled. Opinions are marked as opinions.