SEO Redirects
Setting Up 301 Redirects in WordPress Without Losing SEO Value
Every deleted or renamed URL that isn't redirected is a 404 error waiting to strand a visitor and quietly erode the ranking signal that page had built up.
301
Redirect status code that preserves SEO value
Daily
Backups before editing .htaccess directly
24/7
Human support if a redirect rule breaks the site
NVMe
Storage keeping redirect lookups fast at scale
In short
To set up a 301 redirect in WordPress, install a plugin such as Redirection, go to its settings, and add the old URL in the Source field and the new URL in the Target field, then save — the plugin handles the server-level redirect automatically. Alternatively, add a rule directly to the site's .htaccess file using the format 'Redirect 301 /old-url/ /new-url/' if editing server configuration directly is preferred.
A 301 tells search engines the move is permanent, which transfers most of the original page's accumulated ranking signal to the new URL — a 302 (temporary) redirect does not carry that same signal transfer.
Every time a URL changes on a WordPress site — a post slug gets edited for better SEO, a page gets renamed during a redesign, or an entire category structure gets reorganized — the old URL still exists somewhere: in search engine indexes, in other sites' backlinks, in a visitor's browser history, or in an old email campaign. Without a redirect, every one of those paths now leads to a 404 error, and search engines eventually treat that dead URL as one worth dropping from the index, taking whatever ranking value it had accumulated along with it.
A 301 redirect fixes this by telling browsers and search engines, unambiguously, that the content permanently moved to a new address, and most of the original URL's link equity follows it there. WordPress doesn't include redirect management natively, which is why a plugin like Redirection has become close to a default requirement for any site that changes URLs even occasionally, though editing .htaccess directly works too for anyone comfortable with server configuration. Hosting Cheap's daily backups mean a mistyped redirect rule in .htaccess — one of the few edits capable of taking a whole site offline if done wrong — can be undone in minutes rather than causing a prolonged outage.
Setting Up Redirects With a Plugin
Install the Redirection plugin from Plugins > Add New, activate it, then go to Tools > Redirection. In the Source URL field, enter the old path exactly as it appeared, such as /old-page/, and in the Target URL field, enter the new destination, such as /new-page/ or a full external URL if content moved off-site entirely. Save, and the redirect takes effect immediately without touching server files directly.
The plugin also logs 404 errors as they happen in a separate tab, which is genuinely useful for finding redirects that need creating without guessing — instead of manually tracking every URL change, the 404 log surfaces real visitor and crawler requests hitting dead URLs, which can then be redirected with a couple of clicks straight from that log.
Setting Up Redirects Directly in .htaccess
For a single redirect or a site owner comfortable editing server configuration, adding a line directly to .htaccess works without needing a plugin at all. The basic format is: Redirect 301 /old-url/ /new-url/ — placed above the existing WordPress rewrite rules block in the file, accessible through the cPanel-style file manager or an FTP client. For redirecting an entire folder of URLs to a new folder structure, RedirectMatch with a regular expression pattern handles bulk moves in a single line rather than one rule per URL.
Editing .htaccess directly carries more risk than using a plugin, since a syntax error in this file can return a server error across the entire site, not just the one redirected page. Downloading a copy of the current .htaccess file before editing, or confirming a recent backup exists, turns a possible mistake into a two-minute fix instead of a stressful troubleshooting session.
Avoiding Redirect Chains
A redirect chain happens when URL A redirects to URL B, which itself redirects to URL C — often the accidental result of renaming a page more than once over time without updating earlier redirect rules to point straight at the final destination. Each additional hop in a chain adds load time and, in some cases, dilutes the SEO signal being passed along, so the practical fix is to always redirect from the original URL straight to the current, final URL rather than stacking redirects on top of each other.
Periodically auditing existing redirects — most plugins including Redirection list every active rule in one place — catches chains before they build up. When a URL that's already a redirect target gets moved again, updating the original rule to point at the new final destination, rather than adding a second hop, keeps the chain length at exactly one redirect per changed URL.
Confirming Redirects Work Correctly
After adding any redirect, visit the old URL directly in a browser and confirm it lands on the intended new page rather than a 404 or an unrelated page. Checking the browser's network tab (or a dedicated redirect-checker tool) confirms the status code returned is actually 301 and not a 302, since some plugins or manual configurations default to a temporary redirect unless explicitly set otherwise.
For SEO purposes specifically, resubmitting the affected URLs through Google Search Console after setting up redirects speeds up how quickly search engines recognize the permanent move and update their index accordingly, rather than waiting for the next natural crawl to discover it.
A Stable Host Matters More Than It Seems for Redirects
Every redirect rule adds a lookup the server performs on each request to that URL, and a site with dozens or hundreds of accumulated redirects over the years needs that lookup to stay fast rather than adding noticeable delay. NVMe SSD storage with LiteSpeed keeps redirect-heavy .htaccess files and plugin-based rule tables resolving quickly even as the list grows.
Because .htaccess edits are one of the few changes capable of taking an entire site offline from a single typo, daily backups turn a redirect mistake into a quick restore rather than an emergency, and 24/7 human support is available if a rule needs troubleshooting beyond what's visible in the file itself.
- Daily backups before editing .htaccess redirect rules directly
- 24/7 human support if a redirect rule causes a server error
- NVMe SSD + LiteSpeed for fast redirect lookups even at scale
- Free managed migration that preserves existing redirect rules
Why Hosting Cheap
What you get
Daily backups
A quick restore point in case a redirect edit to .htaccess breaks the site.
24/7 human support
Real help troubleshooting a redirect rule or server error, any time it happens.
NVMe SSD + LiteSpeed
Keeps redirect lookups fast even on sites with a large accumulated rule set.
Free managed migration
Existing redirect rules move over intact when switching to a new host.
Free auto-renewing SSL
Redirected URLs continue resolving securely without a certificate mismatch.
30-day money-back guarantee
Test redirect and .htaccess performance risk-free before committing.
How It Works
Get set up in a few steps
Install a redirect plugin or open .htaccess
Use Redirection for a click-based setup, or edit .htaccess directly for full control.
Add the old URL as source and new URL as target
Set up a 301 rule pointing the changed or deleted URL to its correct new destination.
Test the redirect and check for chains
Visit the old URL to confirm it lands correctly, and audit for any multi-hop redirect chains.
Included
Everything you need, on every plan
- Redirect plugin installed, or .htaccess accessed through file manager or FTP
- Old URL entered exactly as it previously existed, including trailing slashes
- New destination URL confirmed correct before saving the rule
- Redirect tested by visiting the old URL directly in a browser
- Status code confirmed as 301, not a temporary 302
- Existing redirects audited for chains and consolidated to a single hop
- Backup confirmed available before editing .htaccess directly
- Redirected URLs resubmitted through Google Search Console if SEO-relevant
FAQ
Frequently asked questions
What's the difference between a 301 and a 302 redirect?
A 301 tells search engines the move is permanent and transfers most of the original page's ranking signal to the new URL. A 302 signals a temporary move and doesn't pass that signal the same way, so it shouldn't be used for a URL change meant to stick.
Do I need a plugin to set up redirects in WordPress?
No, a plugin like Redirection just makes it easier through a click-based interface. Redirects can also be added directly to the site's .htaccess file for anyone comfortable editing server configuration.
What is a redirect chain and why is it a problem?
A redirect chain happens when one URL redirects to another URL that itself redirects again, adding extra hops. Each additional hop adds load time and can dilute the SEO value passed along, so redirects should always point straight to the final destination.
Will a 301 redirect fully preserve my SEO rankings?
Most of the original page's ranking signal transfers to the new URL, though search engines can take some time to fully recognize and reflect the change. Resubmitting the URL through Google Search Console can speed up that recognition.
Can editing .htaccess break my WordPress site?
Yes, a syntax error in .htaccess can cause a server error across the entire site, not just the redirected page. Having a recent backup available before editing turns a mistake into a quick fix instead of prolonged downtime.
How do I find which old URLs actually need a redirect?
A plugin like Redirection logs 404 errors as they happen, showing real requests hitting dead URLs. That log is more reliable than manually guessing which old links need redirecting.
Keep Redirects Fast and Backed Up
WordPress hosting from $4.19/mo with daily backups before every .htaccess edit.
Get Started