Skip to content
Black Friday 50% off + 15,000 credits Ends Nov 30 Ends Nov 30 see the deal
Black Friday15,000 free credits + 50% offends Nov 30

How to Redirect a Page in WordPress (301s, Plugins and Server Rules)

You renamed a page, merged two posts or moved a whole section, and the old addresses still get visits and links. A redirect sends them to the right place. WordPress makes some redirects on its own; the rest you add with a plugin or a server rule. Here is which to use, and how to avoid chains and loops.

In this article
  1. 01The short answer
  2. 02What WordPress redirects on its own
  3. 03301, 302, 307 or 308?
  4. 041. Add redirects with a plugin
  5. 052. Add redirects at the server
  6. 063. Avoid chains and loops
  7. 07After you move a page
  8. 08Where WPOS fits
Key takeaways
  • WordPress redirects a post's old address after a slug change, but not a page's.
  • Use a 301 (or 308) for permanent moves; Google then shows the new URL in search results.
  • The free Redirection plugin (2,000,000+ installs) covers most sites, including 404 tracking.
  • Server rules work too: Redirect 301 in .htaccess on Apache, return 301 on Nginx, or your host's redirect rules.
  • Point every old URL straight at its final address; Google's crawlers follow at most 10 hops.
  • Redirect loops come from two rules undoing each other, such as Cloudflare's Flexible SSL plus a forced HTTPS redirect.

The short answer

Send each old address to its new one with a 301, in one hop.

  1. Check what WordPress already does. A post whose slug changed redirects on its own; a page doesn’t.
  2. Use a 301 for anything permanent, and a 302 only for short-term moves.
  3. Add the redirect with a plugin such as Redirection, your SEO plugin, your host’s redirect rules or a server rule.
  4. Test each old URL: it should reach the new page in one hop and answer 200.

What WordPress redirects on its own

  • Changed post slugs. When you change the slug of a published post, WordPress 7.1 stores the old slug and answers the old address with a 301 to the new one. The same goes for media attachments.
  • Not pages. WordPress only does this for “published, non-hierarchical” content, and pages are hierarchical. Rename a page’s slug and its old address returns a 404 until you add a redirect yourself.
  • Canonical addresses. WordPress also sends a 301 from variations of an address, such as ?p=123, to the address it considers canonical.
  • Nothing else. There’s no settings screen for your own redirects; that takes a plugin, your host or a server rule.

301, 302, 307 or 308?

Google’s redirect guide splits redirects into permanent and temporary ones:

CodeMeaningUse it for
301Moved permanentlyRenamed, merged or moved pages: the usual choice
308Moved permanentlyThe same, for setups that need it
302Found (temporary)A short-term move, such as a page under maintenance
307Temporary redirectThe same as 302

With a permanent redirect Google shows the new address in search results; with a temporary one it keeps the old address. Google reads server-side redirects most reliably; a meta refresh comes next, and a JavaScript redirect is the last resort.

1. Add redirects with a plugin

For most sites a plugin is the easiest way, and Redirection is the most used free one. Its documentation says you’ll find it under Tools → Redirection once it’s installed:

  1. Install and activate Redirection, then open Tools → Redirection.
  2. Add a redirect: the old path as the source, such as /old-page/, and the new address as the target.
  3. Keep the type as 301 unless the move is temporary, and save.
  4. Open the old address in a private window and check you land on the new page.

Redirection can also watch for permalink changes and add the redirect for you, which covers the page renames WordPress leaves out, and its 404 log shows the old addresses visitors still try. Other options (installs from WordPress.org on 13 November 2026, all tested with WordPress 7.1.4):

PluginActive installsNotes
Redirection2,000,000+Free. 301s, full regular expressions, 404 tracking, a log, and it can add a redirect when a permalink changes
Rank Math SEO4,000,000+Its listing includes a redirection manager and a 404 monitor
Yoast SEO10,000,000+The redirect manager is a Premium feature, with bulk tools and CSV import
301 Redirects – Redirect Manager300,000+A simple list of redirects
Simple 301 Redirects100,000+A simple list of redirects
Safe Redirect Manager40,000+Redirects as a post type, popular with developers

Pick one place for redirects. Two plugins that both manage redirects make it hard to see which rule fired.

2. Add redirects at the server

