301 redirects: the complete SEO how-to

A 301 redirect is the single most important tool in technical SEO for preserving rankings when a URL changes. It sends a permanent signal that a page has moved, and according to Google Search Central it makes the destination URL the canonical one, transferring the old page's accumulated authority to the new location. Get it right and a migration is invisible to your traffic. Get it wrong, with chains, loops, or redirects to irrelevant pages, and you can quietly bleed rankings for months. This guide covers the decision between 301, 302, and canonical, what actually passes through a redirect, and how to remap URLs at scale without breaking anything.

What is a 301 redirect and how does it work?

A 301 is an HTTP status code that means "moved permanently." When a browser or crawler requests the old URL, the server responds with a 301 and a Location header pointing to the new address, and the request is forwarded there automatically.

For search engines the permanence is the whole point. Google keeps track of both the source and the target, then uses the permanent signal to pick the target as the canonical URL and to show it in results. The 308 status code carries the same permanent meaning, while 302, 303, and 307 are treated as temporary, per Google's redirects documentation. Server-side redirects, configured in your server or CDN, are the most reliable method. Meta refresh and JavaScript redirects work but are slower for crawlers to interpret and should be a fallback, not a default.

When should you use a 301 versus a 302?

Use a 301 when the move is permanent and you want the new URL to rank. Use a 302 only when the old URL must stay in the index because you will bring it back. A 302 keeps the source URL in search results and, as Google notes, means the engine "isn't influenced by the redirect," so ranking signals stay on the old page.

The most common mistake is using a 302 for a permanent change. Many CMS platforms and developers default to 302 without realizing it, which can stall the transfer of authority to the new page. Search Engine Journal is blunt on this: for permanent moves, a 301 is almost always the correct choice.

Do 301 redirects lose link equity or PageRank?

Officially, no. Google's Gary Illyes confirmed that 30x redirects, including 301, 302, and 307, no longer lose PageRank, a change reported by Search Engine Journal back in 2016. A redirect concentrates the signals from the old URL onto the chosen canonical.

The practical reality has conditions. Equity flows fully only for genuine 1:1 replacements. If you redirect a page to something topically unrelated, such as sending a deleted product to the homepage, Google can treat the redirect as a soft 404 and pass little or nothing. Redirect chains also erode reliability at each hop. So the honest summary is: a single, relevant 301 to a close equivalent passes signals cleanly, while chains and mismatched targets are where equity actually leaks. This is why redirect quality matters as much to your technical SEO as the redirect itself.

How long should you keep a 301 redirect in place?

At least a year, and ideally forever. Google's John Mueller advised keeping 301 redirects live for at least one year so search engines see the change enough times to record it as permanent, guidance covered by Search Engine Journal.

The deeper reason is external links. Any backlink pointing at the old URL becomes a broken link the moment you remove the redirect, so you lose both the referral traffic and the link equity it carried. If a redirect still receives visits or holds valuable links, there is no upside to removing it. Treat 301s as permanent infrastructure. The cost of leaving one in place is near zero, and the cost of removing it too early can be a page that quietly falls out of the index.

How many redirects can you chain before it hurts?

Keep chains to one hop wherever possible, and never more than two or three. A redirect chain is when URL A points to B, which points to C, forcing crawlers and users through multiple stops. Each extra hop slows the page for users and reduces the chance a crawler follows the whole path.

Redirect loops, where A points to B and B points back to A, are worse: they break the page entirely and return an error to users and bots alike. When you run a migration, always redirect straight to the final destination rather than layering new redirects on top of old ones. A quick way to catch this: after any URL change, crawl the site and flag every URL that resolves through more than one redirect, then rewrite those rules to point directly at the endpoint. Clean chains also protect your crawl budget, since Googlebot wastes fewer requests resolving hops.

• One hop: ideal, signals pass cleanly.
• Two to three hops: tolerable, but flatten when you can.
• Four or more: risky, crawlers may abandon the chain.
• Loops: always broken, fix immediately.

301 redirect versus canonical tag: which should you use?

Choose based on whether both URLs need to stay live. A 301 removes the old URL and forces everyone to the new one. A canonical tag keeps both URLs accessible but tells Google which version to index, making it a hint rather than a command.

Use a 301 when the old page should no longer exist, such as a renamed article or a consolidated category. Use a canonical when both pages must remain reachable, for example a product available under two category paths, or a printer-friendly version of an article. Getting this wrong causes duplicate content problems: a canonical where you needed a redirect leaves two competing URLs in the index, while a redirect where you needed a canonical can break legitimate user paths. As a rule, if a user should never land on the old URL again, redirect it; if they legitimately might, canonicalize it.

How do you set up 301 redirects at scale for a migration?

Build a complete URL map before you touch anything. A site migration lives or dies on a one-to-one mapping from every old URL to its closest new equivalent. Export your full URL list from a crawl, your XML sitemaps, and analytics, then match each entry to a destination.

The workflow that avoids surprises:

• Inventory every live URL, prioritizing pages with traffic and backlinks.
• Map each to its best 1:1 match, not a blanket redirect to the homepage.
• Implement server-side rules, using pattern matching (such as regex) for predictable path changes and exact rules for one-off pages.
• Test on staging by crawling the old URLs and confirming each returns a single 301 to the right target.
• Launch, then resubmit sitemaps and monitor the Page with redirect and coverage reports in Google Search Console.

For domain-level moves, Google's site move documentation recommends redirecting old URLs to their exact new equivalents and using the Change of Address tool where the whole domain moves. Moving to HTTPS is the same discipline: 301 every HTTP URL to its secure twin, a core step in HTTPS migration.

How do the AI engines handle 301 redirects?

The AI engines follow redirects much like traditional crawlers, but the citation layer adds a twist most redirect guides ignore. When ChatGPT, Perplexity, or Google's AI answers fetch a source, a clean 301 forwards them to the current URL, so your consolidated page keeps earning citations. The risk is fragmentation: if old URLs still appear in third-party content and resolve through chains or dead links, the AI engines may cite a stale or missing page instead of your live one.

Two practical implications. First, keep 301s permanent so historical links in articles and forums still resolve to your canonical page, protecting both search and AI visibility. Second, when you consolidate content, redirect to the single strongest version rather than splitting authority across near-duplicates, since AI systems reward one clear, self-contained source. This alignment between redirects and citability is the information-gain angle most 301 tutorials skip: they treat redirects purely as a blue-link concern, when they now also decide which URL the AI engines quote.

What are the most common 301 redirect mistakes?

Most redirect damage comes from a short list of avoidable errors. Watch for these:

• Redirecting everything to the homepage. Google can read this as a soft 404 and pass no equity. Map to relevant pages instead.
• Using 302 for permanent moves. The old URL keeps ranking and the new one struggles to take over.
• Leaving redirect chains after a migration. Old rules stacked on new ones create multi-hop paths that leak reliability.
• Redirecting then blocking in robots.txt. If crawlers cannot fetch the source, they never see the redirect.
• Forgetting internal links. Update your own links to point at the final URL rather than relying on the redirect, which is cleaner for users and your internal linking.
• Removing redirects too soon. Every external link to the old URL breaks the day you delete the rule.

After any large redirect change, recrawl the site and audit status codes as part of your regular technical SEO checks, so a broken rule surfaces in days rather than after a ranking drop.

Frequently asked questions

Related guides