Your Cart
Rank Math redirections

How to Set Up Rank Math Redirections for URL Changes, Deleted Content and Site Migrations

Changing a WordPress URL can create more than a broken link. A permalink update, deleted page, campaign landing page or site migration may leave visitors and search engines facing outdated paths. It can also create redirect chains, overly broad rules or a destination that does not match the original content. Rank Math redirections provide a way to organize these rules, but the quality of the result depends on decisions made before a rule is activated.

A practical workflow starts by classifying the change as permanent or temporary. Next, prepare a source-to-destination map, select the narrowest suitable match type, configure the rule and test both URLs that should match and URLs that should not. This approach also helps when scheduling rules, importing a larger set through CSV or reviewing redirect activity after deployment. The availability of some documented workflows depends on the Rank Math plan, so feature access should be confirmed before following product-specific instructions.

Choose the redirect status: 301, 302 or 307

The redirect status should reflect the expected lifetime of the URL change. A permanent move and a temporary diversion have different purposes, so selecting a status merely because it is familiar can create an inaccurate signal.

A practical status-selection decision

Use a 301 when the old URL has moved permanently. Typical cases include a permanent permalink change, a domain migration or consolidation into a relevant replacement URL. Google recommends permanent server-side redirects such as 301 or 308 for permanent moves. A 301 can signal that the destination should become the relevant canonical location.

Use a 302 when the redirect is temporary and the original URL is expected to remain relevant. This can apply to a temporary campaign, a short-term availability change or a controlled experiment. Do not select a permanent 301 simply because a temporary rule is convenient to create.

A 307 is also temporary, but it preserves the original request method during the redirect. That distinction is more important for non-GET requests than for ordinary page visits. In practice, first decide whether the change is permanent or temporary, then consider whether request-method handling makes 302 or 307 more appropriate. Google treats 302 and 307 as temporary redirect types.

Prepare the URL map before creating rules

Creating rules directly in the interface without first reviewing the URL relationships makes it easier to miss old paths, select unrelated destinations or introduce unnecessary intermediate steps. A small map gives every source URL a deliberate outcome.

Build a direct source-to-destination mapping

Record each old URL together with its intended final destination. For a permanent move, map the old path directly to the most relevant final URL rather than to an intermediate page. Google advises avoiding long redirect chains because they add latency and may create compatibility problems for some user agents and browsers.

Review the relevance of each destination before creating the rule. A destination should represent the intended replacement for the source, not merely be an available page. For a migration, prepare the old-to-final URL mapping before entering individual rules or a bulk import. Export or back up existing redirect rules before making broad changes, importing a CSV or applying a pattern that could affect many URLs.

Handle deleted content deliberately

Deleted content does not automatically require a redirect to the homepage. Use a replacement redirect when a genuinely relevant replacement exists. If no suitable replacement exists, evaluate whether an accurate 404 or an appropriate 410 response better represents the removed content. Rank Math documents 410 as a maintenance code for deleted content without a suitable replacement.

This distinction prevents a broad rule from hiding the actual state of removed pages. It also keeps the destination useful for visitors who followed an old link. The source-to-destination map should therefore include a deliberate outcome for deleted URLs instead of applying the same destination to every old path.

Rank Math redirect match types explained

Rank Math provides several ways to define which requested URLs a rule can match: Exact Match, Contains, Start With, End With and Regex. The broader the pattern, the more important it becomes to test positive and negative examples before activation.

From Exact Match to Regex

Exact Match targets the configured source URL only. It is the sensible starting point for an isolated URL change because its scope is limited to the specified path. If one old page has one replacement, this type reduces the risk of catching unrelated URLs.

Contains matches URLs containing the specified text, so it can affect multiple paths. Start With matches URLs beginning with the specified text, while End With matches URLs ending with it. These types can be useful for a reviewed group of URLs, but a short or common pattern may reach further than expected.

Regex uses a regular-expression pattern and can express more advanced groups with one rule. It also carries a higher risk of unintended matches. Apply it only when the pattern is understood and has been tested against representative URLs that should match and URLs that should not. A broad rule should never be activated solely because it is shorter than several precise mappings.

Case handling and multiple sources

Rank Math documents an Ignore Case option. Review whether ignoring case is appropriate for the particular rule rather than treating it as a default. Case handling can change which requests are included by a pattern, so it belongs in the test plan.

Rank Math also documents the ability to attach multiple source URLs to one destination. This is useful when several reviewed old paths genuinely share the same relevant replacement. Grouping should follow the content relationship, not convenience. Every source in the group should be checked before activation, especially when the rule uses a broader match type.

