Direct Answer
To move a site to a new domain, list every old URL, map each one to its new URL, and import the mapping into RedirHub as 301 redirects, plus a whole-domain redirect that catches anything you missed. Then point the old domain's DNS to RedirHub, submit a Change of Address in Google Search Console, and keep the redirects in place for at least a year.
| Item | Details |
|---|---|
| Goal | Every old URL lands on its new equivalent with one 301, so visitors, links and rankings carry over |
| You need | A list of old URLs, the new site live, access to the old domain's DNS and to Google Search Console |
| Redirect type | 301 Permanent |
Steps#
- List the old URLs from the sitemap, a crawl, and the pages that get traffic or links in Search Console and analytics.
- Map each old URL to its new URL. Use the closest equivalent page, not the homepage. The Migration Redirect Mapper can match old and new sitemaps for you.
- In Links, click Create and choose Website Migration, or import the mapping as a CSV (source_url, destination, type). The review shows every change and any rows to fix before anything is saved.
- Add a whole-domain redirect from old-domain.com to https://new-domain.com with Keep the path. Mapped URLs use their own link; anything unmapped falls back to this one instead of a 404.
- When the new site is live, point the old domain's DNS to RedirHub in Connect DNS. HTTPS for the old domain is issued automatically.
- In Google Search Console, verify both domains and submit a Change of Address from the old property to the new one. Update the sitemap and canonical tags on the new site.
- Check a sample of old URLs in the Redirect Checker: each should be one 301 to a page that answers 200. Watch Analytics in RedirHub for old URLs that still get traffic.
- Keep the redirects and the old domain for at least a year, and longer if old links still bring visitors.
Result#
| Request | Response | Lands on |
|---|---|---|
| https://old-domain.com/about-us | 301 | https://new-domain.com/company/about (mapped) |
| https://old-domain.com/blog/launch | 301 | https://new-domain.com/news/launch (mapped) |
| https://old-domain.com/contact | 301 | https://new-domain.com/contact (not mapped, path kept) |
| http://www.old-domain.com | 301 | https://new-domain.com/ |
For the business case and a full checklist, see Website Migrations. For the CSV format, see CSV import format.
Frequently asked questions
At least a year. Google recommends keeping them for a long time, and old links on other sites keep sending visitors for years.
No. Redirect each page to its closest equivalent. Sending everything to the homepage loses relevance, and search engines may treat it as a soft 404.
No. Once the old domain's DNS points to RedirHub, RedirHub answers its requests and issues HTTPS.
Core includes 2,500 managed links and Pro 10,000; Enterprise limits are set by contract. A whole-domain redirect uses a domain, not a managed link.