Frequently asked questions

Yes, you can use Cloudflare Workers with Webstudio-hosted sites. Set your main domain's CNAME to 'proxied' in Cloudflare to enable Workers, while keeping subdomain CNAMEs (like those pointing to Webstudio) as 'DNS only'. This allows you to reverse-proxy different subdomains or paths through your Worker without creating double-proxy issues.

Patterns:

1. Main domain proxied -> Worker routes traffic to a Webstudio project subdomain
2. Worker maps /blog or /app path segments to a Webstudio project
3. Avoid chaining (nesting) a proxied CNAME behind another proxied CNAME

Only the domain terminating at the Worker should be orange-cloud (proxied); project CNAMEs stay DNS-only.

Webstudio requires CNAME records for custom domains. If your DNS provider converts CNAME to ALIAS for root domains (like Hostinger), this won't work because Webstudio only supports CNAME.

Solutions:

1. Use 'www' subdomain with CNAME pointing to Webstudio,
2. Move to a DNS provider that supports CNAME flattening (like Cloudflare),
3. For unsupported TLDs (.de domains), register a .com equivalent on Cloudflare and redirect. The 'www' approach is recommended if CNAME flattening isn't available.

While you can use any domain registrar, Cloudflare is recommended for DNS management because it supports CNAME flattening, which allows you to use root domains (without www) properly. Other registrars like Namecheap have limitations that can break email services and other domain-connected features.

403 Forbidden errors in Google Search Console are often caused by bot protection settings in Cloudflare. Check your Cloudflare account for bot protection features that might be blocking search engine crawlers. If you're using Cloudflare nameservers, ensure the security settings allow legitimate bot traffic. You can also manually trigger a crawl in Google Search Console to test if the issue is resolved after adjusting your Cloudflare settings.

If your domain shows as 'Active, but not published' and the publish button is grayed out, you likely need to add the required 'Built with Webstudio' badge to your site. On the free plan, you can use one custom domain but must include this badge on your website.

If your domain shows 'Active' but the publish button is greyed out, you likely need to add the required 'Built with Webstudio' badge to your site. For free accounts, this badge is mandatory when using custom domains. Add the badge component to your site, and the publish button should become available. Pro accounts can remove this badge requirement.

When your custom domain shows 'Active, but not published' with a grayed-out publish button, it's usually because you haven't added the required 'Built with Webstudio' badge to your website. In the free version, you can use one custom domain, but it must include the Webstudio badge. You need to manually add this badge component to your site before you can publish to a custom domain.

Your DNS provider likely lacks CNAME flattening at the apex. Adding 'www' ensures reliable CNAME mapping without breaking other records (email, etc.). To use the root cleanly, switch nameservers to a provider (e.g. Cloudflare) that supports flattening.

Root domain setup is non-standard and broken with some providers like Namecheap. It can break other services connected to your domain (like email). The solution is to use CNAME flattening by migrating your domain to Cloudflare nameservers, which properly supports root domain hosting and gives you additional options and protection.

If the publish button is disabled after adding a custom domain, check for error messages displayed in red text in the domain configuration dialog. Common issues include DNS record errors or domain verification problems. The publish button remains disabled until all domain configuration errors are resolved. Make sure your DNS records are properly configured and the domain status shows as 'Active' before publishing.