Custom domains

On the Agency plans you can serve a client’s documents from a domain they own — for example read.acme.com — so readers never see a Living Page address.

Adding a domain

Open the client workspace, go to its Domain settings, and enter the hostname you want to use (read.acme.com).
We’ll show you the DNS records to create.
Add them at whoever hosts the domain’s DNS — the client’s registrar, or their hosting provider.
Leave the page open. We check every few seconds and the status updates on its own.

The DNS records

You’ll be asked to create up to three records. The exact values are shown in the dashboard — use those rather than copying from here, since the verification records are unique to your domain.

Type	Name	Points to	Why
`CNAME`	your hostname, e.g. `read`	`custom.livingpage.app`	Routes readers to us
`TXT`	`_acme-challenge.…`	value shown in the dashboard	Issues the SSL certificate
`TXT`	value shown in the dashboard	value shown in the dashboard	Proves you control the domain

The second TXT record isn’t always requested — add it only if the dashboard shows one.

Certificates are issued automatically once the records resolve. DNS changes can take a while to propagate — anything from a few minutes to a few hours depending on the provider and the previous TTL.

What the links look like

On a custom domain, share links drop the /v/ prefix:

https://read.livingpage.app/v/acme/k3f9x2p1m7qd   ← default
https://read.acme.com/k3f9x2p1m7qd                ← custom domain

Links already shared on the default domain keep working — adding a custom domain doesn’t break anything you’ve sent.

Limitations

Share links only. Embeds are always served from embed.livingpage.app, even when the client has a custom domain
One domain per client, and a given hostname can only be claimed by one workspace
The reader’s browser tab still reads “Living Page” — the page title and favicon aren’t configurable yet, even with white-label on

Client workspaces — what else is set per client.