Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
A redirect sends visitors and search engines from an old WordPress URL to another address. For most beginners, the safest workflow is to install the free Redirection plugin, create a rule that maps the old path directly to its final destination, and test it. Use a permanent redirect when the move is lasting; use a temporary redirect only while the original URL may return.
What a WordPress redirect does
When someone requests an old URL, the web server or WordPress returns an HTTP response telling the browser to load a different URL. This preserves links, bookmarks and crawler paths after a page or permalink changes.
WordPress permalinks are the persistent addresses used for posts, pages and archives. Change them deliberately: redirect each old address to the most relevant new one instead of leaving visitors at an error page.
Choose the right redirect type
| Type | Use it when | Search meaning |
|---|---|---|
| 301 (permanent) | The URL move is intended to last | A permanent canonicalization signal; it does not guarantee a particular ranking |
| 308 (permanent) | The move is permanent and the server supports 308 behavior | Also signals a permanent destination |
| 302, 303 or 307 (temporary) | The original URL may be restored, such as during a short campaign or maintenance event | Does not provide the same permanent canonical signal by itself |
Google Search Central recommends a permanent server-side redirect whenever possible when changing a URL shown in search results. Select the status according to the real duration of the change, not because one code is presumed to improve rankings.
#1 Best Overall
The easiest method: Redirection plugin
The official Learn WordPress tutorial demonstrates the Redirection plugin for dashboard-based setup. Its WordPress.org listing describes it as a free redirect manager that can handle 301 redirects and 404 monitoring without requiring Apache or NGINX expertise, provided the site uses permalinks. Plugin compatibility and features can change, so review the current listing before installing.
- Back up first. Make a current backup and ensure the replacement page is published and working.
- Install the plugin. In WordPress, open Plugins > Add New, search for Redirection, install the plugin from its current WordPress.org listing, then activate it.
- Open the redirect screen. Follow the plugin’s setup prompts and open its Redirects section.
- Enter the source. Put the old permalink path in the source field. On a site at
https://example.com, an old address such ashttps://example.com/old-guide/is normally entered as/old-guide/. - Enter the target. Add the complete final destination path, such as
/new-guide/. Choose the plugin’s permanent redirect option for a lasting move. - Add the rule. Save or add the redirect, then open the old URL in a private browser window and confirm it lands on the intended page.
Keep the source-to-target mapping documented, especially when changing many URLs. The plugin’s logs and 404 reports can help identify old links that still need a relevant destination.
Redirects during a site move or large URL change
Build the URL map first
Create a complete list of old URLs and their final, relevant destinations before switching the site. Do not implement a rule until its target is ready. Include important post, page, category and other archive URLs that people or crawlers still request.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Send every old URL straight to the final page
Avoid chains such as old URL → intermediate URL → final URL. Each extra hop adds delay and creates another point of failure. Update existing redirect rules so the old address goes directly to the final destination.
Do not use the homepage as a mass destination
Google warns: “Avoid redirecting many old URLs to one irrelevant single URL destination, such as the home page of the new site.” Unrelated deleted pages redirected en masse may confuse visitors and can be treated as soft 404s. If no genuinely relevant replacement exists, a proper 404 or 410 response is often clearer than a misleading redirect.
Check supporting signals
- Use the new URL in the destination page’s canonical annotation.
- Remove robots directives that were only blocking indexing during development.
- Update internal links, XML sitemaps and navigation to use the final URLs.
- Keep the redirects active long enough for users, bookmarks and crawlers to encounter the change.
Server-level alternatives
A redirect can be handled before WordPress loads, using Apache configuration such as .htaccess or an NGINX rule. This is efficient for large, stable rule sets, but the exact syntax, file location and permissions depend on the host. Ask the host for its documented method rather than pasting an Apache rule into an NGINX server or editing a managed server file you cannot restore.
Server access is not included with every hosting plan. Keep a backup of the configuration, make one small change at a time and test both the old and destination URLs after reloading the server.
Developer option: redirecting in WordPress PHP
Code is appropriate when a developer needs conditional logic that cannot be maintained as a simple rule. WordPress’s wp_redirect() function defaults to HTTP 302, does not stop execution automatically and should almost always be followed by exit;. A minimal pattern is:
wp_redirect( $destination, 301 );
exit;
Place conditional logic in a suitable plugin or controlled theme environment, and ensure it runs before output is sent. A misplaced snippet can cause headers-already-sent errors, loops or unintended redirects, so beginners should prefer the dashboard method.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to test and troubleshoot
- Old URL shows a 404: verify the source path, trailing slash, capitalization and redirect group, then clear caching layers.
- Redirect loops: inspect both the source and target rules; make sure the target does not redirect back to the source.
- Too many hops: replace chained rules with one old-to-final rule and purge browser, plugin, CDN and server caches.
- Wrong page receives traffic: replace a generic target with the closest topical match; do not send unrelated URLs to the homepage.
- Changes appear inconsistent: test in a private window and check any CDN or host-level redirect settings in addition to WordPress.
- Search results still show the old URL: a permanent redirect is a signal, not an instant ranking or indexing guarantee. Keep the destination accessible and its canonical and internal links consistent.
Which method should you use?
| Your situation | Best starting point | Why |
|---|---|---|
| A few changed posts or pages and no server access | Redirection plugin | Dashboard workflow with redirect and 404 management |
| Many predictable rules and control of the web server | Apache or NGINX configuration | Rules run at the server layer, before WordPress |
| Conditional behavior requiring application logic | WordPress PHP | Flexible, but requires development knowledge and correct response timing |
Whichever method you choose, maintain one authoritative old-to-new map, point directly to final destinations and test representative URLs after every batch of changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
