You would want it to be noindexed if the only content is your indexed domain where the 'wrong' domain version points to. I would look at how the rewrite/redirect is done - is it 301 or 302? I understand that it is not uncommon to buy up multi type-in/fat-finger possibilities so your situation is not unique. Without content it cannot be crawled so you would want to ensure it is a 301/permanent option for as long as you own the .com domain. It might to safe to assume but it doesn't hurt to check.

Many thanks!

It seems "too easy" to set up (if that makes sense). It gives me an option to direct the domain to any site (just to confirm - these are just domain names - nothing is hosted with / on them). I went to do it for the .com domain (particularly as this is the one most people type in error), but wanted to double check with people here....I'd be lost without the advice from this site :-)

Double-check: When you say �redirect�, do you mean a 300-class response (should be 301 but might be 302), or do you mean something on the DNS level where the identical content is served at more than one URL?

If it�s a redirect, a much more important question is: redirect to what? Does everything get sent to https://example.uk/ (root), or is it a page-for-page redirect?

Hi Lucy!

the options for the redirect are shown as:

- Permanent (301)
- Temporary (302)
- Forward with masking

It then shows this:

When user goes to:
example.com

They'll be redirected to:
https://www.example.net/

But, again, does that mean root or page-for-page? If the control panel isn't clear, try it yourself by requesting some interior pages and seeing where you end up. If it turns out to be a global redirect to the root, don't do it.

It might be safer to do it yourself with a minimalist htaccess along the lines of

RedirectMatch Permanent (.+) https://www.example.net$1

(Ordinarily we'd do it in mod_rewrite but since there's just the one line, this is more efficient. If I�m reading Apache docs correctly, mod_alias starts everything with a / slash.) Yes, you can do this even if this site has no other content; you�re simply grabbing all requests and redirecting them.

Admittedly, the chance of some human typing in
https://example.com/full-name-of-page
by mistake for
https://example.net/full-name-of-page
are slim. But still...