How to Change a URL Without Losing SEO: A Step-by-Step Checklist

· 3 min read

The safest URL change is the one you don't make: a published URL is an address other sites, emails, bookmarks, and search indexes already depend on. But sometimes the change is right — the slug has a typo, the title pivoted, the year in the URL now screams "outdated". Done properly, a URL change preserves essentially all of your search equity. Here is properly.

First, decide it's worth it

A slug that's merely imperfect is not worth changing — the redirect tax outweighs the cosmetic gain. Change it when the URL is actively wrong: a misspelling, a keyword that no longer matches the content's intent, a date that makes evergreen content look stale, or a structural cleanup you're doing sitewide anyway. And if you're changing it, change it once — design the new slug to last forever. Draft it with the slug generator, keep it under 60 characters, and check it in the SERP preview before committing.

The change, in order

1. Publish the content at the new URL. The new page should be fully live — same content, updated internal metadata — before anything points at it.

2. Add a 301 redirect from old to new. Permanent, not temporary. One hop. If the old URL was itself a redirect target, update that earlier redirect to point directly at the new final URL — never let chains form.

3. Preserve the query string through the redirect. Campaign links tagged with utm_* will keep hitting the old URL from sent emails for years. If your redirect drops parameters, attribution dies silently.

4. Update every internal link. Redirects are for other people's links; your own site should link directly to the new URL. Search templates, navigation, related-post widgets, and — the one everyone forgets — previous blog posts that reference the page inline.

5. Update the canonical. The new page self-canonicalizes to its new URL. Make sure no stale canonical still whispers the old address.

6. Update the sitemap. The old URL leaves, the new one enters with a fresh lastmod. Resubmitting the sitemap in Search Console nudges recrawling.

7. Update off-site references you control. Social profiles, email footers, ad destinations, README files, documentation. Every link that skips the redirect is latency saved and risk removed.

What happens next (and when to worry)

Expect a days-to-few-weeks transition during which the old URL fades from results and the new one takes its place. Rankings commonly wobble slightly during the handoff, then settle at par. Monitor in Search Console:

  • Coverage: the old URL should move to "Page with redirect"; the new URL should be indexed.
  • Performance: compare clicks for the page (old + new combined) across the change. A sustained drop after 4–6 weeks means something in the checklist was skipped — the usual suspects are a 302 where a 301 belonged, a redirect chain, or internal links still pointing at the old address.

Bulk changes are a different animal

Renaming one page is a checklist; renaming a thousand is a migration, with its own failure modes — pattern-based redirect rules, collision detection, staged rollout. That scale gets its own guide: the bulk slug migration checklist, with the bulk slug generator doing the mechanical half.

The theme through all of it: search engines handle URL changes gracefully when every signal — redirect, canonical, sitemap, internal links — agrees about where the page lives now. Losses come from signals disagreeing.