301 redirect

A 301 redirect is a server response that sends people and search engines from an old URL to a new one for good. If you move /help/test-runs to /docs/test-runs, a 301 sends every visit and every link from the old address to the new page.
What is a 301 redirect?
A 301 redirect is the server's way of saying "this page has moved for good, go here instead." When a browser or Googlebot asks for the old URL, the server answers with the status code 301 and the new address, and the visitor lands on the new page without doing anything.
Let's say you sell test automation software and you rename your help center folder from /help/ to /docs/. Every link in old blog posts, every bookmark and every Google result still point to /help/. A 301 on each old URL sends all of them to the matching /docs/ page.
Google treats 301 and 308 as permanent moves. According to Google's guide to redirects, a permanent redirect makes Google show the new URL in search results, while a temporary one (302, 303 or 307) keeps the old URL showing.
Why 301 redirects matter for B2B SaaS
B2B SaaS sites change shape all the time. Products get renamed, pricing pages move, the blog moves from a subdomain to a folder and the whole site gets rebuilt every couple of years. Each change breaks URLs that buyers and search engines already know.
I used to work in the automation testing niche, where docs and integration pages pile up fast. When a page with good backlinks moves without a redirect, those links hit a 404 and the new page has to earn its ranking from scratch. A 301 tells Google the new URL is the same page in a new place.
Here's what's at stake when redirects go wrong:
- Rankings on money pages: Pricing, comparison and integration pages often rank for searches close to a demo. Losing them during a redesign hurts pipeline long before anyone spots it in a traffic report.
- Backlinks you already earned: Links from review sites, partner pages and old press coverage keep pointing at the old URL. A 301 keeps them working for you.
- Old links in your own product: Help articles linked inside your app, onboarding emails and sales decks all carry old URLs. Without redirects, customers and prospects land on an error page.
How to set up 301 redirects
Most redirects take one line in your server or CMS settings. Google's documentation gives examples like these, first for NGINX and then for Apache:
location = /service {
return 301 $scheme://example.com/about/service;
}
Redirect permanent "/old" "https://example.com/new"The code is the easy part. The planning is where most migrations go wrong. Here's my process:
- Export every old URL first: Pull URLs from your sitemap, your CMS, the Performance report in Search Console and a full site crawl in a tool like SEMRush. Include PDFs and old campaign landing pages.
- Map each URL to its closest match: Each old page should go to the new page that answers the same question. A retired feature page goes to the feature that replaced it, and an old pricing URL goes to the current pricing page.
- Send each URL straight to the final page: Google's site move guide advises against chained redirects and says to keep a chain to 3 hops or fewer if you really can't avoid one.
- Update your own links: Change internal links, navigation, your XML sitemap and your canonical tags to the new URLs. Redirects are a safety net for the links you can't edit yourself.
- Keep them in place: The same guide says to keep redirects for as long as possible, generally at least 1 year. I keep them for good on any URL with backlinks, because those links don't expire.
A 301 redirect example
Redirect chains are the most common redirect problem I find on older SaaS sites. They build up over years of small changes, one rebuild at a time. Here's a hypothetical chain on a site that was rebuilt twice and then moved to www:
Example: a redirect chain on a hypothetical SaaS site
- 1/pricing.html from the 2019 site
- 2/plans/ from the 2022 rebuild
- 3/pricing/ from the 2024 rebuild
- 4www.example.com/pricing/ after the move to www
Each hop slows the page down for visitors and gives Google one more step to follow. Google's crawlers follow up to 10 redirect hops by default, according to Google's documentation on HTTP status codes, but every extra hop is another place where something can break. The fix is to point all three old URLs straight at the final address, so each one takes a single hop.
How to check your redirects
You can test a redirect in a minute, and a full migration in an afternoon. Here's what I check after every move:
- Status codes: Crawl your list of old URLs with a tool like Screaming Frog or SEMRush's Site Audit. Each one should return a 301 and land on a page that returns a 200.
- Chains and loops: The same crawl flags URLs that hop more than once or loop back on themselves. Fix those at the source.
- Search Console: In Google Search Console, run URL Inspection on a few old URLs and watch the Page indexing report. Old URLs should show up under "Page with redirect" as Google recrawls them.
- Clicks on key pages: Compare clicks for your top pages before and after the move. Give Google a few weeks to process the change. If a key page is still down after that, check its redirect first.
Common 301 redirect mistakes
Most redirect problems come from habits that feel faster at launch and cost rankings later. Here's how they compare:
Redirect habits that keep or lose rankings
Do
- Send each old URL to the page that answers the same question
- Point every old URL straight at the final address
- Update internal links, sitemaps and canonicals to the new URLs
- Keep redirects in place for good on URLs with backlinks
Avoid
- Sending every retired page to the homepage
- Stacking a new redirect on top of an old one at each rebuild
- Using a 302 for a move you know is permanent
- Deleting the redirect file a few months after launch
The homepage habit is the one I see most. Google's guidance is to use a 301 when a page has moved or has a clear replacement. If a page has no real replacement, let it return a 404 and save your redirects for pages that moved.
Here's a quick check you can run today. Take the old URL of a page you moved in your last redesign and paste it into a redirect checker. Does it reach the right page in one hop?
Read more
FAQ
What is the difference between a 301 and a 302 redirect?
A 301 says the page moved for good, so Google shows the new URL in search results. A 302 says the move is temporary, so Google keeps showing the old URL. Google treats a 301 as a strong signal and a 302 as a weak one.
How long should you keep a 301 redirect?
Google's site move guide says to keep redirects for as long as possible, generally at least 1 year. I keep them for good on any old URL that has backlinks, because those links keep sending visitors.
How many redirects can Google follow in a chain?
Google's crawlers follow up to 10 redirect hops by default. Google still advises sending each old URL straight to the final page and keeping any chain you can't avoid to 3 hops or fewer.
Should I redirect deleted pages to the homepage?
Only when the homepage really replaces the old page. Google's guidance is to use a 301 when a page has moved or has a clear replacement. If nothing replaces it, let the URL return a 404.


