A 301 redirect is a permanent server-side instruction that sends browsers and search engines from an old URL to a new one, passing the original page's ranking signals to the destination. It differs from a 302 redirect, which signals a temporary move and keeps the original URL in search results.
When you rename, merge, or migrate pages, the 301 decides whether the traffic and authority you built follow the content or vanish at the old address. Skip it and you strand rankings on dead URLs, break the links other sites and AI search engines point at, and hand competitors the visibility you earned.
The 301 in a 301 redirect is the HTTP status code a web server returns when a page has permanently moved, telling any client requesting the old URL to fetch the new one instead. This status code sits in the response header, so it works before the page loads, which is why crawlers and browsers honor it. Every 301 pairs one source URL with one destination URL.
Three parts make a 301 work: the old URL request, the 301 status code the server returns, and the Location header naming the destination. Search engines read this as a permanent instruction, drop the old URL from their index over time, and pass its ranking signals to the new URL. Google's Search Central documentation says a permanent redirect signals the target should become the canonical URL in search results.
A 301 differs from a canonical tag, which suggests a preferred URL without moving anyone, and from a 302, which keeps the old URL indexed. Use a 301 when the move is permanent. AirOps tracks whether the URLs an answer engine cites still resolve after a redirect, so migrations don't cost you citations.
A 301 runs at the server level every time someone or something requests a moved URL. The sequence below shows what happens from the first request to an updated search index.
Request sent. A browser, crawler, or AI search agent requests the old URL that no longer holds the content.
Status returned. The server answers with a 301 status code and a Location header naming the new URL.
Redirect followed. The client fetches the destination and loads that page, so the user never sees the old address.
Index updated. Search engines log the permanent move, drop the old URL, and pass its ranking signals to the destination.
Signals consolidated. Across repeated crawls, external links and citations resolve to the new URL and its authority consolidates there.
The status code tells you the move is permanent and where traffic should go. It does not tell you the destination deserves to rank; if that page is thin or off-topic, a clean 301 still won't hold the old page's position.
Every URL change is a decision about whether to keep the equity you paid to build. A 301 is how you protect rankings, referral traffic, and AI search citations when content moves, and how you consolidate duplicate pages competing with each other.
Preserved rankings and traffic: A correct 301 carries ranking signals to the new URL, so a migration or rebrand doesn't reset the organic visibility you spent years earning.
Broken redirects cost visibility: Redirect chains, loops, or a bulk redirect of every old page to the homepage create soft 404s, strand link equity, and drop pages out of the index. This is the failure mode that quietly erases traffic after a site migration.
Citations that survive URL changes: AI search engines cite specific URLs, and when those URLs 301 cleanly to live pages, your brand stays in the answer instead of resolving to a dead link.
SEO managers use 301 redirects to preserve rankings when they consolidate duplicate or outdated pages into a single authoritative URL.
Content strategists use 301 redirects to point retired blog posts to updated articles so readers and crawlers land on current content.
Growth marketers use 301 redirects to protect campaign traffic and referral links when they rebrand a domain or restructure a site.
The 3xx family of status codes (301, 302, 307, and 308) each signals a different kind of move, and choosing the wrong one tells search engines the opposite of what you intend, which is why a permanent move needs a 301 and a temporary one needs a 302 or 307.
Link equity is the ranking value that flows from linking pages through a redirect to a destination, and a 301 is the mechanism that carries that value forward so the new URL inherits the authority the old page earned.
A redirect chain is a sequence where one URL redirects to a second that redirects again before reaching the final page, and every extra hop slows crawlers, delays indexing, and weakens the signal that should reach the destination.
Preserve the ranking signals and backlinks pointing at a moved or retired page.
Send users to live content instead of 404 errors when URLs change.
Consolidate duplicate URLs into one page so they stop competing in Google search results.
Keep AI search citations valid by resolving old URLs to current live pages.
Speed up domain moves by pairing 301s with a Change of Address in Google Search Console.
Map each old URL to its closest matching new URL, because relevance-matched redirects hold rankings better than blanket redirects.
Redirect directly to the final destination, so you avoid chains that slow crawling and dilute signals.
Update internal links to point at the new URLs, since relying on redirects forever adds load and hides broken paths.
Keep redirects live long term, because search engines need repeated crawls to fully transfer the move.
Test status codes with a crawler before and after launch, so you catch stray 302s, loops, and 404s early.
Monitor indexing and referral traffic after the change, because that is where a bad redirect first shows up.
Avoid the common mistake of redirecting every retired URL to the homepage. Search engines treat an irrelevant bulk redirect as a soft 404, so those pages lose their equity instead of passing it on. Match each URL to a relevant destination, or serve a proper 404 when no equivalent exists.
AirOps: Monitors whether the URLs AI search engines cite still resolve after a redirect, so a migration doesn't quietly drop your citations.
Screaming Frog: Crawls your site to surface redirect chains, loops, and broken 301s before and after a launch.
Google Search Console: Reports indexing status and lets you submit a Change of Address so Google processes a domain move faster.
Audit your URLs. Export your live URLs and crawl the site with a free tool to list every page and its current status code. You can start this week with no budget approval.
Map old to new. For each URL you plan to change, choose the single most relevant destination and record the pair in a redirect map. Skip any page that has no equivalent, so you don't force an irrelevant match.
Implement the redirects. Add 301 rules on the server or in your content management system (CMS), pointing each old URL directly to its final destination with no intermediate hops.
Test before launch. Crawl the mapped URLs and confirm each returns a single 301 to the right target, with no chains, loops, or 404s.
Monitor after launch. Watch indexing and referral traffic for a few weeks, and fix any redirect that sends users or crawlers to the wrong page. Confirm your AI search citations still resolve to live URLs.
A 301 redirect permanently sends users and search engines from an old URL to a new one and passes its ranking signals.
You implement a 301 as a server rule that returns the 301 status code with a Location header naming the destination.
The main constraint is relevance, because a redirect holds equity only when the destination genuinely matches the old page.
The main risk is broken redirects, where chains, loops, or homepage dumps turn moved pages into soft 404s.
The leverage is in mapping and monitoring, since a clean, well-tracked map protects rankings, traffic, and AI search citations.
A 301 redirect signals a permanent move, while a 302 redirect signals a temporary one, and search engines treat them differently. With a 301, search engines drop the old URL, index the destination, and transfer ranking signals to it. With a 302, they usually keep the old URL indexed because they expect the original to return, so ranking signals stay put. Choosing the wrong code sends the opposite instruction: use a 302 for a permanent move and you can hold pages on a URL you meant to retire; use a 301 for a temporary test and you can lose the original URL you wanted to keep. As a working rule, reach for a 301 whenever the change is meant to last, and reserve a 302 for genuinely short-lived moves like a maintenance page or an A/B test.
Keep a permanent 301 redirect in place well beyond launch week and treat it as a long-term fixture. In 2021, Google's John Mueller said to keep a 301 in place for at least a year so the change is recognized as permanent and the destination fully inherits the old URL's signals. Search engines confirm a move across repeated crawls, and that process is not instant, so removing the redirect early can strand the equity you were trying to move. For a major migration, treat the redirect as effectively permanent: leave it running, keep the server rule documented, and only retire it once you are certain no traffic, backlinks, or citations still reach the old URL. If the old page still gets visits or external links after a year, keep the redirect live and leave removal for later.
A 301 sometimes fails to pass rankings because the destination isn't a strong match for the page it replaced. Search engines transfer signals fully only when the new URL covers the same intent as the old one; redirect a detailed product page to a generic category or the homepage and they often treat it as a soft 404, so the equity evaporates. Redirect chains cause the same problem, because each extra hop between the old and final URL slows crawling and weakens the signal that arrives. Timing matters too, since the transfer happens over multiple crawls instead of all at once, so a page can dip before it recovers. To diagnose a stalled transfer, check that each redirect is a single 301 to a genuinely relevant page, confirm the destination is indexable, and give search engines several weeks to reprocess the move.
You can influence how fast search engines process a 301, but you cannot set the exact speed. Google crawls and reprocesses URLs on its own schedule, so the move lands when your pages are next crawled and follows Google's timeline instead of yours. What you can control is everything that helps it happen sooner: point each old URL directly to its final destination, keep the destination fast and indexable, submit an updated sitemap, and use the Change of Address tool in Google Search Console for a domain move. Strong internal linking to the new URLs and healthy external links also pull crawlers through faster. Beyond that, the honest answer is patience, because a large migration can take weeks to settle. Watch indexing reports instead of refreshing rankings daily, and resist the urge to change the redirects again mid-process, which only resets the clock.
A healthy 301 redirect setup on a large site is one where every retired URL points, in a single hop, to a relevant live page that returns a 200 status. Good setups share a few measurable traits: no redirect chains or loops, no bulk redirects to the homepage, and no 301s landing on 404 or noindex pages. In a crawl, you want each mapped source URL to resolve to exactly one destination, with the share of chained or broken redirects at or near zero. On the traffic side, a healthy migration shows organic sessions and rankings recovering to previous levels within a few weeks, and AI search citations still resolving to working pages. If sessions stay depressed after a month, or crawlers keep reporting soft 404s, the map needs work and more time won't fix it.