Multiple Domains, One Website: Redirect, Don't Mirror

The usual story goes like this. A company registers brightkitchens.com, then brightkitchens.co.uk to protect the brand, then bright-kitchens.com because someone typed it wrong once, then brightkitchens.net because the sales rep offered a bundle. A few years later all four resolve, all four show the full website, and nobody remembers why. Search Console shows half the impressions on a domain nobody intended to promote.

Can multiple domains point to one website?

Yes, and it’s normal. The setup that works is boring on purpose: one primary domain carries the site, every other domain exists only to send people there with a permanent redirect. The secondary names are doors, not rooms.

What causes trouble is the other common setup, where the web server accepts all four hostnames and serves identical pages under each. Nobody is penalised for that. But Google sees four copies of every page, clusters them, and picks one canonical URL per cluster. Its choice is based on signals you only partly control, such as internal links, sitemaps and which version other sites link to. If the sales rep’s .net happens to collect a few links from directory listings, it may win.

Which setups are fine and which are not

The canonical tag deserves a remark. Google calls rel="canonical" a strong hint, while a redirect is followed by every visitor and every crawler. When the only goal is “everyone should end up on one domain”, the redirect is the cleaner signal and spares the server from answering for four copies.

Setting up the redirects

The key is that every secondary domain, in both http and https and with and without www, reaches the primary in one hop. That means the secondary domains need valid TLS certificates too. Someone typing https://brightkitchens.net should get a redirect, not a certificate warning.

On nginx, a single extra server block covers all aliases:

server {
    listen 80;
    listen 443 ssl;
    server_name brightkitchens.net www.brightkitchens.net
                bright-kitchens.com www.bright-kitchens.com
                brightkitchens.co.uk www.brightkitchens.co.uk;

    ssl_certificate     /etc/letsencrypt/live/aliases/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/aliases/privkey.pem;

    return 301 https://brightkitchens.com$request_uri;
}

The certificate needs all six names as Subject Alternative Names. With certbot that’s one command with six -d flags and --cert-name aliases.

If the aliases are on Cloudflare, you don’t need a server at all. Create a proxied dummy record (A @ 192.0.2.1 and the same for www) in each alias zone and add a Single Redirect Rule with the expression concat("https://brightkitchens.com", http.request.uri.path), status 301, query string preserved. Cloudflare handles the certificate on its edge. The details, plus Apache and testing with curl, are in our 301 redirect guide.

The primary domain should also have exactly one host variant. Decide whether www or the bare domain is the canonical one and redirect the other, otherwise you have five aliases plus an internal duplicate.

Which domain should be the primary?

Pick the one you print on invoices and say on the phone. In practice that’s often the shortest and the one already holding most of the backlinks. Check the Links report in Search Console for each verified domain before deciding. Switching the primary later is a full domain move, with all the recrawl time that brings.

Country endings add a wrinkle. A .co.uk is a strong signal for the UK; a .com is neutral. If you sell only in Britain, making the .co.uk primary is a defensible choice. If you sell internationally, the .com is usually the better hub, with country folders and hreflang. The trade-offs are in the country code vs .com comparison.

Merging two existing websites onto one domain

Sometimes the extra domain isn’t empty. Two brands merge, or a side project gets folded into the main site. That’s a site move, not an alias setup, and it needs a URL map: each old page redirects to its closest equivalent on the primary domain. Pages with no equivalent get a 404 or 410 instead of a blanket redirect to the homepage, which Google tends to treat like a soft 404.

Because the old domain changes completely, it’s also a case for the Change of Address tool in Search Console. For an alias that never had its own content, the tool adds nothing.

Do keyword domains pointing to the main site help?

This is the question behind a lot of these setups. Someone buys cheap-kitchens-london.co.uk hoping the keywords will rub off. They won’t. A redirect passes signals the redirecting URL already has, and a fresh registration has none. The keyword in the domain name of the redirect source isn’t something Google evaluates for the target. We’ve covered what keyword domains do and don’t do in the exact match domain article.

There are still good reasons to register extra names: brand protection, catching typos, keeping a former company name working, or reserving the .co.uk before a competitor does. Those are business reasons. Treat the cost that way.

What extra domains really cost

Each of these renews every year. Four domains at a fixed price is manageable; twenty “just in case” names add up and usually include several nobody would miss. Once a year, look at which aliases actually receive traffic in your server logs and let the rest expire, unless a brand reason says otherwise.

If you’re consolidating, it helps to have all names with one registrar. Check the .com pricing details for the primary, compare the rest on the full price overview, and see whether the typo variants of your brand are still free with a quick name check.