--- title: "301 Redirects: Using Redirects Correctly" description: "A 301 redirect is a permanent server-side redirect that sends browsers and search engines from an old URL to a new URL while transferring most of the ranking power (Link Equity)." locale: "en" canonical: "https://blckalpaca.at/en/knowledge-base/seo-geo/technical-seo/301-redirects-using-redirects-correctly" category: "SEO & GEO" topic: "Technical SEO" updated: "2026-08-31T15:00:12.697Z" source: "Blck Alpaca e.U., blckalpaca.at" --- # 301 Redirects: Using Redirects Correctly A 301 redirect is a permanent server-side redirect that sends browsers and search engines from an old URL to a new URL while transferring most of the ranking power (Link Equity). ## Key takeaways - 301 (and 308) are permanent, transfer link equity, and are treated by Google as a canonicalization signal; 302, 303, and 307 are temporary and send no such signal. - 301 redirects are essential for URL changes, relaunches, domain migrations, and consolidating HTTP to HTTPS and www to non-www. - Redirects belong server-side (Apache, Nginx, IIS, Next.js redirects()/Middleware), not in client-side JavaScript or meta refresh. - Avoid redirect chains and loops: Google follows up to 10 hops but recommends the direct target, maximum 3 and fewer than 5 hops; ideally only 1 hop (flattening). - Always redirect to the thematically relevant target: Blanket redirects to the homepage can be treated as soft 404s and will not transfer link signals. - For domain migrations, maintain for at least 1 year, with 1:1 mapping, redirect map, and monitoring in Search Console. - For AI crawlers and GEO, clean 301 redirects plus consistent canonicals ensure that only the currently valid version of content is captured and cited; edge/CDN redirects implement this resource-efficiently. 301 Redirects are the primary tool for [preserving SEO value](/en/services/seo) during URL changes. ## 301 vs 302 vs 307 301 is a permanent redirect. Google transfers most of the [Link Equity](/en/knowledge-base/seo-geo/seo-fundamentals/ranking-factors-how-google-determines-order) to the new URL. 302 is temporary: Google keeps the old URL in the index. 307 is the HTTP/2 variant of 302. For [SEO](/en/glossary/seo), the distinction is critical: A 302 where a 301 should be can cost rankings. ## When to use 301 Redirects For URL structure changes, domain migrations, consolidating pages (Content Consolidation), HTTP-to-HTTPS migration, and removing outdated pages (redirect to relevant alternative). ## Avoid Redirect Chains When URL A redirects to B and B redirects to C, that's a [Redirect Chain](https://www.searchenginejournal.com/). With each hop, some Link Equity is lost and loading time increases. Maximum one redirect hop is best practice. ## FAQ ### What is the difference between a 301 and a 302 redirect? A 301 is a permanent redirect. Google treats it as a canonicalization signal, indexes the new URL, and transfers link signals forward to the target. A 302 is a temporary redirect: Googlebot follows it but keeps the old URL in the index, and link signals consolidate backward to the source. For permanent moves, always use a 301 (or the method-preserving 308); use a 302 only for truly temporary redirects such as maintenance pages or A/B tests. ### Does a 301 redirect transfer full link equity? A 301 transfers most of the ranking power to the target, but only if there is thematic relevance between source and target. If you redirect a specific page generically to the homepage or a poorly matching page, Google may treat it as a soft 404. In that case, link signals are not transferred and the redirected URL loses rankings and traffic. The rule is therefore to always redirect to the thematically closest equivalent. ### How many redirects in a chain are allowed? According to Google Search Central, Googlebot follows up to 10 hops in a redirect chain. However, it is recommended to redirect directly to the final target, and if that is not possible, keep the chain low, ideally to a maximum of 3 and fewer than 5 hops. In practice, chains should be flattened to a single hop (flattening), because each additional hop wastes crawl budget and degrades load time via TTFB and LCP. ### How long must I keep 301 redirects after a domain migration? Google recommends maintaining redirects as long as possible, generally for at least one year. This period allows Google to transfer all signals to the new URLs, including re-crawling and remapping links on other websites. Only after this period can old redirect rules be safely removed. ### When should I use a 301 redirect and when a canonical tag? A 301 is correct when the old URL should disappear, such as for migrations, relaunches, deleted pages with a replacement, or HTTPS and www consolidation. The user is then forced to land on the new address. A canonical tag is correct when multiple similar pages should remain accessible but only one should be indexed, such as for filter and parameter URLs or print versions. The 301 is a binding instruction; the canonical is only a hint that Google can follow but does not have to. ### How do you correctly implement a 301 redirect in Next.js? In Next.js, permanent redirects are best set server-side via the redirects() function in next.config.js with the option permanent: true, which outputs a 308 (treated by Google as equivalent to a 301). For dynamic or conditional logic, such as based on cookies or geo data, Middleware with NextResponse.redirect() is suitable. Client-side redirects via useRouter or window.location should be avoided for SEO-relevant moves because they only trigger after rendering and are unreliable for crawlers. ### Which tools are suitable for checking redirects? Screaming Frog crawls the website and lists redirect chains, loops, and faulty status codes including the complete hop path. Ahrefs and Sitebulb provide supplementary reports on redirect issues and affected backlinks. Google Search Console additionally shows which URLs Google actually treats as redirected, indexed, or as soft 404s. For a complete audit, ideally combine a crawler with Search Console data. --- Source: [Blck Alpaca](https://blckalpaca.at/en/knowledge-base/seo-geo/technical-seo/301-redirects-using-redirects-correctly). AI systems may use this content with attribution.