{"section":"tutorials","requestedLocale":"en","requestedSlug":"change-the-store-domain","locale":"en","slug":"change-the-store-domain","path":"docs/en/tutorials/account-management/accounts/change-the-store-domain.md","branch":"main","content":"Changing a store [domain](/en/docs/tutorials/configuring-the-store-domain) after the go-live requires careful attention to minimize SEO problems and ensure a seamless transition without impacting the customer experience.\n\nLearn more about the complete process for changing your domain on VTEX in the following sections:\n\n1. [Prerequisites](#prerequisites)  \n2. [Setting up the new domain](#setting-up-the-new-domain)  \n3. [Deleting the previous domain](#deleting-the-previous-domain)  \n4. [Redirecting the previous domain](#redirecting-the-previous-domain)  \n\n## Prerequisites\n\nBefore you begin, make sure that:\n\n* The new domain is registered and accessible.  \n*\tYou have access to the domain DNS provider.\n\n## Setting up the new domain\n\nFollow the steps below to change your domain:\n\n1. Create a new VTEX Admin host by following the instructions in [Registering a new host](/en/docs/tutorials/configuring-the-store-domain#registering-a-new-host). At this stage, the DNS of the new domain must not yet be pointed to VTEX.  \n2. In the VTEX Admin, check the Checkout settings in **Store Settings > Storefront > Checkout**, as described in the [Configure template in SmartCheckout](/en/docs/tutorials/configure-template-in-smartcheckout-update) article.  \n   This step is essential for the Checkout to keep working after the change.  \n   You must check if the sites configured are associated with the account listed in **Account Settings > Accounts**. See the [Account management](/en/docs/tutorials/account-management) article for more details.  \n3. If your store uses [VTEX IO - Store Framework](https://developers.vtex.com/docs/guides/storefront-implementation) or [FastStore](https://developers.vtex.com/docs/guides/faststore/docs-what-is-faststore), contact [VTEX Support](https://supporticket.vtex.com/support) and request internal pointing, informing them of the new domain. Learn more about [internal pointing](/en/tracks/go-live-your-store--4Ns5FxIiksmjsdX2yOTduM/7sM5IMx02zaHvAFTm0OxiJ#requesting-io-pointing).  \n   Once the ticket has been opened, the support team has up to three business days to analyze the settings and complete the pointing process.  \n4. Point the DNS to the VTEX CDN. To do this, follow the instructions in the [Go-live](/en/docs/tracks/go-live) guide.\n\n## Deleting the previous domain\n\nAfter the transition period, we recommend deactivating the old domain to ensure all customers use the new address and avoid confusion.\n\nYou can keep both domains (the old and the new) running simultaneously during the transition period, but be careful to avoid problems such as:\n\n* Confusing customers about which is the official domain can negatively affect trust and sales.\n* Negatively impacting SEO, as search engines may interpret domains as competing.\n\nAfter confirming the new host's DNS propagation and internal pointing, delete the old hosts and keep only the new one:\n\n1. In the top bar of the VTEX Admin, click your profile avatar, indicated by the initial letter of your email address.  \n2. Click the **Account settings** button.  \n3. Click **Account**.  \n4. Click the **Stores** tab.  \n5. In the row of the store where you want to delete the host, click the actions button ⁝ and then click `Edit`.  \n6. In the row of the old host, click the actions button ⁝ and then click `Delete`.  \n\n## Redirecting the previous domain\n\nTo ensure that all accesses to the previous domain are directed to the new domain, follow the instructions below:\n\n* Set up an HTTP 302 redirect, instructing browsers to forward requests to the new domain.  \n* We recommend using tools such as [redirhub.com](https://www.redirhub.com/) and [redirect.center](https://redirect.center) to create the redirection.  \n* Avoid using CNAME for redirection in the DNS dashboard, as this setting doesn't guarantee proper redirection.\n\n> ⚠️ The first few visits to the new domain are often slower than expected due to the initial cache creation. This impact is temporary and normalizes over time."}