Redirects are a fundamental part of the digital web. Whether you’re migrating a whole website, or just a handful of pages, you need a way to communicate to search engines and browsers where the old content has moved to.
301 redirects are permanent redirects that not only point users to a new URL, but also pass “SEO juice” (search rankings, link value, page authority) from the old URL to the new.
If you’ve been wondering what a 301 redirect is, when it’s appropriate to use one, and how to set one up for your website, you’re not alone. In this beginner’s guide, we’ll run through the basics of setting up a 301 redirect.
What is a 301 Redirect?
A 301 redirect is a permanent redirect from one URL to another. When a browser or search engine crawler encounters a 301 redirect while crawling your site, the server returns an HTTP 301 status code, along with a response header that tells it where to find the new location.
The “301” status code comes from the HTTP protocol system. A 300 series status code indicates a redirection of some kind, with 301 specifically indicating a permanent redirect.
The important distinction between a 301 and other redirects (like a 302 or 307) is permanence. A 301 tells search engines to pass as much value (link value, PR, rankings) as possible to the new URL, and to update its index records to point to the new URL instead of the old one.
On the user experience side, there is no delay or interruption to the browsing experience. Modern browsers parse the redirect header from the server in milliseconds and load the new URL automatically. In most cases the user won’t even notice anything has changed.
301 redirects are implemented using a simple line of code in your server’s response header section. The syntax is “301 Moved Permanently” in the HTTP header, followed by the old path and new full URL as parameters.
When to Use a 301 Redirect
301 redirects are common on the web and are depended on by search engines and browsers to help keep track of all the moving parts. You’ll need to use a 301 redirect when you know that a URL has been permanently moved to a new location.
Website migration and maintenance activities
Moving to HTTPS
Changing domain names
Consolidating sites
Moving to a new platform
Permanent content removal
Content management reasons
Restructuring a site’s URL hierarchy
Removing duplicate or outdated content
Simply changing URLs to be more readable
Business moves, rebranding, or strategic changes
If your business acquired another company and wants to consolidate the websites, you’ll need to redirect the acquired site’s pages to relevant content on the main domain
301 redirects are the most widely used redirect type on the internet, and they get used in all sorts of scenarios. The key in all cases is the word “permanent.” If there’s any question the content may move again in the future, don’t use a 301.
How to Set Up a 301 Redirect
How to set up a 301 redirect depends on your website’s technical configuration. Popular hosting platforms and content management systems have specific methods for implementation. The most common approaches are below.
Server-level
.htaccess file: Enter redirect rules directly into .htaccess file in your root directory (common on Apache servers).
nginx configuration: Edit your server block configuration file and add redirect directives (nginx servers).
IIS (Windows servers): Use the URL Rewrite module or IIS Manager to configure redirects.
Server-side scripting: Write redirects in PHP, Python, Node.js, or other server-side languages.
Platform-specific
WordPress: Install a plugin like Redirection or Yoast SEO, or enter rules in .htaccess.
Shopify: Set up redirects using the built-in URL redirect feature in the admin dashboard.
Wix, Squarespace, Webflow: Use their native redirect managers in settings or site tools.
Custom CMS: Check your CMS documentation or development team for guidance.
For Apache-based websites, using the .htaccess method is most common. To implement a redirect, add a line like this to your .htaccess file: Redirect 301 /old-page.html https://www.example.com/new-page.html
To redirect an entire domain to a new domain, use this code instead: Redirect 301 / https://www.newdomain.com/
If you have a large number of redirects, you can use a spreadsheet to build a redirect map of old URLs to new destination URLs. This will help keep things organized and make it easier to audit redirects in the future.
301 Redirects and SEO
301 redirects pass value to the new URL as search engines crawl the site, including link value, page authority, and search rankings. Google’s official documentation even states that 301 redirects do not lose any “PageRank juice” during the transition period. They are often considered a strong signal of permanent movement of content, so search engines update their index records to point to the new URL after crawling the redirect. This typically takes days to weeks for a medium-sized website, and more time for larger sites.
If done correctly, you’ll maintain your search value and prevent losing rankings. Best practices include minimizing redirect chains (avoid A to B to C redirects), not removing redirects after a few months, making sure the content on the new URL is relevant to the old one, and monitoring search console data to confirm the transfer is complete.
While there can be some minor fluctuations in SEO value during the transition, a 301 redirect in and of itself does not harm SEO.
Common 301 Redirect Mistakes
Some common mistakes when implementing redirects include:
Technical errors
Redirect chains (A redirects to B, B redirects to C). Keep redirects short and direct where possible.
Redirect loops (URLs that redirect back and forth infinitely).
Misusing 301s for temporary changes. Use a temporary 302 or 307 for these.
Redirecting to unrelated pages.
Not redirecting both www and non-www versions of URLs.
Planning or strategy mistakes
Removing redirects too soon (try to maintain for at least a year, ideally keep redirects in place indefinitely).
Not creating a redirect map before starting migrations.
Not testing redirects before a site-wide change goes live.
Redirecting all old pages to the homepage instead of a relevant specific page.
Redirecting many old pages to a single destination page on the new site can appear manipulative to search engines and degrades the user experience.
Use this as an opportunity to assess content and think strategically about whether it still warrants the same real estate on your new domain.
How Long to Keep 301 Redirects?
Google states you should maintain redirects for “as long as possible, generally at least 1 year.” However, they also advise that you should keep redirects in place for longer (ideally indefinitely) from a user experience perspective.
SEO signals can take up to a year to fully transfer to the new URLs after Google first crawls the redirect. Redirects take longer to index than pages with content, so be patient and make sure to leave redirects in place.
Monitor your website after redirects have been implemented for a few months. Check the performance of redirected URLs to make sure they are still getting traffic and to see if any unexpected drop-off has occurred. Use analytics and Google Search Console data for analysis.
301 Redirects Checklist
Redirects are a critical part of any modern website. Use this checklist to make sure redirects are configured correctly.
When to use redirects
Move from HTTP to HTTPS
Change domain names during a rebrand
Consolidate multiple domains into one main domain
Move to a new platform, domain, or hosting provider
Migrate from one CMS to another
Permanently remove duplicate or outdated content
Restructure a site’s URL hierarchy
Merge multiple pages into one
Update URLs to be more readable or SEO-friendly
Fix historical URL mistakes or inconsistencies
Business or strategic moves (acquisitions, rebranding, etc.)
Migrate a site to a new platform or domain
Optimize your site’s URL structure for user experience
301 redirect best practices
Maintain redirects in place for at least one year, ideally indefinitely
Create a redirect map before starting any migration work
Test all redirects before launching site-wide changes
Redirect to relevant, content-appropriate URLs
Avoid redirect chains and loops
Use permanent 301 redirects for permanent moves only
Update all internal links to point to the new URL (preferred alternative to redirects)
Monitor redirects post-implementation in search console and analytics
Audit redirects regularly (use Screaming Frog or similar tools to crawl site and identify issues)
Table of content
Share