Server rules run before WordPress loads, so they’re the quickest, and they work for addresses WordPress never sees, such as old .html files. Take a backup of the file before you edit it.

  • Apache (.htaccess):
    Redirect 301 /old-page/ https://example.com/new-page/
    Always give the code. Apache’s documentation says that without it the redirect is temporary (302). The old path also matches everything below it, so /old-page/ moves /old-page/photos/ too.
  • Nginx:
    location = /old-page/ {
        return 301 https://example.com/new-page/;
    }
  • Managed hosts often replace both with a page in their dashboard. WP Engine, for example, has deprecated .htaccess: new redirects go in the User Portal’s Web Rules page, on the Rewrite rules tab.

Moving a whole static site into WordPress? Our guide to converting HTML to WordPress covers mapping every old .html address to its new page.

3. Avoid chains and loops

  • Chains: A → B → C wastes time on every visit. Google’s crawlers follow up to 10 redirect hops; point every old address straight at its final one, and update old rules when a page moves again.
  • Send each page to its closest match, not everything to the homepage, so visitors land where they expected.
  • Loops (ERR_TOO_MANY_REDIRECTS): two rules undo each other. A common one is described in Cloudflare’s documentation: with the Flexible SSL mode Cloudflare reaches your server over plain HTTP, and if the server forces HTTPS, the visitor bounces back and forth. Other causes are a rule whose target matches its own source, or the same move set up in two places.
  • Duplicates aren’t a redirect problem. Two live copies of the same page compete with each other in search; our guide to duplicating pages covers what to do with copies.

To see every hop an address takes, run this from a terminal; it prints each status code and the next location:

curl -sIL https://example.com/old-page/ | grep -iE '^(HTTP|location)'

After you move a page

  • Update your own links. Menus, buttons and links inside other posts should point at the new address, so your visitors never take the redirect hop at all.
  • Keep the redirect. Old links in emails, social posts and other sites keep arriving long after the move; removing the rule turns them into 404s.
  • Check the sitemap. WordPress’s built-in sitemap lists each page’s current address, so it updates itself; an SEO plugin’s sitemap should do the same.
  • Watch the 404s. Redirection’s 404 log, or the Pages report in Google Search Console, shows the old addresses that still need a rule.

Where WPOS fits

WPOS includes a redirect manager. The agent can add 301, 302, 307 or 308 redirects, or answer 410 Gone for pages removed for good. It matches on the path and passes the visitor’s campaign tags through to the new page. It works inside wp-admin and checks its own work, so a batch of redirects becomes one request:

“The /services/ pages moved to /solutions/. Add a 301 for each old URL to its new page, then open every old URL and confirm it lands on the right page in one hop with a 200.”

WPOS is our product, so weigh this section accordingly; you can try it free for 30 days with 5,000 credits, a live site plus a staging sandbox, and no card.

Frequently Asked Questions

Only for posts. When you change a published post's slug, WordPress remembers the old one and sends a 301 to the new address. Pages are left out, so changing a page's slug breaks its old URL until you add a redirect.

A 301 says the page has moved for good, so Google shows the new URL in search results. A 302 says the move is temporary, so Google keeps showing the old one. Use 301 for renamed or merged pages; 308 and 307 are the other permanent and temporary codes.

Redirection is the most used free option, with 2,000,000+ active installs: it handles 301s, regular expressions and 404 tracking. Rank Math and Yoast SEO Premium include redirect managers too, so if you already pay for one of those, use it.

Yes. On Apache, add a Redirect 301 line to .htaccess; on Nginx, a return 301 rule; many managed hosts have a redirect page in their dashboard. Some hosts, such as WP Engine, no longer use .htaccess, so use their dashboard instead.

Two rules are sending the visitor back and forth. Look for a redirect that points back at its own source, and if you use Cloudflare, check its SSL mode: Flexible mode plus a server that forces HTTPS is a loop Cloudflare's own documentation describes.

A clean 301 sends visitors and search engines to the new page, and Google uses it as a strong signal to show the new URL. Chains slow that down, and Google's crawlers follow at most 10 redirect hops, so point every old URL straight at its final address.

Black Fridayends Nov 30

Start free with 15,000 credits.

Three times the usual 5,000, no card needed. Then 50% off your site licences for 2 months with FRIDAY50.

Claim 15,000 credits