How to Do a 301 Redirect Without Losing Your Rankings

A 301 redirect permanently sends visitors and search engines from an old URL to a new one. Here's how to do a 301 redirect: change a setting in your hosting panel, CMS, or .htaccess file to point the old URL at its replacement. Get the match right, and most of the old page's ranking value carries over.

Before you touch any settings, run the old URL through the free Redirect Checker. It shows you the current status code, whether a redirect is already in place, and how many hops it takes to reach the final page. That single check tells you whether you're starting from a clean slate or untangling a mess someone else left behind.

What a 301 Redirect Actually Does

When someone requests a page that's moved, their browser or a search engine's crawler gets an HTTP status code back from your server before any content loads. That code is a short signal describing what happened to the page. A 301 means "moved permanently", this address is retired, and everything should now point to the new one going forward.

This matters for two audiences at once. Visitors land on something useful instead of a dead page. Search engines update their index, swapping the old URL for the new one and carrying over most of the ranking signals the old page had earned. Skip the redirect entirely, and visitors hit a 404, while search engines eventually drop the old URL with nothing to replace it.

301 vs. 302 vs. 404: Which One Do You Need?

Status	Meaning	When to use it	Effect on rankings
301	Moved permanently	Page deleted, merged, or moved to a new URL for good	Passes most ranking signals to the new URL
302	Moved temporarily	A/B test, seasonal page, short-term maintenance	Search engines keep the original URL indexed
404	Not found	Content removed with no suitable replacement page	No ranking signal passed; a clean dead end

Picking the wrong one is a common slip. A 302 left in place for months tells search engines the move might not be permanent, so they hold off fully transferring value to the new page. If the old page genuinely has nothing to replace it, a 404 is the honest answer, don't force a redirect to an unrelated page just to avoid one.

When You Need a 301 Redirect

A 301 redirect earns its place any time an old address stops working but the content still matters. The usual triggers:

• Deleting or merging pages, combining two similar articles into one and sending both old URLs to the survivor.
• Changing a URL structure, cleaning up long, dynamic URLs into shorter, readable ones.
• Moving to a new domain, pointing every old-domain URL to its equivalent on the new domain.
• Switching from HTTP to HTTPS, a site-wide move that needs a 301 on every page.
• Site redesigns, when a rebuild changes folder structure or page names across the board.

If you're planning a redesign or a domain move, it helps to map your current URLs against your target keywords first, so nothing important gets redirected to the wrong page by accident. A fresh keyword research process before a migration makes that mapping far less error-prone.

How to Do a 301 Redirect on Your Own Site

The exact screen you'll use depends on how your site is built. Here's how to set up a 301 redirect on the three most common setups.

Using a .htaccess File (Apache Servers)

Most traditional hosting runs on Apache, which reads a plain text file called .htaccess sitting in your site's root folder. To do a 301 redirect this way:

