The perfect domain is just a click away: find your domain name →

Most AI builders publish your project to a temporary platform URL first. To give your site a permanent, branded address, you’ll need to register a domain and connect it to your project. The process usually involves a few DNS changes, a verification check and some patience.
Secure your perfect domain in just a few clicks with Wix. Get everything you need in one place: business email, reliable hosting, SSL protection and optional privacy. With 24/7 support, getting your site live is simple and worry-free.
TL;DR: connecting a custom domain to an AI-built website
To connect a custom domain to an AI website builder, add the domain in your builder's settings and then update the DNS records or nameservers at your registrar. Once the changes propagate and your builder verifies the connection, visitors reach your site at your own branded address.
You'll learn:
What a custom domain changes for an AI-built site
What to check before you touch any DNS settings
How to connect your domain step by step
Nameservers vs DNS records (and A record vs CNAME)
How long DNS propagation takes
How to fix the most common connection errors
What a custom domain does for an AI-built website
Most AI website builders first publish your project to a temporary platform URL, such as yourproject.builder-name.app. That's useful for testing, but it means your website address is tied to the platform you're using.
A custom domain gives your site its own permanent address, such as yourbrand.com. You register and control the domain yourself, so you can keep using it even if you rebuild your website or switch to another AI builder.
Why your website needs its own domain
A custom domain makes your website easier to recognize, remember and share. It looks more professional on a business card, in an email signature or in a social media bio. You can also set up a matching business email, such as hello@yourbrand.com, using your domain.
It's also worth understanding that your domain and website are two separate things. Your domain is the web address, while hosting is where your website's files are stored and served to visitors. Your AI builder handles the hosting, and your DNS settings connect your domain to it.
Domains are becoming part of the launch process, too. According to the Wix State of Websites 2026 report, 69% of Wix sites with a custom domain connected it on or before launch day in 2025, up from 47% in 2022. More site owners are setting up their domain as part of launching rather than waiting until later.
What happens when you switch to a custom domain?
Connecting a custom domain doesn't change your website. Your pages, content and settings stay as they are. You're simply giving visitors a new address to reach it.
If you've already shared your temporary platform URL, check if your AI builder supports redirecting it to your new domain. If it doesn't, update any links you've shared so visitors can find your site at its new address.
Learn more:
What you need before you connect a custom domain
Most of the friction in this process comes from skipping prep. Before you open any DNS settings, line up these five things.
A plan that supports custom domains. Many AI builders only allow custom domains on paid plans, so check your platform's requirements first. If the connect option is grayed out, this is usually why.
A published site. Publish first and check the site on its temporary URL, so you know it works before you add a domain to the mix.
Access to your registrar. You'll need to log in wherever the domain is registered to change its settings. Not sure where that is? A WHOIS lookup shows the registrar for any domain.
A copy of your current DNS records. If the domain already points to another website or runs email, screenshot or export every existing record before you change anything. Pointing the domain at a new site disconnects the old one, while email and other services keep working as long as their records stay in place.
One thing worth knowing: connecting a domain doesn't mean you have to transfer it. You can keep the domain registered with its current provider and point it to your AI-built site through its DNS settings. Transferring is a separate process that moves the registration itself to another provider.
How to connect a custom domain to an AI-built website
The buttons differ from one builder to the next, and so do the exact records each platform asks for. The overall sequence is similar almost everywhere, though.
01. Buy a domain or use one you already own
If you don't have a domain yet, run a domain name search and register a domain name you like. Buying it from your website platform is often the simplest route because the connection can be set up for you. If you already own one, find out which registrar holds it and make sure you can log in.
02. Add the domain in your builder's settings
Open your site's domain or publishing settings and look for an option like "Connect a domain" or "Add custom domain." Enter the domain exactly as you registered it, without www or https. Some platforms then ask you to verify that you control the domain, usually by adding a TXT record at your registrar.
03. Choose nameservers or DNS records
Most builders offer two ways to connect. Changing nameservers hands all DNS management to the builder, which is easier to maintain. Adding DNS records keeps DNS at your registrar, which helps if you already run email or other services on the domain.
04. Add the DNS records your builder provides
A typical setup is an A record for the root domain (often shown as @) that points to an IP address, plus a CNAME record for www that points to a hostname. Some builders ask for multiple A records, a TXT record for verification or a flattened CNAME on the root instead. Copy the exact values from your builder's domain settings rather than generic instructions written for another platform.
Then check for existing A, AAAA or CNAME records on the same hosts that conflict with those values. Replace or remove only the conflicting records, following your builder's instructions, and leave records for other services alone.
05. Wait for DNS propagation
DNS changes don't apply everywhere at once. Many connections start working within a few hours, but it can take up to 48 hours (occasionally longer) for every network to see the update. During that window your site may load for some visitors and not others, which is normal.
06. Confirm SSL and pick your main address
Once your builder verifies the domain, it typically issues a free SSL certificate so your site loads over HTTPS. Certificate issuance can trail the DNS update by a few hours. Check that both yourbrand.com and www.yourbrand.com open the site, then set one as the primary address and redirect the other to it.
Worth knowing: changing nameservers moves all DNS management to the new provider, and your existing records don't come along automatically. Before you switch, copy every record you still need, including MX, TXT, SPF, DKIM and DMARC records for email, verification records and records for other subdomains. Recreate them with the new provider so email and connected services keep running.
Found the perfect name for your business? Register your domain before someone else does.
Choosing between nameservers and DNS records
Nameservers decide which provider answers DNS questions for your domain. When you point them to your builder, it manages every record and you handle everything from one dashboard. That's the cleanest option when the domain only serves this website.
Adding DNS records leaves the nameservers where they are and only sends web traffic to your site. Go this route if the domain already runs business email, a separate app or verification records you don't want to rebuild. The tradeoff is that you troubleshoot DNS at the registrar instead of inside your builder.
A record vs CNAME in plain terms
Your domain can have several parts. yourbrand.com is the root domain, www.yourbrand.com is the www version and names like shop.yourbrand.com or app.yourbrand.com are subdomains. Each one can point somewhere different, so yourbrand.com could load your main website while app.yourbrand.com points to an AI-built app on another platform.
An A record maps a name to an IPv4 address (an AAAA record does the same for IPv6), which is why it's the usual choice for the root domain. A CNAME maps one name to another name instead of an IP, which makes it the standard choice for www and other subdomains. A name with a CNAME generally can't hold other ordinary records, and because the root domain always carries records like its nameservers, it usually can't use a plain CNAME.
One thing worth knowing: some registrars offer ALIAS or flattened CNAME records as a workaround for the root domain. They work, but only use them if your builder's instructions mention them. Otherwise stick with the exact record types it lists.
How long DNS propagation takes
Propagation is the time it takes for DNS resolvers around the world to stop using their cached copy of your old settings and pick up the new ones. TTL (time to live) sets how long a resolver may cache a record before checking for an update. Lowering a TTL doesn't clear copies that were already cached under the old value, so some networks keep using the previous information until their copy expires.
Record changes often show up within an hour or two. Nameserver changes usually take longer because they also update the domain's delegation information, and 24 to 48 hours is a practical guideline rather than a guaranteed limit. A free DNS checker tool lets you follow along by showing what servers in different countries currently see for your domain.
Worth knowing: if the site loads on your phone's mobile data but not on your laptop, you may be seeing a local or network-specific cache, a VPN or a different internet provider's resolver. Try a private window or another network before you change any records.
Why your custom domain isn't working (and how to fix it)
Most connection problems trace back to the same handful of causes. If your domain is still misbehaving, work through these.
01. The domain is stuck on verifying
This usually means a record doesn't match what your builder expects. Compare every value against the builder's domain settings, look for a leftover A, AAAA or CNAME record on the same host that conflicts with the new one and check for typos, such as a missing digit in an IP address. Replace only the records that conflict with your builder's instructions.
02. The browser says your connection isn't private
This warning appears when the SSL certificate hasn't been issued yet or doesn't cover the version of the address you're visiting. The platform has to verify the domain before it can issue a certificate, so allow time for both DNS propagation and certificate issuance. If only the www version shows the error, check that its DNS record matches your builder's instructions.
03. The root domain works but www doesn't (or the reverse)
You've likely set up only one of the two records. Add the missing record using the values your builder provides, then choose a primary version so visitors always land on the same address.
04. A DNS proxy is blocking the connection
Some DNS providers can route traffic through their own proxy servers. If your hosting platform doesn't support DNS proxies, the proxy can block domain verification or SSL and sometimes causes redirect loops. Temporarily set the affected records to DNS only, then try verifying the domain again.
05. DNSSEC is blocking the connection
DNSSEC adds a security layer to DNS lookups, but it can interfere with resolution when its settings don't match your current DNS provider. If your records look right and the domain still won't connect, check if DNSSEC is enabled at your registrar and follow your platform's instructions before you change it.
06. Email stopped working after the switch
If you changed nameservers, your MX records and email authentication records (SPF, DKIM and DMARC) probably didn't come along. Add them back in your new DNS settings using the values from your email provider, and mail should start flowing again once they propagate.
07. The domain still isn't working after 48 hours
Work through this checklist before you change anything else.
Confirm the domain is active and hasn't expired.
Check that the domain uses the nameservers your setup requires.
Compare your A, CNAME and TXT records with the values in your builder.
Review your DNSSEC and proxy settings.
Use a DNS checker to see which records have updated.
Contact your registrar about registration or nameserver issues, or your website platform if verification is still stuck.
One thing worth knowing: if you're unsure which service a record belongs to, find out before you delete it. A record that looks unused might be verifying your email or connecting a subdomain to another tool.
Read more: Web host vs domain registrar
What to do after your domain goes live
Once the domain is live, a few quick updates keep visitors and search engines on the right address.
If your AI builder supports redirects from its temporary URL, send those visitors to your custom domain. If it doesn't, update the links you've already shared.
Submit your new sitemap in Google Search Console to help Google discover your updated URLs, then keep an eye on indexing.
Update any login, payment or form settings that still reference the old URL, especially on AI-built apps with sign-in.
Set up an email address on the domain if you want your messages to match your site.
Swap the new address into your social profiles, ads and email signature.
Worth knowing: search engines treat your custom domain as a new address. Permanent redirects pass along most of the value from the old URL when your platform offers them, but expect visibility to fluctuate for a few weeks while search engines catch up.
How to connect a custom domain to a Wix AI website
If you build with Wix's AI website generator, you can register a domain from the same account. A domain purchased through Wix can connect to your Wix site automatically, so you don't need to copy DNS records between tabs. If you use a separate business email service, make sure its MX records are set up too.
Already own a domain somewhere else? You don't need to transfer it. You can connect it by nameservers, which Wix recommends because it then hosts your DNS records and you manage them from your Wix account.
You can also connect by pointing, which keeps DNS management with your current provider and suits domains with several records you'd rather not recreate. For some domain providers, Wix can connect the domain automatically after you sign in to your provider account.
01. Upgrade your site. Connecting a domain requires a site plan, and select yearly plans include a voucher for a free domain for the first year.
02. Open Domains in your Wix account. Choose to connect a domain you already own or buy a new one.
03. Pick your site and enter the domain. Choose the site you want to connect and type the domain exactly as it's registered.
04. Follow the on-screen steps. When automatic connection is available for your provider, Wix handles the records for you. Otherwise it shows the exact nameservers or records to add. The options you see can vary by account and domain provider.
05. Give it time to propagate. It can take up to 48 hours for your domain to work worldwide and for SSL to be issued, so check back before you start troubleshooting.
Expert tip from Adi Avraham, Senior SEO growth at Wix:
"Using AI doesn’t mean you lose control. Wix’s AI features just speed up the basics so you can focus on the creative touches that make your site unique."
Beyond the connection itself, Wix sites come with a free SSL certificate, and Wix offers tools for DNS management and domain security. Wix also offers WHOIS privacy as an option you can add, with availability depending on the domain extension, and 24/7 support is there if a record won't cooperate.
Worth knowing: Wix doesn't support DNS proxies when you connect a domain. If your domain currently sits behind one, turn the proxy off before you connect so verification and propagation can finish.
You can register a domain directly on the Wix website builder and add WHOIS privacy and domain security for extra protection.
Custom domains for AI-built websites FAQ:
Can I connect a custom domain on a free plan?
It depends on the platform, but many AI website builders, Wix included, require a paid plan before you can connect a custom domain. Free plans keep your site on the platform's temporary URL, which works for testing but not for launch.
What's the difference between connecting and transferring a domain?
Connecting points a domain to your website while it stays registered with its current provider. Transferring moves the registration itself, including renewals and billing, to a new provider. You can connect a domain without ever transferring it.
What happens to my old website if I connect the domain to a new one?
Once you change the domain's website records, visitors stop reaching the old site at that address. Email and other services keep working as long as you preserve their DNS records. Back up your existing records before you make any changes.
How long does it take to connect a custom domain to an AI website?
Most domain connections start working within a few hours, but DNS changes can take up to 48 hours to propagate worldwide. The timing depends on DNS caching and your domain provider. Your builder may also need extra time to issue an SSL certificate.
Do I need to buy an SSL certificate?
In most cases no. Most AI builders issue a free SSL certificate once they verify your domain. If HTTPS still doesn't work after a day or two, check that both the root and www records match your builder's instructions.
Will my SEO carry over from the old platform URL?
Some of it can if your old platform supports permanent redirects from its temporary URL to your new domain. Expect search visibility to fluctuate for a while as search engines recrawl your pages. Submitting your new sitemap in Google Search Console helps Google discover the updated URLs.


























