'This guide shows how to redirect one URL to another in WordPress safely when a page slug changes, content is moved, or an old URL needs to point visitors to a new location. It focuses on the two practical methods most site owners actually use: a redirect plugin for easy management and .htaccess for direct server-level redirects.', 'howto' => [ 'Decide whether you only need a few redirects or long-term redirect management.', 'Use a redirect plugin if you want an easier non-code method.', 'Use .htaccess if you want a direct server-level redirect on Apache hosting.', 'Test the old and new URLs immediately after saving the redirect.', 'Watch for redirect loops, wrong destinations, or cached old behavior.' ], 'why' => 'When URLs change without redirects, visitors hit 404 pages and search engines lose a clean path to the new content. A proper redirect preserves access, protects old links, and reduces traffic loss after content moves or permalink changes.', 'faq' => [ [ 'q' => 'When should I use a 301 redirect in WordPress?', 'a' => 'Use it when an old page has permanently moved to a new URL and visitors should always land on the new page.' ], [ 'q' => 'Should I use a plugin or .htaccess?', 'a' => 'A plugin is usually easier for non-developers, while .htaccess is useful when you want direct server-level control on Apache.' ], [ 'q' => 'What is a redirect loop?', 'a' => 'It happens when one redirect sends traffic in a circle, causing the page to fail instead of loading normally.' ], [ 'q' => 'Why does the old URL still appear after adding a redirect?', 'a' => 'Browser cache, plugin cache, or CDN cache may still be serving an older version of the behavior.' ] ] ]; include_once $_SERVER['DOCUMENT_ROOT'] . '/inc/guides/related-guides-helper.php'; include_once $_SERVER['DOCUMENT_ROOT'] . '/inc/guides/related-tools-helper.php'; $relatedGuides = getAutoRelatedGuides($guideSlug, $guideCategory, 5); $relatedTools = getRelatedToolsForGuide($guideSlug, 5); include_once $_SERVER['DOCUMENT_ROOT'] . "/inc/header.html"; ?>

Guides

Step-by-step practical fixes for everyday technical problems.
WordPress Guides

How to Redirect a URL in WordPress Safely

Send old WordPress URLs to the correct new destination without causing loops, broken links, or lost traffic.

Before you start

Know the exact old URL and the exact new destination before creating the redirect.
Do not guess the redirect target. Test the final URL first and make sure it works normally.
If you edit .htaccess, back it up first so you can restore it quickly if the rule is wrong.

Step-by-step instructions

1. Use a redirect plugin for the safest non-code workflow

If you only need to manage redirects without touching server files, a dedicated redirect plugin is usually the safest option for most WordPress users.

Why this is useful

It keeps the redirect logic in a normal admin workflow and is easier to review, edit, and remove later than raw file changes.

2. Add the old path and the new destination carefully

Enter the original URL path as the source and the new URL as the target. Make sure you are not accidentally redirecting a page back to itself or to the wrong slug.

Typical example

If the old page was /old-page/ and the new page is /new-page/, the redirect should move traffic directly from the first path to the second one.

3. Use .htaccess if you want a direct Apache redirect

If your hosting uses Apache and you want a direct server-level redirect, add a rewrite rule to .htaccess.

.htaccess 
Redirect 301 /old-page/ https://example.com/new-page/
When this is good

This is useful when you want a simple, permanent redirect without depending on a WordPress plugin for that one rule.

4. Keep the redirect simple and direct

Do not chain multiple redirects together if you can avoid it. The old URL should go directly to the final new URL whenever possible.

Why this matters

Redirect chains slow things down, complicate troubleshooting, and make maintenance messier over time.

5. Test both the old URL and the new URL immediately

After saving the redirect, open the old URL directly and confirm it lands on the correct destination. Then open the new URL itself and confirm it loads normally on its own.

What you are checking

The old URL should redirect once to the correct final page. The new page should not bounce again in a confusing way.

6. Clear cache if the redirect looks inconsistent

If the redirect seems to work on one device but not another, clear browser cache, plugin cache, and CDN cache before assuming the rule is broken.

Common reason

Old cached responses often make redirect testing look inconsistent even when the rule was added correctly.

Common situations this fixes

You changed a page slug and old links now break

A redirect keeps visitors and search traffic moving to the new page instead of landing on a 404.

You merged two pages and want the old page to lead to the new one

A 301 redirect is the normal way to send traffic from the old page to the replacement page.

You moved content during a site cleanup or redesign

Redirects prevent older bookmarks, shared links, and indexed URLs from becoming dead ends.

You changed permalink structure and need a clean transition

Redirects reduce broken access after permalink-related URL changes.

Common mistakes

Redirecting to the wrong destination

Always test the target page first. A redirect to the wrong page is still a broken user experience.

Creating a redirect loop

If the old and new paths interact badly, the browser may get stuck in repeated redirection and the page will fail.

Leaving the redirect too broad

A broad rule can accidentally catch unrelated URLs and send visitors to the wrong place.

Testing without clearing cache

Cached behavior can make a new redirect look broken or make an old redirect appear to still exist.