Every page on the internet has a unique address called a URL — for example, yourwebsite.co.uk/services/plumbing. Google spends time and resources indexing these addresses and deciding how relevant they are for particular searches. When a URL changes and nothing is set up to handle the old address, Google simply encounters a 404 error (“page not found”) and has to decide what to do with the ranking it assigned to the old URL. Usually, that ranking is lost.
A 301 redirect solves this by acting as an automatic forwarding address. When someone — or Google — visits the old URL, the server instantly sends them to the new one. From the visitor’s perspective, nothing seems to have happened; they just arrive at the right page. From Google’s perspective, the signal is clear: the content has permanently moved, and the search ranking should be transferred to the new address.
Why the Number 301?
Web servers communicate with browsers using numbered codes that describe what happened to a request. You have probably seen a 404 error, which means “not found.” A 200 code means “everything is fine, here is the page.” The 300 range of codes all relate to redirects. A 301 specifically means “this page has moved permanently” — which is the signal that tells Google to transfer the ranking to the new URL. A 302 code, by contrast, means “this page has moved temporarily” — which tells Google to keep checking the old address, because it might come back. Using a 302 when you actually mean a permanent move is a common mistake that can leave your search rankings in an uncertain state for months.
When Do You Actually Need a 301 Redirect?
Not every website change requires redirects, but these situations always do:
- Moving to a new domain name. If your business rebrands and your website moves from oldname.co.uk to newname.co.uk, every page on the old domain should redirect to its equivalent on the new one. This is one of the highest-stakes scenarios — done properly, you can carry your Google rankings across to the new domain with relatively little loss; done badly, you may be starting from scratch.
- Redesigning your website. Website redesigns often involve reorganising pages and changing URL structures. A service that was at /services/painting might move to /painting-decorating after a redesign. Without a 301 redirect, anyone who had bookmarked the old address, or any other website that had linked to it, reaches a dead end.
- Changing a page’s URL for any reason. Even a small change — fixing a typo in a URL, simplifying a long address, removing the date from a blog post URL — creates a broken link if a redirect is not set up. Google treats the old and new URLs as completely different pages unless you tell it otherwise.
- Deleting a page that had any incoming links or ranking. If you remove a page that other websites linked to, or that ranked for any search terms, those links and rankings are wasted unless you redirect the old URL to the most relevant page on your site. Even redirecting to your homepage is better than leaving a 404 error.
- Consolidating duplicate pages. Some websites accidentally end up with multiple versions of the same content — for example, yourdomain.co.uk/contact and yourdomain.co.uk/contact-us both showing the same page. Google can be uncertain which version to rank. A 301 redirect from one to the other resolves this cleanly.
How Do You Set Up a 301 Redirect?
The method depends on how your website is built and hosted:
- WordPress. A plugin called Redirection (free) lets you add and manage 301 redirects through a simple settings panel — no code required. You enter the old URL and the new URL, save it, and the redirect is live immediately.
- Squarespace. Has a built-in URL redirects panel in settings. You can add as many redirects as you need through the interface without touching any code.
- Wix. Also has a built-in redirects manager under Marketing and SEO settings. The same principle applies: old URL, new URL, save.
- Custom-built or hand-coded websites. Redirects are typically set up in a configuration file on the web server, or through the hosting control panel. If your site is hosted on Apache servers, this is done in a file called .htaccess; on Nginx servers it is done in the server configuration. If you have a developer, this is a five-minute task for them. If you are managing hosting yourself, most hosting control panels (cPanel, Cloudflare, Netlify) have a redirects interface that does not require editing server files directly.
How to Check Whether Your Redirects Are Working
Once you have set up a redirect, it is worth verifying it is working correctly. The simplest method is to type the old URL into a browser and check that you end up at the new page. For a more precise check, a free tool called Redirect Checker (search for it — there are several good ones) will show you the exact status code being returned, confirming whether it is a 301 (permanent), 302 (temporary), or something else entirely. Google Search Console will also flag any crawl errors caused by 404s, so keeping an eye on that after a site change is a good habit.
Redirects are one of those behind-the-scenes details that most visitors never think about — because when they are done correctly, there is nothing to notice. But for small businesses that have built up any presence in Google over time, they are one of the most important things to get right when making changes to a website. The cost of not having them is invisible until it is not — and by then, the rankings may already be gone.