Domains
Manage domains in Autonnel: add hosts, set the fallback default, give each domain its own branding, email sender, storage and noindex switch, plus DNS and TLS.
Autonnel uses a multi-domain model: each domain is bound to your deployment and there is no intermediate “site” container. You manage domains from Pages → Domains (/pages?tab=domains). The old Settings → Domains address redirects there. The list shows each domain’s status, page count and From address; click a host (or Settings) to open the domain’s own page, /pages/domains/<id>, with the tabs Pages, Branding, Email, Storage, Payment and Custom code. Adding, deleting, setting the fallback default, the noindex switch and the Branding, Email, Storage and Custom code tabs need the Domains settings permission; the Pages tab needs the Pages permission. A user with only one of the two sees only the matching tabs.
Pages can only be created while at least one domain exists. Without a domain, Create page is disabled, and creating or copying a page or creating a funnel (which creates its default pages) is refused with Add a domain under Pages > Domains before creating pages, also through the API and MCP. The SaaS version always has the workspace subdomain.
A page is served only on the domains it is attached to. See Pages - multi-domain.
Adding a domain
- Open Pages → Domains.
- Click Add domain.
- Paste the hostname, for example
shop.example.com. A pasted URL such ashttps://shop.example.com/landingis reduced to its hostname. A host that serves the admin (it matchesADMIN_DOMAIN) is refused, since binding it would hide its storefront behind the login page. - Click Save.
The new domain row is created with isPrimary: false unless it is the first domain on the deployment, in which case it becomes the fallback default automatically. Only the first domain inherits the pages, custom code and logo that existed before domains; every later domain starts empty, because it is a new brand. Attach pages to it from each page’s Settings, and open it to set its brand.
Fallback default domain
Exactly one domain in the deployment is the fallback default (isPrimary: true in the API). Other domains are not redirected; each serves the pages attached to it. The fallback default domain is the store URL in emails when a sale’s own domain is unknown.
To change the fallback default domain, click Set as fallback default on its row and confirm. The previous one is automatically demoted. The fallback default domain is the brand used when no other domain applies: new pages attach to it by default, admin alerts carry its store name and are sent through its email provider, and emails for orders whose domain was removed use its brand. Each domain keeps its own store name, logo, favicon, sender and custom code.
While other domains exist, the fallback default domain cannot be removed: make another domain the fallback default first.
Email and branding per domain
Each domain is its own brand. Storefront pages on the domain, and the order and recall emails for sales on it, use that domain’s values. Store name, logo, favicon, time zone and the per-domain noindex switch are on the domain’s Branding tab; the From email, From name and Reply-To are on its Email tab, next to the sending provider:
| Field | Used for |
|---|---|
| Store name | Storefront store name, {{storeName}} in email templates, and the From name when From name is empty. Empty uses the domain’s host as the name |
| Logo URL | {{storeLogo}} in email templates (must be https://) |
| Favicon URL | The storefront favicon and home-screen icon (must be https://) |
| From email | The From address for emails about sales on this domain |
| From name | The display name next to the From address. Empty uses the store name |
| Reply-To | Where customer replies go |
| Time zone | IANA zone (for example Europe/Berlin) for dates in this brand’s emails; empty uses the site time zone |
| Discourage search engines on this domain | Follows the site-wide switch until you set it; then this domain’s own value wins (see below) |
Logo and favicon can be pasted as URLs or uploaded with Upload logo / Upload favicon. Uploads go to the bucket configured in Settings → Storage and need an https:// URL: set the static domain there, or leave it blank on a fallback default domain with a root domain of its own, which uses static.<root domain>. On a fallback default domain such as *.workers.dev or an IP address the upload is rejected until a static domain is set. The favicon is served as uploaded (PNG, ICO, SVG or WebP, up to 1 MB); browsers scale it, so a square PNG of 512×512 works everywhere.
Storage per domain
The domain’s Storage tab (Domains settings permission) sets:
- Static subdomain: overrides the global one for this domain. Enter a bare label (
cdn), a full host or a URL. When neither the domain nor Settings → Storage sets one, the default isstatic, so asset URLs usestatic.<root domain>. - Use separate storage for this domain: this domain’s own S3 endpoint, bucket and keys, instead of the global bucket. Saving uploads a test file and fetches it back through the static URL first, so a domain with its own storage needs a static subdomain that resolves. The secret key is stored like the global one and shown masked; leave the masked value to keep it.
Every page with domains has one default domain: the current one, else the fallback default domain, else the earliest attached. It is chosen again when the default is detached or its domain is removed. Uploads made for a page go to its default domain’s storage and use that domain’s static base. Asset URLs are not rewritten per host, and changing the default does not move existing assets; copy them to the new bucket yourself if you need to.
Payment per domain
The domain’s Payment tab has one row per provider: pick an account (created under Payment) or Not bound, plus that provider’s binding fields (PhotonPay: Site ID, required). Binding needs the Payment settings permission; with only the Domains permission the tab is read-only.
- A domain with nothing bound shows
This domain cannot take payments until an account is bound., and the domains list shows aNo payment accountbadge. - An unbound domain cannot check out (409
no payment account bound to this domain); there is no fallback to another domain. - Checkout offers only the providers bound to the domain being visited.
See Payments overview.
Maintenance per domain
The domain’s Maintenance tab (needs the settings.maintenance permission) takes just that domain offline: its storefront pages and funnel steps answer 503 with a “Site under maintenance” page and the optional message. Other domains and the admin keep working, and APIs (checkout callbacks, payment webhooks, the media proxy) stay reachable. Set an optional bypass password (at least 8 characters) and visitors who enter it on the maintenance page get a 24-hour cookie for that domain only; changing or clearing the password signs them all out. The domain page shows a Maintenance on badge while it is active.
Custom code
Each domain also has its own Custom code (pixels, analytics tags, custom HTML/JS) on its Custom code tab. Scripts run only on that domain. See Domain custom code.
Sending provider
The same tab holds the domain’s Sending provider (Cloudflare Email, Resend or Amazon SES) and a Send test button. All of these settings can also be read and changed through the external API. See Email sending.
How the brand is chosen
- A storefront page uses the domain it is visited on. A host that is not bound uses the fallback default domain.
- An order remembers the domain its checkout was submitted on. Receipt, shipping, delivery and refund emails for that order, including Resend confirmation email on the order page, use that domain’s values, and
{{storeUrl}}points at it. - A recall email uses the domain the buyer checked out on, and sends the buyer back there.
- Orders placed before this setting existed, and orders on a domain that is no longer bound, use the fallback default domain.
Logo and favicon are never borrowed from another domain: a domain without its own shows none, so one brand never shows another brand’s assets. A domain without a store name is named after its host, for example shop.example.com, in the storefront, in emails and in payment descriptors.
Each domain sends through its own provider with its own From name and Reply-To, so replies never land in another brand’s mailbox. Every From domain must be verified with the provider chosen for it (for Cloudflare Email, onboard each sending domain under Email Service in that Cloudflare account).
The built-in email designs show the store name but not the logo. To show a per-domain logo, add {{storeLogo}} to your templates in Settings → Email Templates.
Reports per domain
With two or more domains, Overview, Analytics, Interest and Ads show a domain select next to their other filters (it is hidden with a single domain). Orders count by the domain their checkout was submitted on, visits by the host they happened on, and funnels by the domains their pages are attached to. Ad spend that cannot be tied to one funnel on the selected domain is left out and shown in a note with its amount, so it is never silently mixed into one brand. Revenue is never added across currencies: each figure shows the currency with the most orders, and other currencies are listed beside it unconverted. The orders list, its CSV export and the email log show each order’s domain; see Orders.
Search engine indexing
Pages → Domains has a site-wide Discourage search engines from indexing all domains switch. Turn it on while a funnel is being built, for staging deployments, or for paid-traffic-only offers you do not want surfacing in organic search.
When it is on, every bound domain:
- serves a blanket
User-agent: */Disallow: /at/robots.txt - returns an
X-Robots-Tag: noindex, nofollowheader on every storefront response - renders
<meta name="robots" content="noindex, nofollow">in the page head
The header and meta tag matter: robots.txt only asks crawlers not to fetch a URL, so a page linked from an external site can still end up in the index from the link alone. The noindex directive is what actually keeps it out.
The site-wide switch is the default for every domain. Each domain’s Branding tab has Discourage search engines on this domain: until you change it, it shows the site-wide value faded and follows that switch. Toggling it gives the domain its own value, shown solid, which wins over the site-wide switch in both directions: turn it on to hide only a staging domain while the rest are indexed, or off to keep one brand indexed while the site-wide switch hides the others. Use site-wide setting clears the domain’s own value. Rows of hidden domains show a noindex badge. Unbound hosts follow the site-wide switch. The admin dashboard is never crawlable regardless of these settings - its /robots.txt always disallows everything.
Honoring these directives is up to each crawler. Well-behaved engines (Google, Bing) respect them; scrapers may not. Do not use this as an access control - use the domain’s Maintenance tab for that.
DNS configuration
Autonnel does not manage DNS. You must point your domain to your deployment yourself.
For most hosting setups, add a CNAME record:
shop.example.com. CNAME your-autonnel-deployment.example.com.
If your hosting provider gives you an IP address rather than a hostname, use an A record instead.
After DNS propagates (typically a few minutes to a few hours depending on your TTL), the domain becomes live. There is no verification step in the OSS version.
TLS / HTTPS
Autonnel does not issue TLS certificates. You are responsible for terminating HTTPS at your infrastructure layer. Common approaches:
- Cloudflare proxy — set the DNS record to proxied (orange cloud) and Cloudflare issues a certificate automatically.
- Hosting provider cert manager — platforms like Fly.io, Railway, and Render provision certificates for custom domains from their dashboard.
- Nginx + Certbot — for self-hosted deployments, use Certbot to issue Let’s Encrypt certificates and configure Nginx to terminate TLS before proxying to Autonnel.
Static asset domain
The static domain setting controls the base URL prepended to every S3 object key when generating a public asset URL.
If the static domain is left blank, the default is static. plus the root domain of the domain the upload is made for: a page’s default domain, else the fallback default domain. For example, shop.example.com gives https://static.example.com, and shop.example.co.uk gives https://static.example.co.uk. IP addresses, localhost and platform subdomains such as *.workers.dev get relative URLs instead. A domain can override this under Storage (see above).
The static domain field lives in Settings → Storage, alongside the S3 bucket it prefixes, not in Pages → Domains. Set it explicitly if:
- You are using a CloudFront distribution or Cloudflare cache as a CDN in front of your S3 bucket
- Your S3 bucket public URL differs from the
static.subdomain convention - You want all asset URLs to use a specific host for cache-control purposes
The value can be a bare label (e.g., cdn, used as cdn.<root domain>), a hostname (e.g., cdn.example.com) or an https:// URL (e.g., https://cdn.example.com). If you enter a hostname, https:// is prepended automatically; http:// URLs are rejected.
Example:
If your R2 bucket is publicly accessible at https://pub-abc123.r2.dev, set the static domain to that value. All uploaded images will then resolve as https://pub-abc123.r2.dev/<object-key>.
If you put a Cloudflare cache zone in front, change the static domain to your Cloudflare zone URL instead.
Removing a domain
Click the trash icon on a domain’s row, read what goes offline and type the host to confirm. Removing a domain deletes its page attachments and its custom code (pages attached to other domains stay), funnel links that lead only to that domain stop working, and emails for its past orders fall back to the fallback default domain’s brand. No redirect is left in place; visitors to that hostname get the coming-soon page until DNS is updated.
The fallback default domain can only be removed when it is the last domain. Make another domain the fallback default first.
Caveats
- No wildcard domains in OSS — each subdomain requires its own Domain row. Wildcard support (e.g.,
*.example.com) is a SaaS-only feature. - No built-in domain verification — in the OSS version, adding a domain row does not verify that DNS is correctly pointed. Verification (including Cloudflare for SaaS integration) is available only in the managed SaaS version.
- You cannot add the same hostname twice to the same deployment.
Related
- Pages — multi-domain — per-page domain routing details
- Email sending - per-domain sending provider and test email
- Storage — S3 bucket and static domain interaction