(Technical)

301 Redirect

Definition: what gets passed, and how

A 301 redirect is an HTTP response code that tells browsers and search engines a page has permanently moved to a different URL. The MDN web docs define 301 as indicating that “the requested resource has been permanently moved to the URL in the Location header,” and explain that “a search engine receiving this response will attribute links to the original URL to the redirected resource, passing the SEO ranking to the new URL.” MDN docs In other words, it is the official channel for passing the backlinks and ranking signals an old URL has built up to a new URL.

Google Search Central explains the same principle. When Google encounters a permanent redirect, it shows the new URL in search results, and the indexing pipeline uses the redirect as a signal that “the redirect target should be canonical.” Google classifies a 301 as a “strong” signal. Google (official)

Is link value lost? The official position vs. real migration results

Google has officially denied the common belief that “link value leaks through a 301.” In July 2016, Gary Illyes stated that “30x redirects don’t lose PageRank anymore,” and John Mueller added that this was not a new policy but confirmation of how things already worked. Google (Illyes) However, real-world migration results measured in the field tell a slightly different story.

Google’s official positionPageRank is not lost through 30x redirects, and a server-side 301 consolidates link and ranking signals onto the new URL (the redirect target). When implemented correctly, ranking transfer does not leak through the redirect mechanism itself. Google (official)
Expert measurement resultsEven with correct redirects, traffic recovers slowly in real migrations. SALT.agency analyzed 1,052 domain migrations and found that only 22.8% recovered their traffic within 90 days; the median recovery time was about 304 days (about 10 months), and 13.9% had not fully recovered even after 3 years (2026). SALT (data)

The two accounts seem to conflict, but they measure different things. Google’s “no loss” refers to the redirect mechanism in isolation, while the measured figures reflect the outcome of the whole migration: the time it takes Googlebot to recrawl thousands of backlink sources and reconsolidate signals, missing URL mappings, and reindexing delays, all combined. In practice, read it as “PageRank doesn’t leak, but recovery takes months,” and it’s safer to build at least two to three months of traffic fluctuation after the migration into your schedule and expectations.

301 vs. 302

The difference between the two codes is “permanent” versus “temporary.” Google’s redirect documentation clearly states that with a permanent redirect it shows the new URL in search results and treats the target URL as canonical, whereas a temporary (302) redirect keeps the original URL in search results and is not used as a canonicalization signal. Google (official)

Aspect301 (Moved Permanently)302 (Found / Temporary)
Shown in search resultsNew URL (redirect target)Old URL (original page)
Canonicalization signalStrong signal – new URL becomes canonicalWeak signal – original stays indexed
When to useRedesigns, domain migrations, HTTPS switchTemporary maintenance, short-term event pages

If the move is permanent, it’s safer to make that clear with a 301 from the start. If you need to keep both URLs live and only designate a preferred address, the right tool is a canonical tag, not a redirect.

Implementation: server-side redirects come first

Google’s redirect documentation lists implementation methods in order of preference: (1) server-side redirects (HTTP 301/308), (2) meta refresh, (3) JavaScript location, (4) a link with instructions. Because Google may not recognize a JavaScript redirect if rendering fails, the documentation insists you should “only use JavaScript redirects if you can’t do server-side or meta refresh redirects.” Google (official) Below is an implementation example at the web server (nginx) level.

# 1) Domain migration - 1:1 move preserving the path
server {
    listen 443 ssl;
    server_name old-domain.com www.old-domain.com;
    return 301 https://new-domain.com$request_uri;
}

# 2) Moving an individual URL
location = /old-page/ {
    return 301 /new-page/;
}

# 3) Path structure change - bulk move by pattern
rewrite ^/blog/(.+)$ /insights/$1 permanent;

The key is $request_uri in example 1. Without it, every page on the old domain gets lumped onto the new domain’s homepage. Google’s site move guide warns: “Avoid redirecting many old URLs to one irrelevant destination, such as the home page of the new site.” Google (official)

Site migration checklist, based on Google’s official guide

  1. Collect all old URLs and map them 1:1 – Google’s site move guide advises getting a list of old URLs first, then deciding where each one will redirect. Include variant URLs such as http/https, with or without www, and trailing slashes in the mapping. Google (official)
  2. Preserve paths – Send each page to its matching new page. John Mueller recommended returning a 404 or 410 when there is no equivalent page, rather than redirecting to the homepage. Google (Mueller)
  3. Minimize chains – Google says its crawler follows up to 10 redirect hops by default. Order your rules so that any starting address reaches the final URL in a single hop. Google (official)
  4. Update internal links and sitemaps – Change internal links on the new site to point to the new URLs instead of the old ones, and submit the new sitemap to Search Console.
  5. Verify after launch – Check status codes and the Location header with curl -I, and if the migration changes domains, submit the Change of Address tool in Search Console. You don’t need this tool for an HTTP-to-HTTPS switch. Google (official)
  6. Keep redirects for at least 1 year – Google advises keeping redirects “as long as possible, generally at least 1 year,” and, from a user experience perspective, considering keeping them indefinitely. Google (official)

Common mistakes

  • Redirecting every page to the homepage – John Mueller has said Google treats mass redirects without matching pages “mostly as soft 404s.” Link equity doesn’t carry over. Google (Mueller)
  • Leaving redirect chains in place – Google’s crawler follows up to 10 hops by default. The more hops, the more crawling waste and loading delay. Google (official)
  • Using a 302 for a permanent move – A 302 is a weak signal, so the original URL may stay in search results and the index may update more slowly. Google (official)
  • Substituting meta refresh or JavaScript redirects – These rank below server-side redirects in Google’s stated order of preference, and JavaScript redirects may not be recognized if rendering fails.
  • Setting up redirects but neglecting internal links – Google’s site move guide advises updating internal links and sitemaps to the new URLs as well. Google (official)

As the order of Google’s site move guide itself shows, redirect planning is not a finishing touch right before launch but preparation work that starts with URL mapping. The first step the official documentation recommends is building a mapping table as soon as the new URL structure is finalized.

References

Jul.2026By Studio JT

More from Technical

Like this term?
Give it a like!

(42)