301 Redirect

A 301 is the web's permanent change-of-address. I use it when a URL dies, moves, or merges and I want Google to pass most of the old link equity to the new spot. In practice, a 301 sends both users and crawlers to the destination URL with a 301 status code. That status tells search engines "this move is permanent, consolidate your signals here". For example, when I moved a client's blog from /blog/ to /news/, a 301 preserved 95% of their organic traffic within two weeks. Without it, every old link would return a 404 and the [technical SEO](/technical-seo/) effort would feel wasted. The tradeoff: a single 301 passes nearly all link equity, but a chain of three redirects can leak 10–15% according to what I've seen in audits. So map your redirects carefully and keep them direct. Avoid the lazy homepage redirect. If you delete a product page, redirect to the closest category or similar product, not the homepage. That keeps the user's intent intact and [canonical URL](/canonical-url/) understanding precise. I've tested this: a homepage redirect from a deep page saw a 40% drop in conversion rate because users landed on a generic page and left. The 301 itself isn't harmful—Google says it doesn't penalise you—but how you chain and where you point it makes all the difference.

The decision to use a 301 matters most during any site move or restructuring. Think domain migration, HTTPS switch, URL rewrite, or merging duplicate pages. In each case, a 301 preserves the crawl path and signals that the destination should be treated as the canonical version. If you don't set one, search engines may index the old URL as a separate page or treat it as a [duplicate content](/duplicate-content/) issue. I once audited a client who had 1,200 products on new URLs but had used 302 redirects for three months. Google kept crawling the old URLs and the new ones never gained rankings. A 302 is explicitly temporary—Google does not transfer equity. So if you've permanently moved, a 301 is the only correct choice. Another scenario: [pagination](/pagination/). When you consolidate paginated content to a single page, a 301 from each paginated URL to the main page passes signals cleanly. But check you're not creating a loop. Use a tool like Screaming Frog or a server log analyser to verify. I also see teams misusing 301 for A/B testing or seasonal campaigns. Don't. Use 302 or 307 for temporary scenarios. The risk is that a misapplied 301 can lock you into a redirect that takes weeks to reverse in search results. So before deploying, ask: Is this URL truly dead forever? If yes, 301. If maybe, use a temporary code. This rule alone has saved me from undoing redirects later.

My first big mistake was redirecting every deleted page straight to the homepage. I thought it was safe—users end up somewhere, right? Wrong. I diluted my homepage's topical relevance and confused visitors who expected a product page. Google's crawlers also had no reason to treat the homepage as the canonical for hundreds of different products. The result: homepage ranking dropped for broad terms while the old product URLs sat in a redirect limbo. I fixed it by mapping each old URL to the most specific live alternative—an approach I now use in every [SEO audit](/seo-audits/). That brought bounce rates down by 25%. My second mistake was a redirect loop: A → B → A. I hadn't tested the chain and spent an hour in devtools tracing the response codes. Now I always test redirects with a header checker before going live. Third, I used a 301 for a temporary promotion. That promotion ended but the 301 stayed, directing users to a now-irrelevant page for weeks. I should have used a 302. Google treats 301s as permanent, so reversing it takes time and manual re-crawling. Lesson: always match the HTTP code to the duration of the move. I now document every redirect with its reason and expiration if relevant. That discipline prevents most of the errors I made early on.