To redirect a URL without losing rankings in 2026, map each old URL to its closest new equivalent, serve a server-side 301 or 308 from the old address, update internal links, canonicals and your sitemap, keep the redirect live for at least a year, and watch the move in Google Search Console. Google’s Search Central documentation says 301 and other permanent redirects “don’t cause a loss in PageRank,” and its site move guide says to keep redirects “for as long as possible, generally at least 1 year.” When rankings fall after a URL change, the usual cause is a skipped step, not the redirect itself.
Two more numbers matter. Google’s crawler documentation, last updated February 2026, says Googlebot “generally follows 10 redirect hops,” yet the same company’s site move guide tells you to redirect straight to the final URL and keep any chain “ideally no more than 3 and fewer than 5.” Google’s Change of Address tool in Search Console applies only to domain and subdomain moves, and Bing Webmaster Tools has its own Site Move tool. The redirect itself can live in Apache, Nginx, Cloudflare, the Redirection plugin for WordPress, or Shopify’s built-in URL redirects.
The stakes now include AI answers. Google’s AI features documentation says a page must be “indexed and eligible to be shown in Google Search with a snippet” to appear as a supporting link in AI Overviews or AI Mode. A redirect that breaks indexing for your new URL also removes it from Google’s AI features. We found no published redirect guidance from other AI search providers, so this post sticks to what Google and Bing document.
Changing URLs soon? Get a free scan of where your pages rank in Google and AI answers before and after the switch.
What is the step by step method Google documents?
Google’s site move guide reduces to five steps: build a URL map, serve permanent server-side redirects, update every internal reference, keep the redirects for a year or more, and monitor in Search Console. The same steps apply whether you move one page on WordPress or a whole domain.
1. Map every old URL to one new URL
List every URL that earns traffic or links, using your sitemaps, server logs, analytics and Search Console’s Links report, and include images and PDFs. Then pair each old URL with the single new page that answers the same intent. Google’s guide warns against sending many old URLs to “one irrelevant single URL destination, such as the home page,” which it says “might be treated as a soft 404 error.” Consolidating several pages into one new page that covers them all is fine.
2. Serve a server-side 301 or 308
Google’s “Redirects and Google Search” page says a permanent server-side redirect is “the best way to ensure that Google Search and people are directed to the correct page.” It lists methods in order of how reliably Google interprets them: HTTP 301 and 308 first, then an instant meta refresh, then JavaScript, then a plain “we moved” link. Use the fallbacks only when your platform blocks server access.
3. Update internal links, canonicals and the sitemap
A redirect is a patch, not a destination. Google’s site move guide says each new URL should carry a self-referencing rel=“canonical” tag, hreflang annotations should point to the new URLs, and internal links should change to the new addresses. If your canonicals still name the old URL, you are sending Google two conflicting signals; our guide to what a canonical tag does covers how to check them. Submit a sitemap that lists only the new URLs.
4. Keep redirects live for at least a year
Google’s guidance is “generally at least 1 year,” enough time to recrawl and reassign links from other sites. Ask the sites that link to you most to update their links, since every redirect adds latency.
5. Monitor in Search Console and Bing Webmaster Tools
Test redirects with the URL Inspection tool for single pages and a crawler for bulk checks. Then watch the Sitemaps report, where indexed counts for the old sitemap should fall as the new one rises, and the Page indexing report for spikes in “Not found” errors.
Which redirect type should you use: 301, 308, 302 or 307?
Use a 301 or 308 when the move is permanent and a 302 or 307 when the old URL is coming back. Google’s crawler documentation says it treats 308 as “equivalent to 301” and 307 as “equivalent to 302,” so the choice between each pair is about semantics, not rankings.
The table below combines Google’s “Redirects and Google Search” page with its HTTP status code documentation.
| Redirect type | Status code | Use when | Passes signals? |
|---|---|---|---|
| Permanent server-side | 301 (moved permanently) | The page has moved for good | Yes, Google calls it a “strong signal” that the target should be processed |
| Permanent server-side, method preserved | 308 (moved permanently) | Same as 301, and form POST requests must stay POST | Yes, Google treats it the same as 301 |
| Temporary server-side | 302 (found) or 307 | A page is offline briefly and will return | Weak signal; Google keeps showing the source URL in results |
| Instant meta refresh | 0 seconds | You cannot edit server config | Yes, Google reads it as permanent |
| Delayed meta refresh | More than 0 seconds | Rarely the right choice | Google reads it as temporary |
| JavaScript location | No status code | Server and meta options are both unavailable | Only if rendering succeeds; Google says it “might never see it” if rendering fails |
| Crypto redirect | A “we moved” link | Nothing else is possible | Unreliable; Google says not to rely on it |
Cloudflare’s documentation explains the practical difference: with a 301 or 302, a browser “might switch the HTTP method to GET,” while a 307 or 308 must preserve it. That matters for form endpoints and APIs, not ordinary pages.
Do 301 redirects lose PageRank or rankings?
No PageRank is lost, according to Google, but rankings can still wobble for weeks. Google’s site move guide says “301 and other permanent redirects don’t cause a loss in PageRank,” and also warns to “expect temporary fluctuation in site ranking during the move” while Googlebot recrawls.
For medium sized websites, Google says “it can take a few weeks or more” before it consistently shows the new URLs, and larger sites take longer. It may still show the old URL occasionally as an “alternate name,” which it calls normal.
Lasting losses usually trace to mistakes Google itself names:
- Irrelevant targets. Mass redirects to the home page risk soft 404 treatment. If no real replacement exists, a 404 or 410 is the honest answer; our guide on how to remove a page from Google covers that path.
- Chains. Each hop adds latency, and Google says “not all user agents and browsers support long redirect chains.”
- Leftover blocks. A noindex rule or robots.txt block from staging that ships to production hides the new URLs.
- Wrong destinations. Google says it “frequently” sees redirects pointing to URLs that do not exist on the new site.
- Stacked changes. Google’s Change of Address help says that combining a move with a redesign of content and URL structure will “probably” cost some traffic, because Google “might need to relearn and reassess the individual pages.”
How do you set up a 301 on Apache, Nginx, Cloudflare, WordPress or Shopify?
Every major platform supports a true 301. Apache uses .htaccess rules, Nginx uses a return directive, Cloudflare uses Single or Bulk Redirects, WordPress sites commonly use the Redirection plugin, and Shopify has a built-in redirect screen with limits.
Apache. Google’s documentation gives the simplest form using mod_alias, with mod_rewrite for patterns:
Redirect permanent "/old" "https://example.com/new"
RewriteRule "^/service$" "/about/service" [R=301]
Nginx. The official nginx rewrite module documentation says return can send a redirect URL for codes 301, 302, 303, 307 and 308:
location = /service {
return 301 https://example.com/about/service;
}
Cloudflare. Single Redirects default to “301 Permanent Redirect” and also offer 302, 307 and 308. Cloudflare’s documentation lists 10 Single Redirect rules on the Free plan, 25 on Pro, 50 on Business and 300 on Enterprise, with regex only on Business and above. Bulk Redirects handle 10,000 URLs across lists on Free and up to 1,000,000 on Enterprise. Both require your DNS records to be proxied through Cloudflare.
WordPress. The Redirection plugin by John Godley manages 301s from the dashboard, logs 404 errors, imports CSV, and can write rules to .htaccess or export them for Nginx.
Shopify. Go to Content, then Menus, then View URL redirects. Shopify’s help center notes three catches: you can redirect only from a URL that is already broken, fixed paths such as /products and /collections/all cannot be redirected, and stores get 100,000 redirects, or 20,000,000 on Shopify Plus. Shopify also warns that browsers cache 301s, so a removed redirect can keep firing for visitors who already hit it.
How long should you keep a 301 redirect in place?
Keep it at least one year, and longer if it still receives traffic or links. Google’s site move guide says “generally at least 1 year” and suggests keeping redirects indefinitely for users. For domain moves, Google’s Change of Address help sets a floor of 180 days.
The 180 day figure comes from Google’s Change of Address documentation: “Maintain the redirects for at least 180 days, longer if you still see any traffic to them from Google Search.” The same page recommends paying for the old domain for at least a year so nobody else can buy it and use it.
Keeping a redirect costs almost nothing: one line in .htaccess or one row in Shopify’s list protects every backlink and bookmark pointing at the old address.
When do you need Google’s Change of Address tool?
Only when you move from one domain or subdomain to another, such as example.com to example.net. Google’s Search Console help says not to use it for HTTP to HTTPS moves, www to non-www changes, or moving paths within one site. For those, redirects and an updated sitemap are enough.
Google sets several requirements for the tool:
- You must own both properties in Search Console, under the same Google account.
- It works only on domain level properties, not paths like example.com/shop/.
- It does not move subdomains, including www, so submit every variant of the old domain.
- You cannot chain moves: after moving A to B, you cannot immediately move B to C.
Bing Webmaster Tools works differently. Bing’s original help page for its Site Move tool says 301 redirects are “sufficient for Bing to understand” a move and the tool “can help expedite this process.” Unlike Google’s tool, it accepts domain, subdomain and directory moves.
Redirects protect the rankings you have already earned. Earning new mentions on the sites that Google and AI assistants trust is a separate job, and it is the work Subscribe PR’s services cover.
FAQ
Is a 308 redirect better than a 301 for SEO?
No. Google’s crawler documentation says it treats 308 as equivalent to 301, so rankings are unaffected by the choice. The difference is in how browsers handle form submissions: Cloudflare’s documentation notes that a 301 may let a browser switch a POST request to GET, while a 308 must preserve the original method. Use 301 for ordinary pages and 308 for form endpoints or APIs that have moved.
Should I redirect deleted pages to the homepage?
Usually not. Google’s site move guide says redirecting many old URLs to one irrelevant page, such as the home page, can confuse users and might be treated as a soft 404 error. Redirect a deleted page only when a close replacement exists, such as a newer version of the same guide or product. If nothing comparable exists, return a 404 or 410 status so Google drops the URL cleanly.
Can I remove a 301 redirect after a year?
You can, but there is rarely a reason to. Google’s guidance is to keep redirects for at least one year and to consider keeping them indefinitely for users who arrive from old links and bookmarks. Before removing one, check your server logs and Search Console for traffic to the old URL. Shopify also warns that browsers cache 301s, so a removed redirect may keep working for some visitors.
Does a redirect chain hurt SEO?
Short chains are followed, but they cost speed. Google’s crawler documentation says Googlebot generally follows up to 10 redirect hops, while its site move guide advises redirecting straight to the final URL and keeping any chain ideally no more than 3 and fewer than 5. Fix chains by updating each old rule to point directly at the current destination, and update internal links so no visitor hits a redirect.
Do I need a new sitemap after redirecting URLs?
Yes. Google’s site move guide says to submit a sitemap containing only the new URLs, and notes that you can then remove the old one. Search Console’s Sitemaps report lets you watch indexed counts shift from old URLs to new ones. Google says warnings about redirecting URLs in the old sitemap are normal during a move and can be ignored, since you are moving those URLs on purpose.
Is a canonical tag a substitute for a 301 redirect?
Not when the old page should disappear. A 301 sends people and crawlers to the new URL, and Google treats it as a strong canonical signal. A canonical tag leaves both pages live and is only a hint that Google can override. Use a 301 when the old URL has moved for good, and a canonical when two versions must stay reachable, such as filtered product listings.
The short answer
A redirect does not cost you rankings; a sloppy one does. Google says permanent redirects lose no PageRank, so the work is in the details around them: one old URL to one relevant new URL, a server-side 301 or 308 with no chains, canonicals and internal links and the sitemap all pointing at the new address, and redirects left alone for a year or more. Use Change of Address only for a domain move, report the move in Bing Webmaster Tools, and give Google a few weeks before you judge the result.
Before you flip the switch, see where each page stands today. Request a free scan of your Google and AI answer visibility, then compare it after the move.
Tagged