Ctrlk
Webstudio Home
For the complete documentation index, see llms.txt. This page is also available as Markdown.

🌐Publishing & custom domains

Learn how to connect a custom domain to your Project.

Many DNS providers do not allow adding a CNAME at the root/apex. If yours doesn’t, jump to this section for alternate options.

Pre-publish checks

Webstudio checks publishable pages before starting a cloud publish or static export. These checks detect broken Resource references and invalid HTML nesting that could make the generated site fail or behave unexpectedly.

  • Errors stop publishing until you resolve them.

  • Warnings appear immediately but do not prevent publishing.

When a finding identifies a component, choose Show element to close the publish dialog, open the affected page, select the instance, and scroll it into view. Fix the problem, then publish again. Draft pages are excluded because they are not part of the generated site.

Adding a custom domain

These steps will show you how to add a custom domain to your Project.

1. Add a new domain to your Project

Click "Publish" in the top bar, then “Add a new domain”.

Enter the domain or subdomain you want the site to be available at, for example, www.example.com or example.com.

After entering your domain, you will be provided with DNS records, which can be manually added to your DNS or automatically through Entri.

CNAME and TXT records for a new custom domain

2. Add the DNS records

Next, you need to add the DNS records to your DNS provider either manually or automatically.

Option 1: Manually add DNS records

You can configure your custom domain manually by adding the provided CNAME and TXT records to your DNS.

  1. Open your DNS provider

  2. Create a CNAME record

    1. Add a new record.

    2. Set the type to CNAME.

    3. Copy the Name and Value from Webstudio.

    4. Paste them into the corresponding fields in your DNS provider. Note that the DNS provider might label the Value as "Target" or "Content."

  3. Create a TXT record

    1. Add a new record.

    2. Set the type to TXT.

    3. Copy the Name and Value from Webstudio.

    4. Paste them into the corresponding fields in your DNS provider. Note that the DNS provider might label the Value as "Content".

Option 2: Automatically add DNS records with Entri

The Entri option makes configuring your domain extremely simple — no puzzling registrar UIs. You can do it without leaving Webstudio Builder in just a couple of clicks.

  1. Click “Configure automatically”.

  2. Click “Continue” on the Entri configurator. This process will analyze your root domain and detect your DNS settings.

  3. Click on the Authorize button to redirect you to your DNS provider site. Log in, if required, and approve the configuration.

  4. Return to Webstudio and complete the setup.

3. Verify and publish

Click "Check status" and once it's verified, republish your site.

Verification may take up to 24 hours but usually takes only a few minutes.

You must publish your site after the domain is verified, or else "Worker not found" will show on the site.

Keep the Publish dialog open to follow the build and deployment status. Resolve any reported error before trying again.

Once your site is live, you can visit it by clicking the open icon next to the green checkmark.

Publish to Staging

Publish dialog with a verified staging domain and Add a new domain, Export, and Publish actions

You can publish your Project to a separate domain for testing before going live by only checking your staging domain, which can be the default Project subdomain or a custom domain.

Every Project comes with a subdomain ending in "wstd.io". You can use this subdomain as your site’s staging environment. The domain is automatically no-indexed if you add a custom domain.

When publishing the site, optionally select the domain(s) you want to publish to. The workflow for testing/approval would be:

  1. Make changes in the Builder

  2. Open the publish dialog

  3. Ensure only your subdomain is checked

  4. Publish and share with your team/client

  5. Upon approval, reopen the publish dialog and check your live/production domain.

  6. Publish

Staging Password Protection

All staging sites are protected by password by default. This protection cannot be removed — it's a platform security measure to prevent bad actors from using Webstudio staging domains for phishing attacks impersonating other brands, which is illegal and can result in Webstudio domains being blocked.

To share your staging site:

  1. Open the publish dialog

  2. Copy the staging link — it already contains the login credentials embedded in the URL

  3. Share this link with your team or client — they'll be automatically authenticated without needing to enter credentials

Click on the staging domain section in the publish dialog to view the username and password separately if needed.

For public access without password protection, publish to a custom domain instead.

Standardizing on root or www using Cloudflare

Why would you want to do this? Standardizing your domain through Cloudflare is free, flexible, and easy to manage, while also delivering excellent performance.

These instructions show you how to standardize your site’s primary domain in Cloudflare by choosing either www or the root domain.

Note root domain is synonymous with apex, bare, and naked. An example is example.com.

  1. Choose whether you want to use www or your root domain

  2. Add your choice to Webstudio (e.g., www.example.com or example.com)

  3. Add the provided records to your DNS

  4. Redirect the domain you did not add to the domain you added by following the next sections.

