Background of the issue:
I have a bilingual website with the main language as German on the domain hidden link, and it is translated into English in the hidden link directory. I want to change the type of translation hosting to a new hidden link domain for the English version.
Symptoms:
The provider cannot understand the instructions I sent regarding changing the translation hosting to a new domain.
Questions:
Do I need to make an English-language copy of the site on the hosting and link it to hidden link domain?
Can I just direct the IP of the hidden link domain to hidden link
Thank you, I started with this very instruction you sent and sent it to the IONOS provider. But their response was that it was impossible.
I set the IP address in the A-record and AAAA record for the @ and www of the example.com domain myself, pointing to the domain example.de. But this is still unsuccessful (less than 72 hours have passed).
When I repeatedly contacted support, they suggested buying a new hosting, making a copy of the site, and linking it through canonical links.
Your instructions do not mention a duplicate site, so this does not match what my provider is telling me.
I really need to clarify this point, because the site owner is already ready to buy a new hosting package.
Unfortunately, I’m not familiar with how the IONOS hosting provider operates. To set up a second domain locally, I would typically point the second domain to the local server and configure it as an alias in the server settings. This works because the main idea is to direct both domains to the same installation.
If you duplicate your site, you will end up with two separate, unconnected sites. This means that any translations or changes you make on one site will not appear on the duplicated site, which is a separate installation.
I recommend deactivating the "Validate on save" option, entering your second domain, saving your changes, and then testing the domain to see if it works. Sometimes, the validation message can be a false positive. After translating the page, check if you can access it using your secondary domain. If it doesn't work, your second domain is not configured correctly.