← Blog
SEO · November 13, 2026 · 9 min read

Changing a URL After Publishing: When It's Worth It, the 301 Redirect Done Right, and What Happens to Rankings for the Next Six Weeks

D
Changing a URL After Publishing: When It's Worth It, the 301 Redirect Done Right, and What Happens to Rankings for the Next Six Weeks

A URL is the one part of a page you set once and shouldn't touch, and every affiliate site ends up touching a few. The slug has a year in it and the post is evergreen. The slug says "lights" and the keyword is "bike lights". Two guides are being merged and one URL has to survive.

Those changes are worth making, and each costs a few weeks of rankings if done well and the page's history if done badly. The difference is a single redirect, a pass over the internal links, and the discipline not to change anything else at the same time.

This post covers the three reasons that justify changing a published URL and the five that don't, how to set the redirect in WordPress so it's one 301 and not a chain, updating internal links so nothing depends on the redirect, what the dip looks like and how long it lasts, the Search Console check two weeks in, and the mistakes that turn a slug change into a lost page.

The slugs post covers writing a slug right the first time, which is the way to avoid all of this.

The short answer

Change a URL only for a wrong keyword, a year on an evergreen post, or a merge. Set one 301 from old to new, update every internal link to point at the new URL directly, take the old URL out of the sitemap, and change nothing else for a month.

Expect a dip of two to six weeks. Check Search Console at two weeks for the old URL showing "Page with redirect" and the new one indexed. Keep the redirect forever.

Reasons that justify it

ReasonExampleWhy it's worth the dip
Wrong or missing keyword/best-lights/ for a bike lights guideThe slug is a ranking signal and the URL is shown in results; the right words earn back more than the weeks cost
A year in an evergreen slug/best-bike-lights-2024/The slug ages the page every January; the fix is once and permanent
A mergeTwo thin guides becoming oneOne URL has to carry the combined page; the other redirects to it. The pruning post covers choosing which survives

Reasons that don't

The redirect, done right

  1. Change the slug on the post. Note the old URL exactly, including the trailing slash.
  2. Confirm a 301 exists from old to new. Rank Math, SEOPress and Yoast Premium create one automatically when a slug changes; free Yoast doesn't, so add it in a redirects plugin or your host's redirect manager. Test the old URL in a private window: it should land on the new one with a 301 status (a browser extension or an online header checker shows it), in a single hop.
  3. No chains. If the old URL already redirected from an older one, point the oldest directly at the newest. Every hop loses a little and slows the crawl; Google follows up to ten, but two is already one too many.
  4. Not to the homepage, not to a category. A redirect to an unrelated page is treated as a soft 404 and passes nothing. Old URL to the page that replaces it, always.
  5. Keep it permanently. External links to the old URL exist and will keep existing; the redirect is what keeps them working.

Internal links

Every link on your own site to the old URL now goes through the redirect, which works but is slower and weaker than a direct link, and leaves the site depending on a rule in a plugin. Search the site for the old slug (the WordPress search won't do it; a crawler, a database search-and-replace plugin, or your SEO plugin's link report will) and change each link to the new URL.

Hubs, related-posts blocks and the guide's own in-text links are the usual places. The broken links post covers the quarterly crawl that catches the ones you missed; after a slug change, run it that week.

The dip, and the check

Google recrawls the old URL, sees the 301, crawls the new one and starts treating it as the same page; that takes days to begin and two to six weeks to settle.

During it the old URL drops out of results, the new one appears at a lower position, and clicks fall. Then they recover, usually to within a few percent of where they were, sometimes higher if the slug fix was the wrong-keyword kind.

At two weeks, open Search Console: URL Inspection on the old URL should say "Page with redirect"; on the new URL, "URL is on Google". The Page indexing report's "Page with redirect" count should have gone up by one. If the old URL still shows as indexed at four weeks, the redirect isn't being seen; check it returns a 301 and not a 302 or a JavaScript redirect.

The mistakes

Doing it with AffSERP

Guides written by AffSERP's X Best Review tool get a slug built from the target keyword with no year and no filler, which is the way to never need this post, and the Refresh option updates a guide in place on the same URL, so a refresh never changes the address.

If you do change a slug in WordPress, the plugin's redirect handles the move and the guide's internal links to other AffSERP posts are the ones to update; the tool doesn't rewrite them for you, and a quarterly crawl catches any that were missed.

FAQ

Does changing a URL hurt SEO?

Temporarily, if it's done right, and badly, if it isn't. A changed URL is a new page to Google until the redirect tells it otherwise; with a single 301 in place, most of the old URL's signals carry over within a few weeks, and the usual pattern is a small dip for two to six weeks and then recovery to roughly where it was. Without a redirect, or with a chain, or with the slug and the title and the content all changed at once, the page can lose its position and not get it back, because Google no longer has reason to treat it as the same page.

How do I change a permalink in WordPress without losing traffic?

Edit the slug on the post, and make sure a 301 redirect from the old URL to the new one exists and is a single hop. Most SEO plugins (Yoast Premium, Rank Math, SEOPress) create the redirect automatically when you change a slug; free Yoast doesn't, so you add it in a redirect plugin or your host's redirect manager. Then update every internal link that pointed at the old URL so nothing on the site depends on the redirect, resubmit the sitemap, and leave the title and content alone for a month so the only change Google sees is the address.

When should I change a blog post URL?

When the slug has the wrong keyword or no keyword, when it has a year in it on an evergreen post, or when you're merging two pages into one and the surviving URL should carry the combined topic. Those are the cases where the new URL earns more than the dip costs. Don't change one because it's long, because you'd phrase it differently now, because a plugin suggests it, because you changed the title, or because the post is new and hasn't ranked yet; none of those improve anything and each costs the page its history.

How long does a 301 redirect take to transfer rankings?

Google typically recrawls a changed page within days and processes the redirect over two to six weeks, during which the old URL drops out of the index and the new one takes its place. Rankings usually dip during that window and recover as the redirect is consolidated. Keep the redirect permanently; Google has said signals pass through a 301 and that there's no need to remove it, and removing it later breaks every external link to the old URL.

Slugs built right and never changed by a refresh

AffSERP builds each guide's slug from the keyword with no year, and Refresh updates the guide in place on the same URL, so the address never has to move.

Start with free words
D
Written by Daniel R. SEO Lead, AffSERP

Daniel leads SEO at AffSERP. He writes about keyword research, search intent and site structure, favouring methods you can run with Google and Search Console before reaching for a paid tool.

More about Daniel →