Custom domains let visitors open your published site at your own hostname (for example www.yourbrand.com) instead of only the default Webster subdomain.
Before you start
- Publish your project at least once so Production has a live release (Publish).
- Open Project settings → Domains in the builder.
- Have access to your DNS provider (Cloudflare, IONOS, Namecheap, etc.).
Add a domain
- Enter the full hostname (for example
www.example.com). - Webster creates a pending binding and shows DNS instructions:
- CNAME — point your hostname to {slug}.websterai.de (your project slug on Webster hosting).
- TXT — add _webster-verify.{hostname} with the verification token Webster provides.
- Save DNS changes at your provider. Propagation can take a few minutes to 48 hours.
Verify
Click Verify domain in project settings after DNS records are in place.
- In local development, verification may succeed immediately for testing.
- In production, Webster checks DNS through the configured edge provider. If verification is not configured in your environment, the API returns a clear error without deleting your binding.
When verification succeeds, status moves to active and traffic can be routed to your site (TLS provisioning follows in a later release).
Remove a domain
Use Remove on the binding to delete it from the project. Update DNS at your provider if you no longer want the records.
Tips
- Use
wwwor the apex domain consistently — pick one canonical hostname for SEO. - Keep the Webster subdomain working during migration so you can roll back quickly.
- See also: Publish for slug and badge settings.