1. Connect to your site's files through your host's file manager or an FTP client.
2. Open the .htaccess file in a plain-text editor (create one if it doesn't exist).
3. Add a line in this format: redirect 301 /old-page.html https://www.example.com/new-page
4. Save the file and reload the old URL in a browser to confirm it lands on the new page.

Each old URL needs its own line. If you're redirecting more than a handful of pages, a one-off .htaccess edit stops being practical fast, more on that below.

Using WordPress

If your site runs on WordPress, you don't need to touch code. Install a redirect plugin from the Plugins menu, then look for a screen where you can enter the old URL in one field and the destination URL in another. Save the rule, and the plugin handles the server response for you. Most of these plugins also log 404 errors, so you can see which broken links actually need a redirect before you create one.

Using a Website Builder or Host Control Panel

Platforms like Shopify, Wix, and Squarespace, along with hosting providers such as GoDaddy, offer a redirects section inside their own dashboard, separate from your page editor. The pattern is consistent across all of them: find the domain or URL management area, look for a redirects or forwarding option, and enter the old path and new path as a pair. Since exact menu wording changes between providers and updates over time, check your current dashboard for the redirects section rather than hunting for a specific label.

When Your Site's Own Tools Are Enough, and When They're Not

Here's the honest answer: it depends on scale and how often this comes up.

A single page that moved, or one old blog post you merged into a newer one, is a textbook case for doing it yourself. Open your CMS or .htaccess file, add one rule, confirm it works, and you're done. This is a five-minute job, not a project.

A full domain migration, a site rebuild that changes every URL, or an e-commerce catalog with hundreds of product pages is a different problem entirely. At that scale, a single missed redirect can mean a page quietly disappears from search results with nothing in its place. You need a full list of old URLs crossed against their new destinations, built before the change goes live, not patched together afterward from memory.

The recurring case is worth flagging too. If your team keeps running into broken links every time you publish or restructure content, that's not a one-off fix, it's a process gap. Teams without a dedicated SEO hire often underestimate how much ongoing redirect hygiene a growing site needs; a structured SEO plan built for a small marketing team usually bakes this into the routine instead of treating every migration as a fire drill.

Common 301 Redirect Mistakes

Most redirect problems come from one of a handful of repeat offenders.

Mistake	What happens	The fix
Redirecting everything to the homepage	Visitors land somewhere irrelevant; search engines see little topical match	Redirect each old page to its closest live equivalent, not a blanket homepage redirect
Redirect chains	Page A points to B, which points to C, each extra hop can dilute link value and slows the page	Update every old redirect to point straight at the final URL
Redirect loops	Page A points to B, which points back to A, trapping visitors	Trace the chain and fix the rule that loops back
Leaving a 302 in place long-term	Search engines treat the move as temporary and delay transferring ranking signals	Switch it to a 301 once the move is confirmed permanent
Forgetting internal links	Old URLs still get clicked from your own site's menus and posts	Update internal links to point directly at the new URL instead of relying on the redirect

Redirect chains in particular build up quietly. Every site rebuild or URL cleanup adds a new layer if old rules aren't flattened out, so it's worth reviewing your redirect list whenever you make structural changes, not just once after launch.

How to Verify Your 301 Redirect Worked

Once your redirect is live, don't assume it's correct just because the browser lands on the right page, some setups show the new content while still returning the wrong status code underneath, which search engines read differently than you do. Run the URL through the Redirect Checker again to confirm it returns a clean 301 with no extra hops in between. If you manage a lot of redirects, build a simple log of what points where, so the next person editing the site, or future you, isn't guessing.

This is also where tracking pays off. If a redirected page's traffic doesn't recover within a reasonable window, that's worth flagging in your regular SEO tracking rather than discovering it months later in a traffic report nobody read closely.

FAQs

How long does it take for a 301 redirect to work?

The redirect itself works instantly, the old URL starts forwarding visitors the moment it's saved. Search engines take longer to fully process the change, sometimes days to a few months, as they re-crawl the old URL and replace it with the new one in their index.

Does a 301 redirect hurt my SEO?

No, not when it's set up correctly. A 301 redirect is the standard way to preserve ranking value when a page moves, and it's generally considered safer for SEO than leaving a dead link or using a temporary 302.

What's the difference between a 301 redirect and a canonical tag?

A 301 redirect sends visitors and search engines to a different URL entirely, the old one stops serving its own content. A canonical tag keeps both URLs live but tells search engines which version to treat as the primary one for indexing, which is useful for near-duplicate pages rather than pages that are actually gone.

Can I do a 301 redirect without a plugin or code?

Yes, if your host or website builder has a built-in redirects section in its dashboard. That covers most GoDaddy, Shopify, Wix, and Squarespace sites without touching a line of code.

How many redirects are too many?

There's no fixed number, but each extra hop in a chain adds load time and a small amount of risk that link value doesn't fully transfer. The goal is always a direct path: old URL straight to the current one, with no intermediate stops.

Talk to the Team Before Your Next Migration

Knowing how to do a 301 redirect for one page is simple. Getting all of them right across a full site move, without losing the rankings those pages already earned, is where most teams need a second set of eyes, especially if you're also trying to explain the change to stakeholders who want a clear before-and-after. If you'd rather have your redirect mapping, traffic impact, and SEO plan reviewed before you flip the switch, talk to the team and walk through a sample report built around your own site.

Sources

• 301 Redirects For SEO: All You Need To Know | Hallam
• How to Set Up a 301 Permanent Redirect via .htaccess & ...
• A Guide to 301 Redirect Best Practices for SMBs
• How to Create a 301 Redirect for WordPress Pages and Blog ...
• What Is A 301 Redirect, And How Do You Implement ...