ESDomain editorial team · Reviewed 2 November 2026
Define the scope
Before registering the destination, establish whether you are changing only the address or also the content, host and platform. Separating those decisions makes problems easier to diagnose. Back up the site and list important pages. Include pages generating enquiries, sales or external links even if they are not shown in the main navigation.
Decide who will control the old domain and how long it will remain available. If keeping it, record its renewal alongside the new .es renewal. Review systems using complete URLs, including forms, images, sign-in flows and automatic messages. The destination name should be registered and prepared before visitors are sent to it.
Map the pages before launch
Create a small table of old URLs, new URLs and the intended outcome for each. A continuing service page should have an equivalent destination. Decide how retired content will be handled on the new website too. Make these decisions before launch day, when the team may already be busy checking access, forms and customer communication.
Configure permanent redirects at the host or application serving the website. Changing DNS alone does not redirect individual web pages. Test real examples, including deeper paths. Google’s migration documentation explains URL mapping and the Search Console steps. Use that documentation with your hosting team to select the mechanism supported by your particular website platform.
Review the destination as a visitor
Open the .es pages on a device without your administrator session. Check the certificate, navigation, forms and images. Review canonical URLs and the sitemap against the addresses you intend to publish. If the site has several language versions, test the links between them. Keep a written list of failures so the team can verify each correction.
Email deserves a separate plan. A website address change does not create mailboxes or move old messages. Decide whether existing email addresses will remain in use and coordinate changes with their provider. Test delivery and replies before telling customers to use a different address. Website publication and email readiness should each have their own acceptance checks.
Review after launch
After launch, review old paths, received enquiries and errors on the new site. Retain the URL map and configuration backups. Investigate the particular destination when a link fails. Repeatedly changing DNS can introduce unrelated problems when the actual fault is an incorrect page route or an application setting that needs a targeted correction.
Use Search Console and your existing reporting tools to follow the transition. Choosing .es does not guarantee search positions or eliminate migration fluctuations. Keep content maintained and fix observed errors. For a business heavily dependent on search traffic, involve the people responsible for its hosting and search operations before changing the public address.