Website Migration Redirects

Your site moves. Your visitors follow.

Links, bookmarks and search results still point to your old domain. Point it at RedirHub and those URLs keep landing on the right pages of your new site, even after the old server is gone.

Visits to the old domain pass through RedirHub to the matching pages of the new site, while the old server is retired.

Built for moves that change the hostname

Domain changes · Rebrands · Acquired & legacy-site consolidation · Country-domain consolidation · Retiring old infrastructure

Same hostname? Those redirects belong at that origin, CDN or server.

How it works

From a list of old URLs to a server you can switch off

  1. 01

    Inventory

    List the old URLs that must keep working.

  2. 02

    Map

    Same paths, or one CSV row per changed URL.

  3. 03

    Review

    See every change before anything is written.

  4. 04

    Connect

    Point DNS here; HTTPS follows once it’s verified.

  5. 05

    Check

    Spot-check key URLs, then retire the old server.

Map

Same paths, or changed URLs

You choose every destination.

Same paths

oldbrand.com/* newbrand.com/*

  • /pricing?ref=email
  • /docs/setup?v=2
  • /about
  • /pricing?ref=email
  • /docs/setup?v=2
  • /about

path + query forwarding · covers its www

1 domain · 0 managed links

Changed URLs

old URL the new URL you pick

  • /about-us
  • /p/1182
  • /news/2023/launch
  • /blog/launch
  • /company
  • /products/widget-pro

CSV mapping · source, destination

1 managed link per row

No map yet? Build it with the free Migration Redirect Mapper

Review

Nothing goes live until you confirm

Upload the map, fix what’s wrong, and see exactly what it will write before you import.

  1. 01 / 03

    Fix invalid rows

    Errors are grouped by cause. Common ones can be fixed in one click.

    Import of rebrand-2026.csv: 14 rows need a fix, grouped by cause, with one-click fixes
  2. 02 / 03

    Review every change

    See what will be added or updated and how much plan capacity it uses.

    Import review: domains and links added, plan capacity after the import, and where the links are
  3. 03 / 03

    Confirm and import

    Nothing is written until you confirm.

    Import complete: domains and links added, and the DNS records still to set
  4. Recreated from the RedirHub dashboard with sample data. The review checks the file and your plan, not the pages your destinations point to.

Try it with your own redirect map.

View Pricing

DNS & capacity

Connect your domain and choose the right capacity

Bring the old domain online with RedirHub, then pick the capacity your migration needs.

01

Bring the old domain online

Point its DNS here. HTTPS follows once DNS is verified.

  1. 01

    DNS connected

    The dashboard’s record, at your DNS provider.

    www.oldbrand.com CNAME RedirHub

  2. 02

    DNS verified

    RedirHub sees the old hostname pointing here.

  3. 03

    HTTPS provisioning

    Requested automatically for the old hostname.

  4. 04

    Redirect active

    Old URLs are answered over HTTPS.

  5. 05

    Check key URLsYour step

    You spot-check them with the Redirect Checker.

  6. 06

    Retire old serverYour step

    Once everything looks good, you can turn it off.

Once DNS is verified, RedirHub automatically provisions HTTPS and activates the redirect when the secure connection is ready.

The dashboard shows the DNS record to add for each hostname: a CNAME, or an A record. A root domain, or any hostname on an A record, also needs a TXT record to verify it. Custom Name Servers are an optional paid add-on on Pro.

02

Choose the capacity you need

Plans are sized by managed links and domains.

A managed link is one changed URL. A whole-domain redirect uses a domain and no managed links.

FAQ

Questions before you move

Can I use RedirHub if my new site stays on the same domain?
Usually not for that part of the move. RedirHub answers for a hostname once its DNS points here, so it fits hostnames you are moving away from. If the new site keeps the same hostname, redirects for changed paths normally need to run at that site’s origin, CDN or server. If the move also retires other hostnames — an old country domain or a legacy subdomain — those can point to RedirHub.
How are managed links counted?
Each changed URL is one managed link. A whole-domain redirect that forwards paths and queries uses one domain and no managed links. Every old hostname you connect counts as one domain, and a root domain covers its www. The plan cards above show what each plan includes.
Do I need to map every URL?
No. If the paths stay the same on the new domain, one whole-domain redirect covers them all. If paths change, map the URLs that matter: pages with search traffic, backlinks, bookmarks, and anything printed or emailed. Your analytics and crawl exports are the usual starting point, and you can add more URLs later with another CSV import.
What happens during the DNS switch?
You point the old domain’s DNS to RedirHub. The dashboard shows the record to add for each hostname: a CNAME, or an A record. A root domain, or any hostname on an A record, also needs a TXT record to verify it. DNS changes take time to reach every resolver, depending on your provider and record TTLs. Once DNS is verified, RedirHub automatically provisions HTTPS and activates the redirect when the secure connection is ready. Keep the old server running until your key redirects check out, then retire it.
Does RedirHub check destinations before launch?
The import review checks the file and your plan: missing or malformed https:// in destinations, unsupported redirect types, plan capacity and duplicate www rows, and it shows every change before anything is written. It doesn’t visit the destination pages. After cutover, spot-check your most important old URLs with the free Redirect Checker.
Can I import tens of thousands of URLs?
Yes. Plans start at the included capacity and scale up: on Core and Pro you can add managed-link capacity. The review shows how many domains and managed links a file uses before you import it. For very large or multi-domain migrations, talk to sales about tailored capacity and onboarding.
Which plan fits my migration?
Start from two numbers: how many old hostnames you’re moving and how many changed URLs you’ll map. The plan cards above show what Core and Pro include; Pro also keeps a longer analytics history. Either plan can add capacity — enter your numbers in the pricing calculator to see the price.
How long should I keep old redirects?
For as long as the old URLs still get visits. Links on other sites, bookmarks and printed material don’t expire on your schedule. Redirect analytics show which old URLs are still in use, so you can retire redirects deliberately instead of guessing.