WordPress Redirect Without Plugin: 2 Proven & Easy Methods

A broken link is an emergency. Instead of adding another redirect plugin to your stack, go straight to the source. Let’s pop the hood and wire in a redirect that’s as fast and reliable as your server itself.

We put this guide together to show you how to perform a WordPress redirect without using a plugin in minutes.

Just so we’re clear, this is a hands-on approach, and you’ll be dealing with core WordPress files. So you should only proceed if you’re comfortable making those kinds of changes yourself.

TL;DR: Use .htaccess for fast redirects and functions.php for conditional ones.  Before editing anything, always use a backup plugin to create a full site backup to protect your work.

Pre-redirection steps

Before you add a single line of code, preparation is everything. A few minutes spent here can save you hours of headaches later. 

How to perform a WordPress redirect without plugin

You have two primary paths for a manual redirect in WordPress. You can either edit a server configuration file or modify your theme’s files. Both work well, but they are suited for different jobs.

Method 1: Using the .htaccess file

This is our go-to for most simple, permanent redirects. The .htaccess file is a server configuration file. It tells the server what to do before WordPress even loads. This makes it extremely efficient.

☄️ Note: A robust backup strategy is non-negotiable here. Before you continue, confirm you have a complete, recent backup of your site.

Here are the steps to get it done:

1. Access your site’s files. You’ll need to use FTP via a client like FileZilla or your hosting provider’s File Manager.
2. Find the .htaccess file. It’s located in the root directory of your WordPress installation, usually the public_html folder. It’s a hidden file, so you may need to enable Show Hidden Files in your FTP client or File Manager settings.
3. Add your redirect rule. Right-click and open the file to edit it. Add your redirect code at the very top, before the # BEGIN WordPress line.

For a single, permanent redirect: 

Redirect 301 /old-page-slug/ https://yourdomain.com/new-page/

For a temporary redirect: 

Redirect 302 /old-page-slug/ https://yourdomain.com/new-temporary-page/

4. Save and upload. Save the file. If you edited it on your computer, upload it back to the server and overwrite the original.
5. Test immediately. Open a new browser window (preferably in incognito mode) and try to visit the old URL. It should instantly send you to the new one.

Method 2: The functions.php file

This PHP method is perfect for powerful, conditional redirects, like for logged-in users. However, you must use a child theme to protect your code from being erased during theme updates.

How to create a child theme: The fastest way is to use a free plugin like Child Theme Configurator. Install it, follow the steps to create and activate your child theme, and then you can safely remove the plugin. Your child theme will remain.

Once your child theme is active, follow these steps:

1. Access your child theme’s functions.php file. You can find this in your WordPress dashboard under Appearance > Theme File Editor, or via FTP in /wp-content/themes/your-child-theme-name/.
2. Add the redirect code. Add the following PHP snippet to the bottom of the file:

function my_custom_redirects() {

    if ( is_page('old-page-slug') ) {

        wp_redirect( 'https://yourdomain.com/new-page/', 301 );

        exit();

    }

}

add_action( 'template_redirect', 'my_custom_redirects' );

3. Customize the code. Change ‘old-page-slug‘ to the slug of the page you want to redirect. Update https://yourdomain.com/new-page/ to the full destination URL. The exit(); part is important. It stops WordPress from loading the rest of the old page, which saves resources.
4. Save and test. Save the file and test the old URL in your browser to make sure it works.

📁 Note: Restoring a WordPress site from a backup is the fastest way to recover if this code change causes an unexpected issue.

Method comparison: .htaccess vs. functions.php

So, which one should you use? It really depends on the job. There’s no single “best” answer, only the right tool for the task at hand.

Our verdict? For 90% of simple 301 redirects, use .htaccess. It’s the cleanest and highest-performing method. For those unique cases that require specific logic, functions.php is there when you need it.

⚠️ Note: Hardening WordPress is crucial, and part of this involves securing all core files, including the .htaccess file. Since these files are common targets for malicious code injections.

Advanced nuances and pro tips

Once you get comfortable with the basics, you can handle more complex situations. Here are a few things I’ve learned over the years.

Troubleshooting common issues

Even with careful preparation, things can go wrong. Here’s a quick checklist for when a redirect isn’t working as expected.

1. Clear your cache. This is the most common culprit. Your browser or your server might be caching the old version of the page. Clear all caches, including your browser, any caching plugins, and your CDN.

2. Check for a redirect loop. This happens when a URL gets redirected back to itself, creating an endless redirect loop. This is often caused by conflicting rules, especially with HTTP-to-HTTPS redirects.
3. Reset your permalinks. Go to Settings > Permalinks in WordPress and just click Save Changes without changing anything. This can sometimes fix .htaccess issues by regenerating the file.

Parting thoughts

Learning to create redirects without a plugin gives you more control over your site. You can fix errors faster and keep your site lean by avoiding another plugin. A correctly implemented 301 redirect is one of the most important skills for preserving your SEO value during site changes.

The best method always depends on your specific needs. But by mastering both the .htaccess and functions.php approaches, you’ll be prepared for any situation.

Just remember to always back up your site first. Good documentation of your manual redirects will also save you a lot of trouble down the road.

FAQs