To set up redirects in WordPress using the .htaccess file, locate the file in your site’s root directory and add redirect rules above the # BEGIN WordPress section. For basic 301 redirects, use the format Redirect 301 /old-page https://example.com/new-page. For pattern-based redirects, enable mod_rewrite and use rewrite rules like redirecting HTTP to HTTPS or changing URL structures. Always back up the file, test changes in a staging environment, avoid caching issues, check for conflicts with plugins, and ensure syntax accuracy to prevent errors.
Setting up redirects in WordPress using the .htaccess
file is a straightforward way to manage URL changes, especially when moving content or reorganizing your site. It’s fast, doesn’t require plugins for simple cases, and works at the server level. But it also needs to be done carefully—especially if you're not used to working with server configuration files.
Understanding Where to Add Redirects
The .htaccess
file is usually located in the root directory of your WordPress installation. If you're using an FTP client or your hosting control panel (like cPanel), you can find it there. Keep in mind that this file might be hidden by default, so make sure your file browser shows hidden files.
Before making any changes:
- Always back up your
.htaccess
file. - Test redirect rules on a staging environment if possible.
You'll want to place your redirect rules above the # BEGIN WordPress
section in the file. That way, they won't get overwritten when WordPress updates its internal rewrite rules.
How to Do a Basic 301 Redirect
A 301 redirect tells browsers and search engines that a page has permanently moved to a new location. This is great for SEO because it passes most of the original page's ranking power to the new one.
To redirect an old page to a new one, use this format:
Redirect 301 /old-page https://example.com/new-page
Just replace /old-page
with the path of the old URL (relative to your domain) and the full URL of the new destination.
Some common variations:
- Redirecting a whole category:
Redirect 301 /old-category https://example.com/new-category
- Sending traffic from an outdated post to your homepage:
Redirect 301 /outdated-post https://example.com/
This method works well for small-scale redirects, but if you have dozens or hundreds, consider using a plugin or more advanced rewrite rules.
Using Rewrite Rules for More Flexibility
Sometimes you need something more flexible than basic Redirect
commands—like redirecting all URLs matching a certain pattern. For that, Apache's mod_rewrite
engine comes into play.
Here's a common example: redirecting all traffic from HTTP to HTTPS:
RewriteEngine On RewriteCond %{HTTPS} off RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Another example: redirecting all requests for old blog URLs like /blog/post-name
to /news/post-name
:
RewriteEngine On RewriteCond %{REQUEST_URI} ^/blog/(.*)$ RewriteRule ^blog/(.*)$ /news/$1 [R=301,L]
These rules are more powerful but also trickier. A single typo can break your site, so double-check everything and test after applying.
Common Mistakes and Tips
When editing .htaccess
, mistakes happen. Here are a few common pitfalls and how to avoid them:
- Caching issues: After setting up a redirect, clear both your browser cache and any caching plugins or CDN caches to see the change.
-
Conflicting rules: If you're using a redirection plugin in WordPress, it may conflict with manual
.htaccess
rules. Check both places if things aren’t working as expected. -
No syntax highlighting: Editing
.htaccess
in plain text makes it easy to miss errors. Use a code editor that supports syntax checking. - Overwriting rules: Make sure your redirect lines don’t get pushed below the WordPress-generated section—you’ll lose them after a permalink update.
If your site breaks after saving changes, restore your backup .htaccess
file immediately.
Basically, setting up redirects via .htaccess
is pretty straightforward once you understand the basics. Just remember to keep it clean, test often, and always have a backup handy.
The above is the detailed content of How to set up redirects in WordPress htaccess. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To roll back the WordPress version, you can use the plug-in or manually replace the core file and disable automatic updates. 1. Use WPDowngrade and other plug-ins to enter the target version number to automatically download and replace; 2. Manually download the old version of WordPress and replace wp-includes, wp-admin and other files through FTP, but retain wp-config.php and wp-content; 3. Add code in wp-config.php or use filters to disable core automatic updates to prevent further upgrades. Be sure to back up the website and database before operation to ensure safety and reliability. It is recommended to keep the latest version for security and functional support in the long term.

