You moved a page. Maybe you redesigned the site, renamed a URL to something cleaner, or merged two old articles into one. The new version is live and looks great. But somewhere out there, an old link still points at the address that used to exist. A visitor clicks it. Google crawls it. And what happens next, whether they land softly on the new page or hit a dead end, comes down to one small instruction you may never have set: a 301 redirect.
The 301 is one of the most quietly important tools in all of web maintenance. Get it right and you can move, rename, and reorganize your entire site without losing a visitor or a ranking. Get it wrong, or forget it entirely, and you bleed traffic, break links, and watch years of accumulated SEO value evaporate. This guide explains exactly what a 301 is, when to use it, and the mistakes that turn a simple redirect into a problem.
What is a 301 redirect?
A 301 redirect is a server instruction that tells browsers and search engines that a page has permanently moved to a new URL. The "301" is an HTTP status code, the same family of codes as the 404 you see on a missing page or the 200 a normal page returns. Specifically, 301 means "Moved Permanently."
When someone, or something, requests the old URL, the server responds with a 301 and the address of the new location. The browser then automatically forwards the visitor to the new page, usually so fast they never notice. Search engines do the same, and crucially, they update their index to associate the new URL with the old one's history.
That last part is what makes the 301 special. It doesn't just move people. It moves SEO value. The ranking signals, the authority from backlinks, the accumulated trust that the old URL earned over time get passed along to the new one. A 301 is how you change a URL without starting from zero.
301 vs other redirects and status codes
The 301 is one of several codes that sound similar but behave very differently. Mixing them up is a common and costly mistake.
301 vs 302
A 302 means "Found," or more usefully, "moved temporarily." Use a 302 when the move is genuinely short-term: a page under maintenance, a seasonal promotion, an A/B test. Because the move is temporary, search engines generally keep the original URL in their index and don't fully transfer ranking signals to the destination.
The mistake people make is using a 302 for a permanent move. If you've genuinely moved a page for good but use a 302, Google may keep the old URL indexed and hesitate to pass full value to the new one. For a permanent change, you want a 301.
301 vs 308
A 308 is also a permanent redirect, very similar to a 301. The main technical difference is that a 308 strictly preserves the original request method (for example, a POST stays a POST), whereas a 301 historically allowed it to change to a GET. For ordinary page moves on a content site, a 301 is the standard choice; 308 matters more in specific application contexts.
301 vs a canonical tag
A canonical tag is a hint that tells Google which of several similar URLs is the preferred one to index, but all the URLs stay accessible. A 301 actually moves the page so the old URL no longer serves content. Use a canonical when you need duplicate or variant URLs to remain reachable but want one indexed; use a 301 when the old URL should genuinely go away and forward to the new one.
When you should use a 301 redirect
The 301 is the right tool whenever a URL changes permanently and you want to keep the value and the visitors. Common situations:
- Changing a URL. Renaming a page, cleaning up a messy URL structure, or switching to a more descriptive slug.
- Deleting a page that had value. Rather than letting it 404, redirect it to the most relevant live page so you keep its traffic and link equity.
- Merging or consolidating content. Combining two thin articles into one strong one? Redirect both old URLs to the merged page.
- Migrating to HTTPS. Redirecting every
http://URL to itshttps://equivalent is done with 301s. - Changing domains. Moving to a new domain name relies on 301s to carry your rankings across.
- Fixing www vs non-www. Standardizing on one version and 301-redirecting the other prevents duplicate-content confusion.
How to set up a 301 redirect
How you implement a 301 depends on your platform:
- WordPress and most CMS platforms: a redirect plugin or built-in redirect manager lets you map old URLs to new ones without touching code. This is the easiest route for most people.
- Apache servers: redirects are typically added to the
.htaccessfile usingRedirectorRedirectMatchrules. - Nginx servers: redirects are configured in the server block with a
return 301directive. - Hosting platforms and CDNs: many (like Netlify, Cloudflare, or Vercel) offer their own redirect configuration files or dashboards.
Whatever the method, the principle is the same: tell the server that requests for the old URL should respond with a 301 pointing at the new URL.
The mistakes that turn a 301 into a problem
Redirecting everything to the homepage
This is the big one. When you remove a batch of pages, it's tempting to point them all at your homepage in one sweep. Don't. Google treats a redirect to an irrelevant page, especially a mass redirect to the homepage, as a soft 404, and you lose the value you were trying to preserve. Always redirect to the most relevant live page. If there genuinely isn't one, letting the page return a proper 404 or 410 is often better than a misleading redirect.
Redirect chains and loops
A redirect chain is when URL A redirects to B, which redirects to C, which redirects to D. Each hop slows the page down and dilutes the signals being passed along. A redirect loop is worse: A points to B and B points back to A, trapping the visitor and the crawler. Always redirect the old URL directly to the final destination, and audit periodically to collapse any chains that have formed over time.
Forgetting to update internal links
A 301 is a safety net, not a substitute for fixing your links. If your own internal links still point at the old URL, every visitor and crawler takes an unnecessary redirect hop. After setting up redirects, update the actual links in your content to point straight at the new URLs. Those stale internal links are a close cousin of broken links, and tracking them down is part of the same maintenance habit.
Leaving old links broken instead of redirecting
The flip side: deleting a valuable page and not redirecting it at all. The page 404s, any backlinks pointing to it are wasted, and the traffic disappears. If a page had any inbound links or traffic, a 301 to a relevant replacement reclaims that value.
How to check your 301s are working
After setting up redirects, verify them:
- Test the URL directly. Visit the old URL and confirm it lands on the right new page, not the homepage or an error.
- Check the status code. Use your browser's developer tools (the Network tab) or an online HTTP status checker to confirm the response is genuinely a 301 and not a 302 or a 200.
- Use Search Console's URL Inspection. Confirm Google sees the redirect and is processing it as expected.
- Watch for chains. Make sure the old URL goes straight to the final destination in a single hop.
Where Steterly fits in
Redirects are the kind of thing that quietly drift out of alignment. A 301 you set up last year still works, but the internal links pointing at the old URL never got updated. A page got deleted in a redesign and nobody set the redirect, so now it 404s. A redirect chain formed across three migrations and nobody noticed. None of these break loudly, they just slowly leak traffic and trust while everything looks fine on the surface.
Steterly is a whole-site quality scanner that crawls your site the way a search engine would and surfaces exactly this kind of quiet decay: broken links from pages that should have been redirected, missing or broken images, typos, outdated copyright years, leftover placeholder text, missing meta titles and descriptions, and Core Web Vitals issues. It follows redirect chains to the end and tells you which page each broken link lives on, so you can fix the cause instead of guessing.
You can start with a free scan of up to 50 pages, no credit card required. Create a free account, run a scan, and get a clear, prioritized report of what's broken or drifting, so your redirects actually do the job they were set up for.
Frequently asked questions
What is a 301 redirect in simple terms?
A 301 redirect is a server instruction that tells browsers and search engines a page has moved permanently to a new URL. Anyone who visits the old address is automatically forwarded to the new one, and search engines transfer the old page's ranking signals and authority to the new location, so you keep the value the original page built up.
What is the difference between a 301 and a 302 redirect?
A 301 signals a permanent move and passes ranking signals to the new URL, while a 302 signals a temporary move and generally keeps the original URL indexed. Use a 301 when a page has moved for good, and reserve a 302 for genuinely short-term situations like maintenance or a seasonal promotion.
Does a 301 redirect pass SEO value?
Yes. Passing along ranking signals and link authority is the main reason to use a 301 rather than simply deleting a page. The old URL's accumulated trust and backlink value transfer to the destination, which is why a 301 lets you change or move a URL without starting your rankings from scratch.
Can too many 301 redirects slow down my site?
Redirect chains, where one URL redirects to another that redirects again, do add delay and dilute the signals being passed. A single direct 301 has negligible impact, but chains and loops hurt both speed and SEO. Always point the old URL straight to its final destination in one hop and clean up any chains that form over time.
Should I redirect a deleted page to my homepage?
Generally no. Google often treats a redirect to an irrelevant page, especially a mass redirect to the homepage, as a soft 404 and discards the value you were trying to keep. Redirect to the most relevant live page instead, and if no relevant replacement exists, returning a proper 404 or 410 can be the better choice.
How do I check whether a 301 redirect is set up correctly?
Visit the old URL and confirm it lands on the correct new page, then use your browser's developer tools or an online HTTP status checker to verify the response is genuinely a 301 rather than a 302 or 200. Search Console's URL Inspection tool also confirms how Google is processing the redirect.