URL Redirects: Change a Page Without Losing Rankings

Posted October 28th, 2026 under Web development

Two colleagues reviewing a printed URL redirect plan before a website change

Google’s own crawler will follow a redirect chain for up to ten hops, but Google’s search documentation recommends keeping any chain under five — and that gap, more than any single technical mistake, is where small businesses get URL redirects wrong. A URL change sounds like simple housekeeping: rename a page, fix a slug, merge two old posts into one. Done without a plan, it can quietly erase years of accumulated search ranking in the time it takes to click publish.

Why changing a URL is riskier than it looks

Every backlink, every bookmark and every existing search listing points at the exact address being retired. Google’s own guidance on moving a site treats even a single URL change with real caution — a complete old-to-new mapping, testing before launch, monitoring after — because one mismatched redirect can send a page’s accumulated ranking nowhere useful. Not every page needs a new address, either: if a page is already drawing solid traffic, Google’s own advice is blunt — don’t change the URL just because a newer naming convention looks tidier. Save URL redirects for real reasons: merging duplicate content, fixing a URL that was broken from the start, or moving a page somewhere more logical in the site.

Set up URL redirects the right way

A 301 redirect tells Google and every browser the move is permanent. A 302 tells them it’s temporary, which means most of a page’s ranking value stays parked on the old URL instead of moving to the new one — that’s the core job URL redirects are supposed to do, and a 302 quietly fails at it. On a WordPress site, the fastest correct way to do this is with the Redirects module already built into All in One SEO: add the old slug, point it at the new one, and confirm the type reads “301 Moved Permanently” rather than letting a theme or caching plugin improvise something else. Skipping this single step is the most common reason URL redirects fail to protect a page’s ranking.

Two coworkers mapping old URLs before setting up URL redirects

Keep every redirect chain short

Googlebot will technically follow up to ten hops before giving up on a chain, but Google’s own documentation recommends staying well under that ceiling — three hops at most, five as a hard limit.

  • Point every old URL straight at its final destination. Update the redirect itself instead of letting it bounce through an earlier version that has since moved again.
  • Never redirect loosely to the homepage. A redirect should only point old content at a genuinely related new page — dumping unrelated URLs onto the homepage reads as a manipulation attempt, not a fix.
  • Return a real 404 or 410 for content that isn’t moving. A page that’s simply gone shouldn’t be redirected to something unrelated just to avoid showing an error.

How long does the ranking transfer actually take?

Patience matters here. Google’s documentation says a medium-sized site can take “a few weeks or more” for new URLs to fully replace the old ones in search results, and the move isn’t complete until Googlebot has recrawled every old and new URL at least once — there’s no fixed schedule for that to happen. Google’s Gary Illyes has said publicly that a redirect’s ranking signals consolidate permanently at the new address after roughly a year, measured from when Google first crawls the redirect, and independent testing by SEO analysts has broadly supported that figure without confirming it to the letter. The practical takeaway: keep a redirect live for at least a year, not just a few months, even once traffic looks like it has moved over.

Hand writing a redirect checklist before changing a page URL

What else has to change besides the redirect

The redirect itself is only step one.

  • Update internal links. Every menu item, button and in-page link still pointing at the old URL should be repointed directly — don’t lean on the redirect to carry internal traffic indefinitely.
  • Refresh the XML sitemap. Remove the old URL, add the new one, then resubmit the sitemap in Google Search Console.
  • Check canonical tags. A leftover canonical pointing at the old address can undercut the very redirect meant to replace it.

What this means for a multilingual Aruba site

A URL change on a site running English, Spanish, Dutch and Papiamento rarely happens on just one language version — and URL redirects have to cover every one of them, not only the version someone happened to be editing. Redirect the EN slug and quietly leave the ES or NL equivalent pointing at a dead page, and a chunk of a business’s visibility to Spanish- or Dutch-speaking customers disappears without anyone noticing until a client asks why bookings from Venezuela or the Netherlands dropped. See our earlier piece on multilingual sites done right for how EN/ES/NL/Papiamento pages should be structured in the first place, since that structure is exactly what a redirect plan needs to match.

A short checklist before any URL on the site changes:

  • 301, not 302. Set the correct redirect type before anything else goes live.
  • One hop, no chains. Point directly at the final URL, not at an earlier redirect.
  • Update internal links and the sitemap. Don’t rely on the redirect alone to carry traffic.
  • Leave the redirect live for at least a year. Ranking signals take time to fully consolidate.
  • Check every language version. A redirect plan isn’t finished until all of them are covered.

139 Design Studio builds and maintains WordPress and WooCommerce sites for Aruba businesses working across English, Spanish, Dutch and Papiamento, and that includes getting URL redirects right the first time — no lost rankings, no broken chains to track down later. Get in touch and we’ll map the redirects before anything on your site changes.

Sources: Google Search Central, “How to move a site” (developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes); Ahrefs, “Are Permanent Redirects Permanent?” by Patrick Stox (ahrefs.com/blog); EasyWP, “7 SEO Factors to Check Before Changing a URL Slug” (easywp.com).