Connecting your own domain
Besides the free your-shop.wparts.com address you can connect your own domain - for example your-shop.com or shop.example.com. Both addresses work in parallel: the free address is not going anywhere. Each site can have one custom domain.
Step 1. If you don't have a domain yet, buy one from any registrar (Namecheap, GoDaddy, etc.). You only pay the registrar for the domain itself - connecting it to WParts is free.
Step 2. In the builder, on the “Publish” step (or in site management), find the “Custom domain” block and add the exact domain name - without http://, without a path and without a port: just shop.example.com.
Step 3. In your registrar's DNS management panel, set up the record. For a subdomain (shop.example.com): create a CNAME record with the name shop and the value dns.wparts.com, and remove any conflicting A/AAAA/CNAME records for that name. For an apex domain (example.com): create an ALIAS/ANAME record or enable CNAME flattening to dns.wparts.com; if your DNS provider does not support that, connect www.example.com as a subdomain instead, or ask our support for the A/AAAA fallback option.
Step 4. If you use Cloudflare or a similar proxy, switch the record to “DNS only” mode (grey cloud) and keep it in that mode permanently - including during SSL certificate renewal.
Step 5. Wait for DNS to propagate - usually 5–30 minutes, sometimes up to 24–48 hours. Then click “Verify” next to the domain. Verification statuses: “Pending” - the record is not visible yet, wait and retry; “Verified” - everything is set up correctly; “Failed” - the record was not found, check your DNS settings. Once the domain is verified, the SSL certificate (HTTPS) is issued automatically: “Pending” → “Provisioning” → “Active”, usually within a few minutes. Your site on the custom domain starts working when the SSL status becomes “Active”.
Why “DNS only” matters: the certificate for your domain is issued by our edge server, and the DNS record must point exactly at it. An enabled proxy substitutes its own addresses for the real ones, so verification and certificate issuance fail. This is a limitation of our connection scheme, not of proxies in general.