The steps to create a custom shortcode in WordPress are as follows: 1. Write a PHP function through functions.php file or custom plug-in; 2. Use add_shortcode() to bind the function to the shortcode tag; 3. Process parameters in the function and return the output content. For example, when creating button shortcodes, you can define color and link parameters for flexible configuration. When using it, you can insert a tag like [buttoncolor="red"url="https://example.com"] in the editor, and you can use do_shortcode() to model it

The main reasons why WordPress causes the surge in server CPU usage include plug-in problems, inefficient database query, poor quality of theme code, or surge in traffic. 1. First, confirm whether it is a high load caused by WordPress through top, htop or control panel tools; 2. Enter troubleshooting mode to gradually enable plug-ins to troubleshoot performance bottlenecks, use QueryMonitor to analyze the plug-in execution and delete or replace inefficient plug-ins; 3. Install cache plug-ins, clean up redundant data, analyze slow query logs to optimize the database; 4. Check whether the topic has problems such as overloading content, complex queries, or lack of caching mechanisms. It is recommended to use standard topic tests to compare and optimize the code logic. Follow the above steps to check and solve the location and solve the problem one by one.

Methods to optimize WordPress sites that do not rely on plug-ins include: 1. Use lightweight themes, such as Astra or GeneratePress, to avoid pile-up themes; 2. Manually compress and merge CSS and JS files to reduce HTTP requests; 3. Optimize images before uploading, use WebP format and control file size; 4. Configure.htaccess to enable browser cache, and connect to CDN to improve static resource loading speed; 5. Limit article revisions and regularly clean database redundant data.

Miniving JavaScript files can improve WordPress website loading speed by removing blanks, comments, and useless code. 1. Use cache plug-ins that support merge compression, such as W3TotalCache, enable and select compression mode in the "Minify" option; 2. Use a dedicated compression plug-in such as FastVelocityMinify to provide more granular control; 3. Manually compress JS files and upload them through FTP, suitable for users familiar with development tools. Note that some themes or plug-in scripts may conflict with the compression function, and you need to thoroughly test the website functions after activation.

TransientsAPI is a built-in tool in WordPress for temporarily storing automatic expiration data. Its core functions are set_transient, get_transient and delete_transient. Compared with OptionsAPI, transients supports setting time of survival (TTL), which is suitable for scenarios such as cache API request results and complex computing data. When using it, you need to pay attention to the uniqueness of key naming and namespace, cache "lazy deletion" mechanism, and the issue that may not last in the object cache environment. Typical application scenarios include reducing external request frequency, controlling code execution rhythm, and improving page loading performance.

Object cache assists persistent storage, suitable for high access and low updates, tolerating short-term lost data. 1. Data suitable for "persistence" in cache includes user configuration, popular product information, etc., which can be restored from the database but can be accelerated by using cache. 2. Select a cache backend that supports persistence such as Redis, enable RDB or AOF mode, and configure a reasonable expiration policy, but it cannot replace the main database. 3. Set long TTL or never expired keys, adopt clear key name structure such as user:1001:profile, and update the cache synchronously when modifying data. 4. It can combine local and distributed caches to store small data locally and big data Redis to store big data and use it for recovery after restart, while paying attention to consistency and resource usage issues.

The most effective way to prevent comment spam is to automatically identify and intercept it through programmatic means. 1. Use verification code mechanisms (such as Googler CAPTCHA or hCaptcha) to effectively distinguish between humans and robots, especially suitable for public websites; 2. Set hidden fields (Honeypot technology), and use robots to automatically fill in features to identify spam comments without affecting user experience; 3. Check the blacklist of comment content keywords, filter spam information through sensitive word matching, and pay attention to avoid misjudgment; 4. Judge the frequency and source IP of comments, limit the number of submissions per unit time and establish a blacklist; 5. Use third-party anti-spam services (such as Akismet, Cloudflare) to improve identification accuracy. Can be based on the website
