301 Redirect SEO

A 301 redirect tells Google and users that a page has moved permanently to a new location. It's the standard way to preserve search visibility when you change a URL, restructure a site, or migrate a domain. The key word is 'permanent' — you don't use a 301 for a temporary move like an A/B test or a seasonal landing page. That would be a 302 redirect, which tells Google the original URL will come back.

I see a lot of 301 redirects set up without thinking. Someone moves a page and blindly redirects everything to the homepage. That wastes the topical relevance of the old page. If you've built authority on a page about 'red widgets', redirecting it to a category page about 'widgets' passes some link equity, but the signal is diluted. The best practice is to redirect to the most specific equivalent page. If you can't find one, consider creating that page instead of dumping everything on the homepage.

Google's documentation states that a 301 redirect passes most of the link signals — anchor text, PageRank, and trust. But it's not a perfect transfer. I've seen sites lose 10–15% of organic traffic after a migration even with correct redirects. The drop is partly due to the time it takes Google to re-crawl and re-index the new URLs. That delay can be weeks. Using a [canonical tag](/canonical-tag/) alongside a 301 is redundant and can confuse Google; pick one or the other. A 301 is the stronger signal for a permanent move, so that's what I use for URL changes.

301 redirects matter most in three scenarios: domain migrations, site restructuring, and consolidating duplicate content. When you move from oldsite.com to newsite.com, every page needs a 301 from the old URL to the new equivalent. Google's guide on site moves is clear: map each URL individually, not just the root. I've audited migrations where a client redirected every blog post to the blog index page. That killed their organic traffic for months. You need to redirect example.com/blog/seo-tips to newsite.com/blog/seo-tips, not to newsite.com/blog.

Site restructuring matters too. If you change your URL structure from /p/123 to /product/red-widget, a 301 tells Google the new location is permanent. But only if the content is the same or equivalent. If you're merging two pages because they cover the same topic, a 301 to the surviving page is a clear signal to consolidate signals. That's better than using a canonical tag on a page that still exists but is deprecated. I've run [technical SEO audits](/technical-seo/) where I found 301 redirects pointing to URLs that themselves had a 301 — a chain. Google says to avoid redirect chains because they slow crawling and waste budget. I keep chains to a maximum of three hops, and ideally zero.

Another scenario is fixing broken links. If you have a page that's deleted and no equivalent exists, a 301 to a relevant category page is better than a 404. But don't 301 everything to the homepage. I prefer to redirect to the most closely related page, even if it's not perfect. You can also use a 410 Gone status for pages that are permanently removed with no good replacement. That's a cleaner signal for Google to remove the page from its index. The [website structure](/website-structure/) should be planned so that redirects are the exception, not the rule.

I used to believe a 301 redirect was a perfect transfer of all ranking signals. It's not. I've had pages that ranked #1, got redirected to a new URL with the same content, and never recovered the same position. Google's algorithm takes time to re-evaluate the new URL, and during that window, competitors can move in. The transfer is strong but not guaranteed. Now I treat a 301 as a way to preserve value, not to clone it.

I also used to set up 301 redirects for every URL change, even minor ones like adding a trailing slash or changing case. That's overkill. If the change is cosmetic and your server is consistent, Google will usually figure it out. I now use a [canonical URL](/canonical-url/) for those cases and only use 301 when the URL is genuinely changing permanently. Canonical tags are cheaper for the crawler and don't create redirect chains.

Another mistake was redirecting to the homepage instead of the most relevant page. I had a client who moved a product page, and I redirected it to the category page. The product had specific search intent; the category page was too broad. Conversions dropped by 20% because users landed on a page that didn't match their query. Now I map each old URL to its best new equivalent, even if it means creating a new page. That's more work, but it preserves the user experience and the topical authority. I also check for [duplicate content](/duplicate-content/) issues: if the old and new pages are nearly identical, a 301 is cleaner than leaving both live with a canonical tag.