301 redirect basics
301 redirects are a powerful tool for ensuring that visitors to your site reach the content they need as quickly and easily as possible. Specifically, the Mozilla Developer Network web docs define a 301 redirect as follows:
The HyperText Transfer Protocol (HTTP) 301 Moved Permanently redirect status response code indicates that the requested resource has been definitively moved to the URL given by the [redirect’s] Location headers. A browser redirects to the new URL and search engines update their links to the resource.
Breaking this down a little, imagine that you have a page titled “Careers” hosted at https://example.com/careers/. However, you believe that your audience would react better to a page titled “Join Our Team,” and want to update the URL to https://example.com/join-our-team/ to better match the page’s title.
To follow through on your plan, you change the slug of your page from /careers/ to /join-our-team/ — but now what happens when someone tries to visit the old /careers/ page, either through the still-indexed page in their search engine of choice or through a backlink from another page?
By setting up a 301 redirect from the old /careers/ page to the new /join-our-team/ page, you can automatically forward any traffic that lands on the old page to the new one — ensuring a seamless experience for your visitors.
Search engines such as Google will carry any SEO value from the old page to the new page — meaning you won’t lose any keywords or rankings post-switch, and will also avoid having to wait for Google and other search engines to index your new page (i.e. it goes live and is displayed in search effectively immediately).
Why use 301 redirects for website refreshes and redesigns?
A screenshot of an example 301 redirect spreadsheet that we might make for a website redesign project. This sheet is formatted for RankMath’s import feature, and would be exported as a .csv file before being uploaded to the site.
When you redesign or otherwise make major adjustments to the URL structure or architecture of your website, you may need to change the URLs of various pages and posts. If you fail to set up the proper 301 redirects, search engines won’t know where to find the new pages, and your traffic will plummet.
Further, as noted above, you will lose any SEO value generated by your prior pages, effectively lowering your website’s value in the eyes of search engines such as Google and all but ensuring the loss of any relevant keywords those pages ranked for.
For this reason, it’s generally a best practice to create a spreadsheet near the end of the website redesign process that details what pages you’ll be redirecting and where those redirects should point to. It’s not uncommon for these spreadsheets to range from around twenty rows to several hundred rows long, usually depending on if you’re changing the URL structure of your blog posts, projects, or other content marketing assets.
How to implement 301 redirects
A screenshot of the 301 redirects plugin, which we use to manage redirects on our main circle S studio website.
There are several ways of implementing 301 redirects on a website, ranging from slightly more technical processes like editing your site’s .htaccess file to more user-friendly solutions such as using a redirect plugin:
- Editing your .htaccess file — The most direct way to set up redirects is to add a new line to your website’s .htaccess file, which you can edit using SEO plugins such as Yoast or RankMath, or through other means. This solution is the most direct and common way for developers to set up redirects, but lacks the dedicated user interface found in other solutions, while also requiring a small amount of technical knowledge about website development.
- Using a plugin — In most cases, we recommend that our clients set up redirects using plugins, as this solution offers the greatest amount of flexibility while retaining the same speed and technical effectiveness of editing your .htaccess file. Common solutions include RankMath SEO’s redirects module, Yoast’s Redirect Manager, and WebFactory’s 301 Redirects plugin.
- Creating a rule at the hosting level — Sometimes in website redesign projects, you’ll want to move from one domain to another (such as an abbreviation of your business name or a custom top level domain or TLD such as .group or .design). Generally speaking, there are two methods of setting up redirects in this scenario. First, you would set up normal redirects on the old website using a plugin as noted above, sending all traffic from your old domain to the comparable page on the new one. This means that you’ll have to keep paying for hosting the site for the sole purpose of redirecting traffic to the new domain. Then, after leaving those redirects up for a year, it may be worthwhile removing the old domain entirely to save on hosting costs — at which point you can set up redirect rules at the domain level with whatever service manages your actual domain and DNS settings (such as GoDaddy or Google Domains).