Changing domains or permalink structures is where many WordPress sites lose traffic they did not mean to lose. The pages still exist, but the old URLs no longer do, and that is enough to break rankings, backlinks, and user journeys.

The fix is not just “add some redirects.” You need a redirect map that covers your main URL changes, uses permanent 301s where appropriate, and still catches the messy leftovers. This is exactly the kind of workflow we built Must-Have Redirect for.

Step 1: List what is changing before you touch URLs

Before you change the domain or save a new permalink structure in WordPress, map the old URL patterns to the new ones.

This matters because most migration problems are predictable. If your blog URLs are moving from /2024/05/post-name/ to /post-name/, you already know the shape of the breakage. If product or landing page slugs are changing, you can list those too.

Start with three buckets:

  1. One-to-one page moves
    – Example: /about-us to /about
    – Example: /contact-old to /contact

  2. Pattern-based changes
    – Example: /blog/old-category/post-name to /resources/post-name
    – Example: /*.html to cleaner WordPress URLs

  3. Uncertain or long-tail URLs
    – Old campaign pages
    – Typos in backlinks
    – Legacy URLs you may have missed

Your goal here is not perfection. It is to identify the redirects that should be explicit, then let the plugin handle the edge cases safely.

Step 2: Install Must-Have Redirect and set the core options

Once your mapping is ready, install the plugin in WordPress:

  1. Download the ZIP from your account.
  2. In WordPress admin, go to Plugins > Add New.
  3. Upload must-have-redirect.zip.
  4. Activate Must-Have Redirect.

Then configure the basics.

  1. Open the plugin settings area.
  2. Enable Smart 404 Handling.
  3. Set Similarity Threshold to Close Match (10% difference) to start.
  4. Choose a Custom 404 Page if you want a branded fallback when no good redirect exists.

We recommend starting with Close Match during a migration. It is stricter, which helps avoid overly aggressive redirects while your manual rules do the heavy lifting.

The custom 404 page is also worth setting up. Not every broken URL should redirect somewhere unrelated. If there is no sensible destination, a proper 404 page is often the safer outcome.

If you want setup details, see our Must-Have Redirect docs.

Step 3: Add manual 301 redirects for your important URLs

Your highest-value URLs should get manual permanent redirects.

In Must-Have Redirect, manual rules let you define:

  • Pattern
  • Destination
  • Status

For migration SEO, use 301 Permanent for old URLs that now have a clear new home.

Create those rules first:

  1. Add the old path in Pattern.
  2. Add the new path or destination URL in Destination.
  3. Set Status to 301.
  4. Save the rule.

A few examples:

  1. /about-us → /about with 301
  2. /services/web-design → /services/wordpress-development with 301
  3. /old-contact → /contact with 301

This is the part of the migration workflow that protects your most important rankings and backlinks. If a page has traffic, links, or business value, do not leave it to guesswork.

Also, keep the destination relevant. A redirect from an old service page to the homepage is technically valid, but often not helpful for users or search engines.

Step 4: Use wildcard redirects for permalink pattern changes

Manual one-by-one rules do not scale when the URL structure itself is changing. That is where wildcard redirects become useful.

Must-Have Redirect supports * wildcards in the Pattern field. Internally, we translate those patterns into anchored, case-insensitive matching, so they are useful for structured migrations.

Set up wildcard rules like this:

  1. Identify the old pattern.
  2. Match it with *.
  3. Point it to the closest new destination structure.
  4. Use 301 if the change is permanent.

Examples of pattern-based changes:

  1. old-product/*
    – Use when everything under an old section moved to a new section.

  2. *.html
    – Useful when older static-style URLs have been replaced by WordPress permalinks.

  3. Old dated or nested structures
    – For example, when legacy blog URLs follow one structure and the new site uses shorter slugs.

The practical advice here is simple: use wildcards only where the relationship is predictable. A broad rule can clean up hundreds of URLs, but a careless one can also send unrelated pages to the wrong destination.

In other words, wildcards are for pattern changes, not for papering over a messy migration.

Step 5: Let URL normalization reduce duplicate redirect noise

One part of this workflow we like is that Must-Have Redirect normalizes URLs before processing them.

That includes:

  • removing trailing slashes
  • filtering tracking parameters like utm_source, utm_medium, fbclid, and gclid
  • sorting remaining query parameters alphabetically

That matters because migrations often create what looks like a larger redirect problem than you really have. The same broken URL may appear in multiple forms, such as:

  1. /old-page/
  2. /old-page?utm_source=newsletter
  3. /old-page?fbclid=abc123

From a WordPress perspective, those should usually resolve consistently. Normalization helps your redirect rules match the underlying path instead of being fragmented by tracking junk.

If you need to remove an additional query parameter during migration, you can extend that behavior with the mhredirect/remove_query_params filter:

add_filter('mhredirect/remove_query_params', function($params) { $params[] = 'my_tracking_param'; return $params; });

For most sites, the defaults will already cover the common marketing parameters.

Step 6: Test the misses and use smart 404 matching for stragglers

Even a careful redirect map will miss something. Old backlinks, copied URLs in emails, and typo-heavy requests tend to show up after launch, not before.

This is where Smart 404 Handling becomes useful as a migration safety net.

Here is a practical post-launch routine:

  1. Visit old URLs from your mapping and confirm they resolve correctly.
  2. Test a few messy versions with tracking parameters attached.
  3. Check long-tail legacy URLs that may not have a manual rule.
  4. Review automatically created matches and their hit counts.
  5. Convert frequently used auto matches into manual 301 redirects where appropriate.

By default, smart matches create auto rules with 302 status. That is intentional. It gives you a safe temporary layer for missed URLs, while you review what users and crawlers are actually requesting.

If an auto match is clearly correct and keeps getting hits, edit it into a permanent manual rule. That turns an improvised catch into part of your long-term redirect map.

The point is not that Smart 404 replaces planning. The point is that it catches the migration leftovers you did not know you had.

Step 7: Watch for loops and keep the cleanup sensible

After launch, a redirect setup should stay maintainable.

Must-Have Redirect includes loop prevention, so redirects are skipped if the destination path equals the current normalized path. That helps avoid one of the more frustrating migration mistakes.

You should still do a quick review:

  1. Check that no old path redirects to itself in a different form.
  2. Confirm wildcard rules are not too broad.
  3. Review hit counters to see which redirects are actually being used.
  4. Keep strong manual 301 rules for important paths.

Auto-generated rules are also cleaned up over time. On Sundays, the plugin removes stale auto rules from previous weeks or ones with fewer than 10 hits. That helps keep the temporary migration layer from becoming clutter.

Take-home message

If you want to change permalink structure safely or move to a new domain without throwing away existing SEO value, the key is coverage. Plan your redirect map, create manual 301s for important URLs, use wildcard rules for structural changes, and let smart matching catch the stragglers.

Done properly, WordPress migration redirects are not just a patch after launch. They are part of the migration itself. If you want a focused tool for that workflow, explore Must-Have Redirect and see how it fits your site.