How to Change a URL Slug Without Losing SEO
Renaming a URL slug can wipe out your rankings and backlinks if you do it wrong. Here's the safe, step-by-step way to change a slug and keep your SEO intact.
Sometimes a slug just has to change. Maybe it has a typo, a stale year, or a keyword you've since outgrown. The problem is that a URL is an address — and when you change an address without telling anyone, the mail stops arriving. Done carelessly, a slug change can erase rankings, break backlinks, and serve 404 errors to real visitors.
Here's how to change a slug safely, so you keep the SEO value you've already earned.
Why changing a slug is risky
Over time, a URL accumulates value:
- Backlinks from other sites point to that exact address.
- Rankings are tied to the URL in Google's index.
- Bookmarks and shares live in inboxes, docs, and social posts.
Change the slug and all of those suddenly point to a page that no longer exists. Google sees a 404, visitors hit a dead end, and the authority you built can leak away.
The golden rule: always add a 301 redirect
A 301 redirect is a permanent instruction that says "this page has moved here." It forwards both visitors and search engines from the old URL to the new one, and it passes nearly all of the old page's ranking signals along with it.
Whenever you change a slug, create a 301 redirect from the old slug to the new one. No exceptions.
Step-by-step: changing a slug the safe way
1. Decide whether the change is worth it
If the only benefit is a slightly nicer slug, it may not be worth the risk on a page that already ranks well. Reserve changes for slugs that are genuinely broken, misleading, or hurting clicks.
2. Generate the new slug
Create a clean, descriptive replacement. Paste your title into the URL slug generator to get a lowercase, hyphenated, keyword-focused slug in one click.
3. Publish the new URL
Update the slug in your CMS. The page now lives at the new address.
4. Add the 301 redirect
Point the old URL to the new one. How you do this depends on your stack:
- WordPress: a plugin like Redirection, or your SEO plugin's redirect manager.
- Nginx:
return 301 /new-slug;in your server block. - Netlify/Vercel: a rule in
_redirectsorvercel.json.
5. Update internal links
Find every place on your own site that links to the old slug and update it to point directly to the new one. Redirects work, but direct links are cleaner and faster.
6. Resubmit and monitor
Submit the new URL in Google Search Console and watch the Coverage and Performance reports for a couple of weeks to confirm the redirect is recognized and rankings transfer.
What not to do
- Don't change slugs in bulk for no reason. Each change is a small risk; multiply that across hundreds of URLs and you invite trouble.
- Don't use a 302 (temporary) redirect for a permanent move — it doesn't pass authority reliably.
- Don't delete the old page without a redirect. That's the fastest way to lose rankings and frustrate visitors.
A quick checklist
- New slug is clean, short, and descriptive
- 301 redirect from old → new is live
- Internal links updated
- New URL submitted in Search Console
- Rankings monitored for 2–4 weeks
The takeaway
Changing a slug isn't dangerous — changing it without a 301 redirect is. Generate a clean replacement, redirect the old address to the new one, update your internal links, and your rankings will follow you to the new URL.
Need the fundamentals first? Read what a URL slug is and the SEO slug best practices.