How do I get my website onto my own domain instead of a builder's subdomain?

This page may contain affiliate links from which Blur Studio earns commissions.

A subdomain (yourbusiness.wegic.net, or the equivalent on any builder) works fine while you're testing, but it looks noticeably less credible on a real business card, invoice or Google listing than a domain with your own name on it. The good news is this isn't a hard technical problem anymore, it's a short, well-documented process on most modern site builders. Here's exactly what it involves on Wegic, an AI tool that builds and hosts your site from a chat description, which publishes the steps directly in its own help center rather than leaving you to guess.

Which plan do you actually need?

This is the part that trips people up before they even get to the technical steps: custom domain support on Wegic is gated to the Premium plan specifically. Starter, at $39.9 a month ($23.9 if you pay annually), does not include it, and your site stays on a wegic.net subdomain regardless of how you set things up. Premium runs $69.9 a month, or $41.9 a month if you commit to a year upfront ($502.8 total), and includes custom domain support along with unlimited visitors and more monthly credits (2,000 versus Starter's 600). If your whole reason for reading this is "I want my own domain," check which plan you're actually on before trying to follow the connection steps, since they simply won't work on Starter.

Step by step: connecting your domain

1. Buy the domain itself, if you haven't already, through any registrar: GoDaddy and Namecheap are the two most common, and price is fairly similar across mainstream options for a standard .com. This is separate from your Wegic subscription; you're paying the registrar directly, usually $10-20 a year for a standard domain.
2. Go to your workspace at wegic.ai/workspace and find the publish settings for your site.
3. Choose "Connect your own domain" under the Publish menu, and enter the domain name you bought.
4. Copy the DNS records Wegic gives you. As of this check, that's an A record pointing your root domain (the "@" entry) to the IP address 43.153.40.157, and a CNAME record pointing your "www" subdomain to a Wegic-provided address (something like xxxx.n2.wegic.app, specific to your account).
5. Add those records at your domain registrar, not inside Wegic. This means logging into wherever you bought the domain (GoDaddy, Namecheap, Cloudflare, Hostinger, Squarespace Domains, IONOS, Alibaba Cloud and Wix domains are all explicitly documented as supported registrars) and adding the A and CNAME records exactly as given. The documentation is specific on one point worth repeating: the CNAME must point to a domain, never an IP address directly.
6. Wait for DNS to propagate, which the documentation describes as controlled by the record's TTL (time to live) setting, and can take anywhere from a few minutes to over 24 hours depending on your registrar and existing settings.
7. Click Connect inside Wegic, then publish. The connection needs to be verified before your site actually serves from the new domain, so don't assume it's live just because you've added the records; confirm the connection step completed and republish.

What the documentation doesn't fully cover

SSL (the padlock, the "https" that makes a browser trust your site) isn't explicitly detailed in Wegic's own custom-domain documentation. Most modern site builders provision SSL automatically once a custom domain is connected and verified, and there's no indication Wegic works differently, but this is worth confirming directly with their support before you launch, rather than assuming, since a site without a working SSL certificate throws a visible security warning to every visitor. Fixing a "Not secure" warning with a free SSL certificate explains what that means.

What happens to your domain and site if you cancel your subscription also isn't spelled out in the documentation I could verify. Domains you've bought through a separate registrar stay yours regardless of what happens with Wegic, since that's a separate purchase, but confirm directly what happens to the connection, the published site, and any content if you ever downgrade or cancel, before you're relying on it for real business traffic. Who hosts your website and who fixes it when it goes down covers who is responsible.

Common mistakes people make with this exact process

• Adding the records at the wrong place. DNS records go at your domain registrar's dashboard, not inside Wegic's own interface. This is the single most common source of confusion, since the instructions reference both places in the same flow.
• Pointing the CNAME at an IP address. The documentation is explicit that the CNAME record must point to a domain name, never an IP address. Getting this backwards (or mixing up which record type goes where) is a common copy-paste mistake.
• Assuming propagation is instant. DNS changes can take minutes or up to a full day depending on TTL settings and your registrar. Don't panic and start re-entering records if it hasn't updated within the first hour; give it time before troubleshooting.
• Forgetting to click Connect and republish. Adding the DNS records correctly isn't the final step. The connection needs to be verified inside Wegic and the site republished before visitors actually land on the new domain.
• Not checking existing DNS records for conflicts. If your domain already has an A record or CNAME at the same entry points (common if you previously had email or another service configured), the new records can conflict with the old ones. Clear out anything that overlaps before adding Wegic's records. Pointing your domain at a new website without breaking email explains how to do that safely.

What I'd actually tell you

This process is genuinely more straightforward than most non-technical business owners expect, mostly because the documentation is specific rather than vague. The part that actually trips people up isn't the DNS records themselves, it's not realizing upfront that custom domains require the Premium plan, then being confused when the connection option simply isn't available on Starter. Check your plan before you start, and budget the domain purchase itself (a separate, small annual cost through your registrar) alongside the Wegic subscription when you're working out the real total cost. Getting a small business website without paying an agency covers the wider options.

If you're not confident reading a DNS dashboard, this is a reasonable five-minute task to hand to anyone technically comfortable rather than struggle through yourself, since getting a record slightly wrong is a common, easily fixed mistake rather than a sign you need a developer.

Budgeting the real total cost of owning your own domain

It's easy to see the Premium plan's $69.9 monthly figure (or $41.9 if paid annually) as the whole cost of having your own domain, when it's really two separate line items. The domain registration itself runs roughly $10-20 a year through most registrars for a standard .com, renewed annually regardless of what you do with Wegic. On top of that, moving from Starter to Premium to unlock custom domain support is itself a real cost increase, roughly $30 more a month on the monthly plan or about $18 more a month if you're paying annually, purely for the domain and unlimited-visitor features, not for any additional editing capacity beyond the extra credits that come with it. Add those together honestly before deciding whether the branded domain is worth it at your current stage, rather than treating the upgrade as a minor line-item change.

When to get help with this instead of doing it yourself

If you've followed the steps and your domain still isn't connecting after 24-48 hours, that's past the point of normal propagation delay and worth getting a second set of eyes on, since it usually means a record conflict or a typo rather than something you just need to wait out longer.

How I'd approach this

Connecting a domain to a site builder is a small enough task that I'll walk a client through it directly if they're stuck, rather than treating it as billable work on its own. Where I actually get involved is the bigger question behind it: whether a site builder with a custom domain is the right long-term home for the business, or whether it's time for a proper build that you own outright, with your own hosting and domain relationship, not dependent on a subscription staying active. Get in touch if you're not sure which side of that line you're on.