How to Change URLs Safely

A URL feels like a small, cosmetic detail, right up until you change one and watch a page's traffic fall off a cliff a week later. Site redesigns, CMS migrations, and simple cleanups like removing a date from a blog slug all involve renaming URLs, and every one of those changes carries the same risk if it's rushed.

The good news is that the risk is almost entirely avoidable. Search engines don't punish sites for changing URLs — they punish sites for changing URLs without telling anyone. A redirect is that notice, and getting it in place correctly is most of what "safely" means here.

Quick Answer

To change a URL safely, set up a 301 redirect from the old URL to the new one before the old page goes offline, update every internal link that pointed to it, and resubmit the new URL in your sitemap. Done together, these steps carry over most of the page's existing ranking signals and prevent the broken links that usually cause a traffic drop.

What does "changing a URL safely" mean?

It means making sure that every path pointing at the old address — search engines, internal links, external backlinks, bookmarks — gets redirected to the new one before, or at the same moment, the old URL stops working.

The practical takeaway: changing a URL isn't risky by nature. It's risky when the handoff between old and new is left incomplete or left too late.

Why this matters for your rankings

A mishandled URL change is one of the most common self-inflicted SEO problems, and it's entirely preventable:

📊 Quick stat Most of the traffic loss reported after a URL change traces back to a missing or delayed 301 redirect, not to the new URL itself — the address change is rarely the actual problem.

Step-by-step: changing a URL without losing traffic

  1. Decide on the final new URL before you touch anything. Settle on the exact new path first, since redirecting to a URL you'll rename again shortly after creates a redirect chain.
  2. Set up a 301 redirect from the old URL to the new one. Use your CMS's redirect settings, a plugin, or server configuration so the old address forwards visitors and crawlers straight to the new page.
  3. Publish the new page before removing the old one. The redirect only works if there's somewhere for it to point, so the new URL needs to be live first.
  4. Update every internal link that pointed to the old URL. Search your site's navigation, related-content sections, and body links for the old path and point them directly at the new one.
  5. Update your sitemap. Remove the old URL and add the new one so crawlers are directed to the right address without relying on the redirect alone.
  6. Test the redirect directly. Visit the old URL yourself and confirm it lands on the new page with a single hop, not a chain of multiple redirects.
  7. Leave the redirect in place indefinitely. Old backlinks, bookmarks, and cached search results can keep pointing at the old URL for years, so the redirect should stay live rather than being cleaned up later.
Try the Rebrixe Redirect Generator — free Enter the old and new URL, get a ready-to-use 301 redirect rule. No coding required.
Generate Redirect Rule →

Common mistakes that cause ranking drops

1. Using a 302 instead of a 301

A 302 tells search engines the move is temporary, so they keep the old URL indexed instead of transferring its signals to the new one — the wrong redirect type quietly undoes the whole point of redirecting.

2. Redirecting everything to the homepage

Sending every old URL to the homepage instead of its true new equivalent looks like a redirect on the surface, but search engines treat it as a soft 404 and it does nothing to preserve the original page's relevance or ranking signals.

3. Building a chain of redirects

Redirecting an old URL to a URL that itself redirects somewhere else adds delay for every visitor and dilutes the signal passed along at each hop — the old URL should point straight at the final destination.

4. Removing the redirect too soon

Deleting a redirect once traffic to the old URL seems to have dropped off reintroduces broken links for anyone still arriving through an old backlink, bookmark, or cached search result.

💡 Pro tip Keep a running list of every URL you've ever changed and where it redirects to, so a future migration doesn't accidentally break a redirect chain that's already several links deep.

Real-world examples

How different kinds of URL changes get handled safely in practice:

Blog cleanup
Removing a date from a slug
One 301 rule
Redirects /blog/2022/my-post to /blog/my-post and updates the internal link on the blog index page.
Ecommerce store
Renaming a product category
Bulk redirect map
Redirects every URL under the old category path to its matching URL under the new one, in a single mapped batch.
Site migration
Moving from HTTP to HTTPS
Sitewide 301s
Redirects every HTTP URL to its HTTPS equivalent and updates the sitemap to list only HTTPS addresses.
Content consolidation
Merging two similar pages
Redirect to survivor
Redirects the weaker page's URL to the stronger page's URL instead of leaving both live and competing.

In each case, the redirect went live before the old URL disappeared, and internal links were updated rather than left to rely on the redirect alone.

Redirect methods compared

A look at the main ways to redirect a changed URL, and where each one is the right — or wrong — choice.

Method SEO signal transfer Setup effort Best for
301 redirect Full, permanent Low, one rule per URL Any permanent URL change
302 redirect Minimal, treated as temporary Low Short-term A/B tests or maintenance pages only
Meta refresh Weak, not a true HTTP redirect Moderate Avoid for SEO-relevant page moves
Canonical tag alone Partial, a hint not a directive Low Duplicate content, not a full URL move

Generate your redirect rule right now — free

The Rebrixe Redirect Generator builds clean 301 redirect rules for the most common server and CMS setups. No account, no watermark, and nothing to configure by hand — just enter the old and new URL and copy the result.

Free Redirect Generator Enter the old and new URL, copy the redirect rule.
Open Redirect Generator →

Frequently asked questions

Not if it's redirected correctly. A proper 301 redirect from the old URL to the new one passes most of the page's accumulated ranking signals along, so a well-executed change usually causes only a brief, minor dip rather than a lasting drop.
A 301 tells search engines the move is permanent and transfers ranking signals to the new URL. A 302 signals a temporary move, so engines keep indexing the old URL and don't fully pass signals over, which makes it the wrong choice for a permanent URL change.
Yes. Redirects prevent broken links for visitors and crawlers, but leaving internal links pointed at the old URL adds an extra redirect hop on every click and dilutes the signal strength that would otherwise flow directly to the new URL.
Indefinitely, or as close to it as possible. Search engines and external sites can keep referencing the old URL for years, and removing the redirect later turns a handled change into a fresh batch of broken links and lost traffic.
On most CMS platforms, yes. WordPress, Shopify, Wix, and Webflow all have built-in redirect settings or plugins where the old and new paths can be entered directly, without touching server configuration files.
Leave the 301 redirect in place so those backlinks continue to pass value to the new URL. Reaching out to ask sites to update the link directly is worthwhile for high-value backlinks, but it isn't required for the redirect to work.
It still matters. An outdated sitemap keeps pointing crawlers at the old URL, which adds unnecessary redirect hops during crawling and can slow down how quickly the new URL gets fully indexed.

Generate your redirect rule in seconds

The Rebrixe Redirect Generator builds a clean, correct 301 redirect for the most common server and CMS setups — no account, no watermark, and nothing to code, just a ready-to-use rule.

Launch the Redirect Generator →
← Back to blogs