AgenCMS

Custom domains

This page explains the two ways your published site can be reached: the default subdomain you get automatically, and a custom domain you connect yourself. It also covers the URL options that control how your live pages are served.

How your site is served by default

Every website gets a default subdomain as soon as it exists, in the form your-slug.yourplatform.com, where your-slug is the website slug. You do not configure anything for this to work. As long as the website is published, that subdomain serves your live pages, posts, sitemap, and robots file.

Your slug comes from the Website slug field under General in website settings. If you change the slug, the default subdomain changes with it.

To reach settings, open the website workspace and go to /dashboard/websites/{website}/settings, then choose the section from the left navigation.

Connecting a custom domain

You can serve the same published site from your own domain instead of (or in addition to) the default subdomain.

  1. In website settings, select the Domains section.
  2. In Primary custom domain, enter your domain, for example www.example.com.
  3. Click Save settings.
  4. Point the domain at the platform with your DNS provider. Use the host the platform tells you to point to. Without correct DNS, the domain will not resolve.

Once the domain points to the platform and the website is published, requests to that host serve your site automatically.

Additional domains

If you want extra hosts (aliases) to serve the same site, add them under Additional domains. Enter one domain per line, for example:

example.com
shop.example.com

These behave the same as the primary custom domain: any request whose host matches one of them resolves to your published site.

What custom domains do and do not include

Be aware of what the dashboard actually does for you:

  • There is no DNS verification or automatic DNS setup in the dashboard. You enter the domain, save, and configure DNS yourself at your registrar.
  • There is no in-app SSL certificate management screen. Certificate issuance is handled by the platform infrastructure once your domain resolves correctly.
  • Saving a domain does not publish your site. The website must be published for any host to serve it. You can toggle this under General with the Publish / Unpublish control.

If a domain looks connected but pages do not load, the usual cause is DNS that has not propagated yet or is pointing at the wrong host.

URL and normalization options

The Domains section also controls how live URLs are normalized. These apply to whichever host serves your site:

  • Canonical base URL sets the absolute base used for canonical tags, the sitemap, and generated links, for example https://www.example.com. Set this to your preferred public address so search engines see one consistent URL.
  • WWW policy lets you force www, force the non-www version, or leave hosts as-is.
  • Trailing slash policy can preserve, add, or remove a trailing slash on URLs.
  • Force HTTPS redirects live traffic onto HTTPS.
  • Auto redirect on slug change creates a redirect automatically when a page or post URL moves, so old links keep working.

Click Save settings after changing any of these.

Choosing your public address

If you set a Canonical base URL or a Primary custom domain, that address becomes the public-facing base for your site's links and canonical tags. If you set neither, your site uses the default your-slug.yourplatform.com subdomain as its public address.

For a single, clean public identity, connect a custom domain and set the canonical base URL to match it.