1.4
Path Forwarding
Redirect the domain. Keep the path.
Send yoursite.com/blog/post to newsite.com/blog/post automatically - no rebuilding every single URL by hand.
Why it matters
Domain migrations break more than the homepage - every blog post, product page, and old campaign link needs somewhere to land. Rebuilding thousands of individual redirects by hand is slow and error-prone. Path forwarding carries the rest of the URL along automatically.
How it works
The whole path, carried over.
Redirect an entire URL structure in one rule, instead of rebuilding every link by hand.
Tech, explained simply
Wildcard rules, not one-off links
A normal redirect maps one URL to another. Path forwarding uses a wildcard rule - everything after the domain gets carried over to the new destination automatically, so oldsite.com/* becomes newsite.com/* in one step.
This matters most during migrations and rebrands, where hundreds or thousands of pages need to move at once. Instead of writing a rule per page, you write one rule per pattern.
Specific exceptions still take priority over the wildcard, so you can redirect everything in bulk and still carve out special cases where a page should land somewhere different.
FAQs
Everything you might ask about path forwarding
Does this work for an entire site migration?
Yes - this is the standard approach for moving one domain's structure to another.
What if the new site doesn't have a matching page for every old URL?
You can set fallback or exception rules for pages that need a different destination.
Do query parameters and UTM tags carry over?
Yes, by default parameters are preserved unless you configure otherwise.
Can I forward just one folder instead of the whole domain?
Yes - wildcard rules can be scoped to any subpath, like /blog/*.
Will this affect my SEO rankings?
Path forwarding with 301s is the standard method search engines use to transfer ranking signals during a move.
Have more questions?
Other features