1: Add a DNS record for the other domain

Cloudflare rules can’t apply to traffic that isn’t proxied through Cloudflare. Therefore, adding a DNS record for the domain you are not using is essential. Cloudflare offers an IP address for this exact use case.

Create an A record and point it to 192.0.2.1.

This address does not route traffic to an origin server but allows Cloudflare to apply rules, redirects, and Workers to incoming traffic. The equivalent IP address for an AAAA record is 100::. - Cloudflare

Next, choose one of the following options based on your preferred setup.

2a: Redirect root to www

If you choose www as your primary domain, be sure to redirect the root domain to it. For example, example.com should redirect to www.example.com.

Follow Cloudflare's guide to redirect your root domain to www.

2b: Redirect www to root

Although www is just a subdomain like xyz.example.com, many users still reference it out of habit. To ensure they reach your site, it’s best practice to redirect www to your root domain. To do this, make sure you’ve create the A record with 192.0.2.1 as described above, then follow Cloudflare’s guide to set up a Rule in the Cloudflare dashboard.

Exporting Projects

Webstudio can be self-hosted, putting you in control of your hosting, pricing, security, and compliance.

For more information about exporting and self-hosting, view Self-Hosting.

Removing a domain

To remove a domain from Webstudio:

  1. Click “Publish” in the top bar.

  2. Click your domain.

  3. Click “Remove domain”.

Domain issues

Below are common issues when adding custom domains and how to resolve them.

DNS provider doesn't allow CNAME flattening

While modern DNS providers like Cloudflare support using CNAME at the apex, such as example.com (aka CNAME flattening), others only allow using CNAME with a subdomain, such as www.example.com.

Providers that don't support CNAME flattening

This list is not comprehensive.

  • GoDaddy

  • Hostinger

  • Squarespace

  • DigitalOcean

  • Namecheap

  • IONOS

  • Hover

Option 1: Switch your DNS provider (without changing your domain registrar)

The easiest way to work around the CNAME limitation is to switch your DNS control over to a provider like Cloudflare. This process takes about 10 minutes and is free. Once you have migrated, you can use the original process detailed above to configure it.

You can move the DNS (where the DNS records are managed) without needing to move the registration (i.e. where the domain was purchased), though it may make sense to move both.

Why use Cloudflare

Especially useful for agencies managing multiple client domains:

  • Free plan is sufficient for most needs

  • Additional CDN features and enhanced security

  • Script injection capabilities (Facebook Pixel, Google Analytics)

  • Faster DNS and better performance

  • Easier management of multiple domains in one dashboard

Steps to migrate to Cloudflare

  1. Sign up for Cloudflare (free tier is sufficient)

  2. Add your site/domain

  3. Select the free plan

  4. Cloudflare will scan and import existing DNS records automatically (email MX records, etc.)

  5. Change nameservers at your registrar to the ones Cloudflare provides

  6. Wait 15-20 minutes for propagation

  7. Once verified, add Webstudio CNAME and TXT records in Cloudflare

DNS propagation typically takes 10-15 minutes, but can take up to 72 hours in rare cases depending on registrar and location.

Option 2: Publish your website on a www subdomain

Go back to Step 1, but this time, prefix your domain with www.

Video Tutorial

The above options are shown in the following video.

Publishing to a Subdomain

Subdomains are useful for marketing teams who want autonomy over landing pages (e.g., go.example.com) while keeping the main site separate.

To publish to a subdomain:

  1. Follow the same process as adding a custom domain

  2. Use the subdomain (e.g., go) as the CNAME name instead of @ or www

  3. Add the corresponding TXT record

Worker not found

You may see "Worker not Found" message when opening the site, like this:

Published site showing a Worker not found error

Worker not found is due to one of the following reasons:

  1. You haven't published your Project after adding a custom domain.

  2. You clicked on publish, but it is still in the process of deployment. It usually takes 1 minute to distribute your Project across the globe. Webstudio is utilizing Cloudflare's advanced Edge network.

  3. Your domain was not properly connected or you need to republish.

Adding a domain with a country code like .co.uk

Using a second-level domain (SLD) within a country code top-level domain (ccTLD) such as .co.uk is fully supported. However, the DNS records provided when adding a domain in the Builder are incorrect.

Here are the provided records and correct records when adding example.co.uk:

Record Type
Provided Value
Correct Value

CNAME

example

@

TXT

_webstudio_is.example

_webstudio_is

Related

PreviousShare links
NextCore Components

Last updated

Was this helpful?