How to Redirect Hundreds of Domains Without Managing Them One by One
Direct Answer
To redirect hundreds of domains without touching each one, manage them in one redirect service instead of at each registrar: list the domains and their destinations in a CSV, import it once, point each domain's DNS to the service, and let it issue HTTPS for every domain. After that you change destinations in groups by tag, and see which domains still get visitors, from one dashboard.
A portfolio of a few hundred domains is normal for a domain investor, a company that has bought other brands, or an agency that looks after its clients' old domains. Every one of those domains should land somewhere useful: the main site, a regional page, a product page or a for-sale page. Doing that one domain at a time, in several registrar accounts, is where portfolios start leaking traffic.
Why registrar forwarding stops working at portfolio scale#
Most registrars include free domain forwarding, and for one or two domains it is fine. With a portfolio, the same feature turns into a list of small problems:
| Task | Forwarding at each registrar | One redirect service |
|---|---|---|
| Setup | One form per domain, in every registrar account you use | One CSV import for all domains |
| HTTPS on the old domain | Often missing, so https:// visits show a certificate warning | A certificate issued automatically for each domain |
| Keeping the path (old.com/about → new.com/about) | Depends on the registrar | A setting per redirect |
| Changing 80 destinations at once | 80 forms | Select by tag, change once |
| Which domains get visitors | Usually not shown | Clicks per domain and tag |
| Where the rules live | Spread across accounts | One list you can export |
The HTTPS gap matters most. Browsers and many apps open links over https:// by default, so a forwarded domain without a certificate shows a warning instead of your site. If you use GoDaddy, our GoDaddy forwarding guide shows how this looks in practice.
Step 1: List every domain and where it should go#
Export the domain list from each registrar and merge it into one spreadsheet. For each domain, decide the destination and add a tag that groups it, such as the brand, the country or "for sale". Tags are what let you change many domains at once later.
| Domain type | Usual destination | Example tag |
|---|---|---|
| Typos and other TLDs of your brand (.net, .co) | The main site | Brand |
| Country domains (.de, .co.uk) | The regional section of the main site | DE, UK |
| Product or campaign domains | That product or campaign page | Product |
| Acquired brands | The matching page on the new site, keeping paths | Acquired |
| Domains you want to sell | A for-sale page or marketplace listing | For sale |
Step 2: Import the portfolio from one CSV#
In RedirHub, a bare domain in source_url redirects the whole domain, and its www version comes with it. Tags go in one quoted cell. The full format, with every column and error message, is in the CSV import reference.
textsource_url,destination,type,tags
mybrand.net,https://mybrand.com,301,Brand
mybrand.co,https://mybrand.com,301,Brand
mybrand.de,https://mybrand.com/de,301,"Brand,DE"
mybrand.co.uk,https://mybrand.com/uk,301,"Brand,UK"
oldbrand.com,https://mybrand.com/oldbrand,301,Acquired
shortpremium.io,https://mybrand.com/domains-for-sale,302,For saleBefore anything is saved, the import shows how many domains and links it adds, what it uses from your plan, and any rows to fix, such as a destination without https://. Domains for sale get a 302, because the destination will change when the domain sells.
Step 3: Point DNS, in batches if you like#
Each domain starts redirecting once its DNS points to RedirHub. Domains on Cloudflare can be connected automatically; elsewhere you add an A record for the root and a CNAME for www. See Connect DNS. You don't have to switch everything on one day: a domain that is still waiting doesn't hold up the others, and the dashboard shows which ones still need DNS.
For very large portfolios, the Nameservers add-on on Pro lets you delegate domains to RedirHub's name servers instead of adding records to each one.
Step 4: Let HTTPS issue itself#
As each domain's DNS goes live, RedirHub requests a certificate for it (and for www when www points to RedirHub too) and renews it automatically. If something in a domain's DNS blocks the certificate, such as a CAA record, you get an email naming the domain. Details in Automatic HTTPS.
Step 5: Change destinations in groups#
Filter Links by a tag, select the results and change the destination for all of them at once. Every bulk change shows a preview first. Typical jobs: a regional site moves, a rebrand changes the main domain, or a batch of domains moves to a new marketplace. See Edit, change destination and export links in bulk.
Step 6: See which domains are worth keeping#
Analytics breaks visits down by domain and by tag, with countries, referrers and devices, and a Humans only switch leaves bot traffic out. That answers the questions a portfolio owner keeps asking: which domains still bring people, which typo domains are worth renewing, and which for-sale domains get enough type-in traffic to price higher.
What it costs#
In RedirHub, a whole-domain redirect uses one domain from your plan and no managed links, so a portfolio is priced by the number of domains.
| Plan | Price | Domains included | Fits |
|---|---|---|---|
| Core | $49/month | 25 | A brand with its typos and country domains |
| Pro | $119/month | 250 | Most investor and multi-brand portfolios |
| Enterprise | By contract | Set by contract | Thousands of domains |
Domain capacity can also be expanded on its own, without changing plans. Both plans start with a 14-day free trial. See pricing.
Mistakes that cost portfolio traffic#
- Forgetting www: if www.mydomain.net has no DNS record, half the type-in traffic never arrives.
- Sending an acquired site to the homepage: pages with links and rankings should go to their closest equivalent, with paths kept.
- Chains: a domain that forwards to another redirect domain adds a hop for every visitor. Point each domain straight at the final URL; see Fix redirect chains and loops.
- Letting a domain expire while it still gets traffic: check the per-domain visits before each renewal date.
Automating it#
When domains come and go every week, script it with the API or keep the whole portfolio in Git with the Terraform provider. Auto-Redirect (Enterprise, or Pro with the Dedicated Cluster add-on) creates the redirect by itself as soon as a new domain points to RedirHub.
Redirect your whole portfolio Import your domains from one CSV, get HTTPS on every one, and see which domains still bring visitors. 14-day free trial.
See domain parkingFrequently asked questions
Add each domain as a whole-domain redirect to the same destination, or import them all from one CSV with source_url and destination columns. Then point each domain's DNS to the redirect service. HTTPS is issued for each domain automatically.
For a few domains, often yes. With hundreds, it usually means one form per domain, missing HTTPS on the forwarded domain and no traffic data, so a central redirect service saves time and visitors.
No. In RedirHub a root domain also covers its www version, as long as www points to RedirHub in DNS. Add a separate www redirect only if it needs a different destination.
In RedirHub a whole-domain redirect uses one domain and no managed links. Pro includes 250 domains for $119/month, and Core includes 25 for $49/month. Enterprise is set by contract.
A 302, because the destination will change when the domain sells. Use a 301 for domains that permanently belong to a brand.
Yes. RedirHub Analytics breaks clicks down by domain and tag, and can leave bot traffic out, so you can decide which domains are worth renewing.
TC is the Operations Manager at RedirHub, leading the company’s operational strategy and execution to ensure reliable, scalable redirect infrastructure. He oversees internal processes, cross-team coordination, and platform readiness while supporting customers through complex redirect implementations. With a strong understanding of large-scale domain operations and real-world edge cases, TC plays a key role in aligning product and customer success to deliver stable, high-performance redirection solutions.
Related Articles
View All Articles