Create rules for URL changes, deleted content and migrations

Once the status and scope are decided, apply them to the actual change. Keep the rule aligned with the purpose of the URL change and avoid using a broad pattern when a precise source-to-destination mapping is available.

Permanent changes and migrations

For a permanent permalink or domain change, confirm that the old URL will not return as the primary location. Then map each old URL directly to its relevant final destination and use a permanent redirect status. A migration should be treated as a mapping exercise first and an interface exercise second: organize the old paths, review their destinations and only then create the rules.

After activation, update internal links and sitemap references so they point to preferred URLs rather than relying on redirects for normal site navigation. Direct references make the intended structure clearer and reduce unnecessary hops.

Temporary rules and removed content

For a temporary campaign, experiment or availability change, use a temporary status because the original URL is expected to remain relevant. The rule should not be treated as permanent canonicalization. Decide when it should stop applying and avoid leaving a temporary redirect active after the temporary situation ends.

For removed content, redirect only when a relevant replacement exists. Otherwise, evaluate an accurate 404 or 410 response. This is more precise than sending unrelated deleted URLs to the homepage and helps preserve the distinction between moved content and content that no longer has a suitable replacement.

Scheduling, statistics and CSV redirect workflows

Redirect management often continues after the first rule is created. Planned changes may need a defined activation period, while larger migrations may require a reviewed import and ongoing monitoring.

Scheduled activation and deactivation

Rank Math documents active and inactive redirect states. It also describes scheduled activation and scheduled deactivation as optional PRO features. Confirm the current plan and feature availability before presenting scheduling as available in a particular installation.

For a planned rule, distinguish between simply keeping it inactive and scheduling when it should become active or inactive. Before scheduling, verify the source, destination, status and match type. A scheduled broad rule can still affect unintended URLs, so timing does not replace pattern testing.

CSV import, export and monitoring

Rank Math documents CSV export and import for redirects as PRO functionality. Confirm that this functionality is available in the relevant license context. Before a bulk change, export or back up the current rules. Prepare a reviewed source-to-destination file and verify that the required source and destination fields are present. Without those fields, an imported redirect may not be created successfully.

A controlled workflow is safer than importing everything at once. Start with a small test batch, verify the resulting rules and then process the remaining reviewed mappings. Rank Math documents CSV operations that can create or update redirects and report statuses such as created, merged, updated and deleted.

For monitoring, Rank Math records redirect hits, creation time and last-accessed time. The documented statistics count both human and bot access. Treat the figures as directional operational data, not as unique visitors, conversions or proof that every redirect was used by a person.

Test, debug and maintain redirect rules

A redirect is not finished when it has been saved. Testing should confirm the response, destination and scope of the rule, while ongoing review should identify chains, unintended matches or changes introduced by later site work.

A practical test checklist

Open the old URL directly and confirm that it returns the intended response status, points to the expected Location target and reaches the correct final page. The final destination should be relevant to the original source and should not require an unnecessary intermediate redirect.

For Exact Match, test the configured source and a nearby URL that should remain unaffected. For Contains, Start With, End With and Regex, test representative positive and negative cases. Include paths that resemble the intended pattern but should not be redirected. This is particularly important for rules that could affect an entire section.

After deployment, check for redirect chains and loops. Verify canonical signals, internal links and sitemap references, and inspect crawl or indexing signals where relevant. Google’s migration guidance supports using direct final destinations, and its guidance also describes checking moved URLs with the URL Inspection tool. Use staging or a controlled test set where possible.

Debug unexpected redirects

When a request redirects unexpectedly, review the match type, pattern, source list and rule status before changing the destination. Rank Math provides a redirect debugger that can identify the rule responsible for a redirect. Its documented workflow is intended for administrators and displays an interstitial before the redirect proceeds.

Use the debugger to determine whether the issue comes from an overly broad Contains, Start With, End With or Regex rule, a case-handling choice or a source that was grouped with unrelated URLs. Then retest the original positive and negative examples. Continue reviewing redirect statistics and re-test after permalink, hosting, caching or migration changes, because a rule that worked in one environment may require renewed verification after site changes.

In summary, classify the URL change as permanent or temporary before selecting 301, 302 or 307. Build a source-to-final-destination map, choose the narrowest Rank Math match type that fits and avoid chains, loops and blanket homepage redirects. Confirm plan availability before using documented PRO workflows such as scheduling or CSV import and export. Test both expected and unintended matches, then review statuses, destinations, internal links, sitemaps and indexing signals after deployment. Remember that redirect statistics include bot activity, so they are not equivalent to human traffic or conversions. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń