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 Google uses it as a strong signal that the new URL should become canonical, consolidating the old page's signals onto it (see Google's redirects documentation).
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:
location = /old-slug { return 301 /new-slug; }in your server block. - Apache:
Redirect 301 /old-slug /new-slugin.htaccess. - Next.js: a
redirects()entry innext.config.ts(permanent: trueissues a 308). - 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
Use URL Inspection in Google Search Console to request indexing of the new URL, then watch the Page indexing and Performance reports for a couple of weeks. The old URL should move to "Page with redirect" and its clicks should shift to the new one.
Changing many slugs at once
A site-wide slug clean-up or platform migration is the same process at scale, with a few extra safeguards:
- Export every current URL — from your CMS, your XML sitemap and Search Console's Performance report (so you include URLs that still get traffic but are no longer linked).
- Build a redirect map: a two-column spreadsheet of old URL → new URL. Generate the new slugs in one pass with the bulk slug generator, which also resolves duplicates.
- Map one-to-one, not everything-to-home. Redirecting hundreds of pages to the homepage is treated like a soft 404 and throws away their relevance.
- Test before launch by crawling the old URL list and confirming every one returns a single 301/308 to a 200 page.
- Keep the old sitemap briefly, so Google recrawls old URLs and discovers the redirects faster, then replace it with the new one.
We did exactly this when Slugme.io moved from Nuxt to Next.js and retired its /fr, /es and /ar locale prefixes: each old prefix now permanently redirects to the matching language page instead of returning a 404.
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. Google may eventually treat a long-lived 302 as permanent, but it sends the opposite signal and can keep the old URL in the index for longer.
- 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 (or a whole list of them with the bulk slug generator), 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.
Frequently asked questions
How long does it take Google to transfer rankings to a new URL?
For a single page, often days to a few weeks, depending on how frequently Google crawls it. Requesting indexing of the new URL in Search Console and updating internal links speeds it up.
Is a 308 redirect as good as a 301?
Yes. Google treats both 301 and 308 as permanent redirects that consolidate signals to the target. Frameworks like Next.js use 308 by default for permanent redirects.
How long should I keep the redirect in place?
As long as possible — ideally forever. Google recommends keeping redirects for at least a year, but external links and bookmarks keep arriving long after that, and a redirect costs almost nothing to maintain.
Do redirect chains hurt SEO?
Each extra hop adds latency and a chance of breaking. Google follows a limited number of hops, so point old URLs directly at the final destination rather than chaining /a → /b → /c.