Viewing 1 replies (of 1 total)
  • Plugin Support Darin Kotter

    (@dkotter)

    Thanks for the question @dorjem, I’ll do my best to provide some answers.

    To start off, if you’re looking to redirect an entire site from one URL to another, generally you’ll be better off doing that at the server level, just for performance reasons.

    That said, this plugin will work for this use case if that’s the direction you want to go.

    For the redirects that you want to use wildcards (like /researchgroup/* https://researchgroup.com/) you’ll need to make sure you use the wildcard on both sides (so /researchgroup/* https://researchgroup.com/*).

    As far as ordering goes, I’m not 100% sure on this, you’ll want to set these redirects up and then test them out to be sure. The ordering you have I believe is the correct approach, where you add the most specific redirects first and the least specific ones last. This should ensure the wildcard matching isn’t too greedy, matching on URLs that have a more specific redirect set up.

    For instance, the redirect /researchgroup/* will match all URLs that have anything after the researchgroup part. This would include the category, tag and author URLs. But by having specific redirects for each of those added first, those more specific redirects should be picked up prior to the wildcard one matching.

    The one issue you might run into is between the first two rules there:
    /researchgroup/* https://researchgroup.com/
    /researchgroup/ https://researchgroup.com/blog/

    When using wildcard matching, it does not require there to be anything in the actual wildcard slot. This means both /researchgroup/* and /researchgroup/ can match at the same time. But I think as long as you add the wildcard one last, it should work. But if not, you probably need to make use of the regex functionality to ensure those redirects are seen as two separate items.

Viewing 1 replies (of 1 total)
  • The topic ‘Move domain name, what to do with unique urls?’ is closed to new replies.