How to Redirect URLs in WordPress Without Losing Traffic

WordPress redirect manager with 301 redirects from old URLs to new pages and 404 log

URLs change more often than people expect. You rename a page, merge two old posts, restructure categories, move to a new domain, or delete content that is no longer relevant. Every one of those changes breaks links from search results, social posts and other websites, unless you add a redirect.

A redirect tells browsers and search engines that a page has moved, and where to find it now. Done right, it keeps your visitors and most of your search ranking. This guide explains which redirect to use and how to add redirects in WordPress safely.

Types of Redirects

301 Moved Permanently: the page has moved for good. Search engines transfer the old page's signals to the new URL. This is the redirect you want in most cases.
302 Found and 307 Temporary: the page is moved temporarily, for example during maintenance or a short campaign. Search engines keep the original URL indexed.
308 Permanent: similar to 301, but strictly keeps the request method. Rarely needed for normal content sites.
410 Gone: not a redirect, but a signal that a page was removed on purpose and will not return.

Redirect status codes explained: 301, 302 and 307, 308 and 410

When You Need a Redirect

You changed a post or page slug.
You merged several thin articles into one complete guide.
You changed the permalink structure.
You moved from HTTP to HTTPS, or from one domain to another.
You deleted a product or service that has a close replacement.
You migrated from another platform, such as Blogger, to WordPress. See migrating from Blogger to WordPress.

How to Choose the Right Destination

Redirect each old URL to the most relevant new page, not to the home page. A visitor looking for a guide to backups should land on your backup guide. Redirecting everything to the home page confuses visitors and search engines often treat it like a missing page.

If there is no relevant replacement at all, it is better to let the old URL return a 404 or 410 status with a helpful custom error page. Our guide on creating a custom 404 page shows how to keep those visitors on your site.

Method 1: A Redirect Plugin

For most WordPress users, a redirection plugin is the easiest choice. You enter the old path and the new URL, choose 301, and save. Good plugins also:

Log 404 errors so you can see which broken URLs visitors actually hit.
Create redirects automatically when you change a post slug.
Support regular expressions for redirecting whole groups of URLs.
Import and export redirect lists.

Many SEO plugins include a redirect manager as well, so check before installing a separate plugin.

Method 2: Server-Level Redirects

Redirects at the server level are processed before WordPress loads, which makes them very fast. On Apache servers you add rules to the .htaccess file; on Nginx, rules go in the server configuration, usually through your host. For example, an Apache rule looks like this:

Redirect 301 /old-page/ https://www.example.com/new-page/

Server rules are ideal for domain moves and HTTPS redirects. Always back up the file before editing, because a typo can take the whole site offline.

A redirect chain from A to B to C compared with direct redirects to the final URL

Method 3: Redirects at Your Host or CDN

Some managed hosts and CDNs offer redirect rules in their dashboard. They are fast and survive theme or plugin changes. They are a good home for domain-wide rules, while page-level redirects stay easier to manage in a plugin.

Avoid Redirect Chains and Loops

A chain happens when URL A redirects to B, which redirects to C. Each hop slows the visitor down and can weaken the signal passed on. A loop happens when A redirects to B and B redirects back to A, so the page never loads.

When you change a URL that is already a redirect destination, update the old redirects to point directly to the newest URL.
Keep a single list of redirects in one place.
Test important redirects with a redirect checker or your browser's network panel.

Update Internal Links Too

Redirects are a safety net, not a replacement for correct links. After changing URLs, update your menus, buttons, internal links and sitemap so they point directly to the new address. In Elementor, check header and footer templates and any hard-coded links in widgets. When moving domains, the Replace URL tool helps, as covered in moving an Elementor site to a new domain.

After Adding Redirects

Test a sample of old URLs in a private window.
Submit your updated sitemap in Google Search Console.
Watch the Pages report for "Page with redirect" and "Not found" entries over the next weeks.
Keep 301 redirects in place for at least a year, ideally permanently, since links on other websites rarely get updated.

Planning a Large URL Change

When you restructure many pages at once, such as merging a category or replacing an entire section of a blog, plan the redirects before changing anything.

Export a list of all current URLs from your sitemap or an SEO crawler.
Add a column with the new destination for each old URL.
Mark pages that will be removed with no replacement.
Check Search Console and Analytics to find which old pages bring the most traffic, and give those the closest possible matches.
Import the redirect list, test a sample, then publish the new structure.

A simple spreadsheet like this becomes your record of what changed and why, which is useful months later when someone asks where an old page went.

Redirects and Elementor Popups or Forms

Do not forget URLs stored inside your designs. Popup display conditions and triggers that target specific URLs, form redirects after submission, and buttons in templates may still point to the old addresses. Review them after any URL change so visitors do not land on a redirect on every click.

Frequently Asked Questions

Do redirects hurt SEO?

A well-planned 301 redirect to a relevant page keeps most of the value of the old URL. Problems come from redirecting to irrelevant pages, long chains, or removing redirects too early.

How many redirects are too many?

Thousands of redirects are fine when they are processed efficiently, for example at the server. Performance problems usually come from chains and inefficient rule patterns rather than the count.

Should I redirect deleted products?

Redirect to a close replacement or the relevant category if one exists. If the product is gone with no alternative, a 410 status or a helpful 404 page is more honest.

Can I redirect a URL to another website?

Yes. A 301 redirect can point to any address, which is useful when content moves to a new domain. Make sure the destination is relevant and stays online, because a redirect to a broken page is worse than none.

Wrapping Up

Use a 301 redirect whenever a page moves permanently, point it to the most relevant new page, avoid chains and loops, update internal links, and keep redirects in place long term. With a simple redirect habit, changing URLs no longer means losing visitors or rankings.