Manage WordPress Redirects From One Place
URLs change for many reasons.
A page gets renamed. A product is replaced. Categories are reorganized. A website moves to a new structure. An SEO migration changes hundreds of paths. Sometimes a temporary campaign simply needs to send visitors somewhere else for a while.
Without a redirect, anyone following the old URL may encounter a missing page.
Redirect Manager gives you a central WordPress interface for defining exactly what should happen when those old URLs are requested.
Instead of editing .htaccess, modifying NGINX configuration, or adding custom PHP for routine redirects, you can create and manage rules directly through WP PowerSuite.
For a simple URL change, that might mean one 301 redirect. For a large migration, it could mean wildcard or regex rules capable of handling entire sections of the website.
Create Simple Exact Redirects
The most common redirect is also the simplest.
If:
/old-page/
has permanently moved to:
/new-page/
you can create an Exact rule connecting those two URLs.
The source can be entered as a path or complete URL, while the destination can be another path, a full HTTP/HTTPS URL, or a WordPress post or page selected directly from the interface.
Exact rules are ideal when there is a clear one-to-one relationship between an old URL and its replacement.
For SEO migrations and deleted content with an appropriate replacement, this gives you precise control instead of redirecting every missing page to a generic destination.
Redirect Entire URL Patterns With Wildcards
Creating individual redirects becomes inefficient when dozens or hundreds of URLs follow the same structure.
Wildcard redirects allow one rule to match an entire group of URLs.
For example, a pattern such as:
/old-blog/*
can capture the remaining portion of the URL and use it in the destination.
This is useful when moving directories, changing content structures, reorganizing documentation, migrating product sections, or replacing predictable groups of URLs.
Captured portions of wildcard matches can be reused in the target, allowing a single redirect rule to replace what might otherwise require a long list of individual redirects.
Build Advanced Redirects With Regex
For more complex migrations and URL structures, Redirect Manager supports regular-expression matching.
Regex gives developers much greater control over which requests match a rule and which parts of the source URL should be captured for the destination.
Captured values such as $1, $2, and additional groups can then be used to construct dynamic destination URLs.
Because poorly constructed regular expressions can cause performance or matching problems, WP PowerSuite validates regex patterns and rejects patterns considered unsafe.
Wildcard rules remain the easier choice for straightforward patterns, while regex is available when more precise matching is genuinely required.
Choose the Right Redirect Status
Not every redirect means that a URL has permanently moved.
Redirect Manager supports:
301 — Moved Permanently
302 — Found / Temporary Redirect
303 — See Other
307 — Temporary Redirect
308 — Permanent Redirect
A 301 is the default and is generally appropriate when an old URL has permanently been replaced by another.
Temporary redirects can be used when the original URL may become valid again or when the destination is intentionally temporary.
Having redirect status available per rule means you can choose behavior based on the purpose of each URL rather than applying one redirect type across the entire website.
Add Conditions to Redirect Rules
Sometimes the requested URL alone should not determine what happens.
Redirect Manager allows rules to include additional conditions. A redirect can depend on whether the visitor is logged in or logged out, whether the referring URL contains a particular value, whether a specific query parameter is present or matches a value, or whether the visitor's accepted language matches selected language codes.
All enabled conditions for that rule must match before the action runs.
This opens up more advanced routing possibilities without requiring separate custom PHP snippets.
For example, the same URL structure can behave differently based on query parameters, or a rule can be limited to requests arriving from a particular referral source.
Return an Error Instead of Redirecting
Redirect Manager is not limited to sending visitors somewhere else.
A matched URL can instead return an HTTP error response.
Supported responses include 401, 402, 403, 404, 405, 410, 501, 502, and 503.
You can also provide a custom message for the response.
This can be particularly useful when content has intentionally been removed and should not have a replacement. For example, a 410 Gone response can explicitly indicate that a resource has been permanently removed rather than redirecting visitors to an unrelated page.
It can also be useful for deliberately blocking specific legacy paths or returning controlled maintenance and availability responses.
Control Which Redirect Takes Priority
As a redirect collection grows, more than one rule may potentially match the same URL.
Each Redirect Manager rule has a configurable priority. Lower priority numbers are evaluated first, and more specific source patterns are considered when rules otherwise compete.
This lets you keep broad wildcard or regex rules while giving more specific exceptions precedence.
For example, a general rule could redirect an entire old section while a higher-priority exact rule sends one particular URL somewhere different.
This provides much more control than relying solely on the order in which redirects happen to appear in a list.
Keep Query Parameters or Remove Them
By default, query parameters from the incoming URL can continue to the redirect destination.
This is useful when links contain information such as campaign parameters that should survive the redirect.
When those parameters should not be carried over, enable Strip Query String for that individual rule.
The choice is made per redirect, giving you control over whether the destination receives the original query parameters.
Track Which Redirects Are Actually Being Used
Redirect rules often remain on websites long after anyone knows whether they are still receiving traffic.
WP PowerSuite records the hit count and last-hit time for each redirect rule.
This gives you practical context when reviewing your redirect collection.
A frequently triggered redirect may still be important because external websites, search results, bookmarks, or old marketing materials continue sending visitors to the original URL.
A redirect that has not been triggered for a long time may be worth reviewing as part of a cleanup, depending on your SEO and migration requirements.
Redirect Manager tracks usage of its own rules; it is not a general visitor analytics platform.
Import and Export Redirects in Bulk
Large migrations can involve hundreds of URL changes.
Instead of manually creating every redirect, Redirect Manager supports CSV import for bulk rules. A sample format is provided, and imported rows are checked before they are added.
Duplicate and invalid rules are skipped rather than blindly inserted.
Existing redirects can also be exported to CSV, making it easier to review them in a spreadsheet, move rules between websites, or keep an external copy of your redirect configuration.
This makes Redirect Manager practical for both everyday URL changes and larger SEO migration projects.
Redirect Manager, 404 Redirect, and URL Shortener
WP PowerSuite keeps these features separate because they solve different problems.
Redirect Manager is for deliberate source-to-destination rules. Use it when you know an old URL and where that URL should go.
404 Redirect is a catch-all fallback. It handles URLs that WordPress determines are missing and that have not already matched another redirect rule.
URL Shortener creates intentionally short, shareable URLs on your domain for campaigns, social media, marketing, and similar purposes.
Redirect Manager runs before 404 Redirect, so a precise rule gets the opportunity to handle the request before the general 404 fallback.
This makes it possible to combine the modules without sacrificing control over important redirects.
