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.

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.

Weglot doesn't work well with Webstudio because Webstudio sites are Single Page Applications (SPAs). SPAs are faster than traditional websites because they don't reload the entire page on each navigation—instead, they dynamically update content in the browser.

Weglot struggles with SPAs for several reasons:

1. Content detection timing: Weglot scans the page HTML on load, but SPA content is rendered dynamically by JavaScript after the initial page load, so Weglot may miss content entirely.

2. Navigation without page reloads: When you navigate between pages in an SPA, the browser doesn't perform a full page reload. Weglot relies on page loads to detect and translate new content, so navigating to a new page won't trigger translation.

3. Dynamic content updates: Even with Weglot's "Dynamic" setting (which watches for DOM changes using a body selector), it can cause performance issues and may not catch all content changes reliably.

4. DNS/proxy complexity: Weglot typically works by proxying your site through their servers, which adds complexity and potential points of failure for SPA architectures.

For multilingual Webstudio sites, consider using a headless CMS with built-in i18n support (use our CMS Finder to find one that fits your needs) and fetching translated content based on language parameters in your URLs.