Domain and security
Domain, DNS, and SSL for ecommerce: three launch essentials
Set up a custom domain, CNAME records, and HTTPS in the right order before customers or payment providers rely on your store.
Domain setup affects payment callbacks, search visibility, and buyer trust. Finish the domain and HTTPS checks before you turn on production payments.
Do the setup in this order
First make sure the default store address opens. Then submit the custom domain in store settings and create the CNAME record at the domain provider using the target shown in the admin area. Pick one preferred address, often www, and redirect the other one.
SSL acceptance checklist
- HTTP redirects to HTTPS.
- Browsers show no certificate warning.
- Homepage, product pages, checkout, and images have no mixed-content errors.
- The preferred domain is consistent across navigation and payment settings.
When the domain will not open
DNS changes take time. If the domain does not resolve, check the host and CNAME target before changing records again or issuing another certificate. Keep payment keys, private keys, and unredacted configuration screenshots out of public posts and support tickets.