Deploying a website

Every TrustPager website record can be given real hosting: a working production URL, its own custom domain, and automatic redeploys every time the site changes. This is managed from the Deployment band at the top of each website's detail page.

You'll see the Deployment band on any website you can view. Creating, redeploying, pointing a domain, choosing the Core URL, taking the site offline, and deleting the repository all need website edit permission. Adopting an existing site is limited to platform admins and owners.

Where to find it

Go to https://app.trustpager.com/growth/websites and open any website record. The Deployment band sits at the top of the detail page, above the page builder.

Creating and hosting a site in one step

If the website record hasn't been hosted yet, click Create my website. This sets up a hosting repository from TrustPager's starter template and deploys it immediately. From that point on, every change to the site redeploys automatically.

Deployment status and controls

Once a site is hosted, the Deployment band shows:

• Status: Building, Live, or Build failed.
• Production URL: the live address visitors use. This is the site's default hosting URL until a custom domain is pointed at it.
• Staging URL: a separate address for previewing changes before they go live on the production URL.
• Last deployed: when the most recent deploy went out.

Two buttons sit alongside the status:

• Redeploy: triggers a fresh deploy without needing a new change to push.
• Refresh status: re-checks the current build and deploy state (use this if a status looks stuck).

Custom domain and canonical URL

To put the site on the client's own domain instead of the default hosting URL:

1. Enter the domain (for example example.com) in the Deployment band and click Point a domain.
2. TrustPager attaches both the bare domain (example.com) and its www version (www.example.com), and shows the DNS record(s) to add at the domain's own DNS provider (a CNAME pointing at the site).
3. Add the CNAME record(s) shown, then click Refresh. Repeat until each record shows Verified. DNS propagation isn't instant; it can take anywhere from a few minutes to a few hours depending on the provider.

If the domain is on Cloudflare DNS

Add the record(s) exactly as shown and set Proxy status to Proxied (the orange cloud). Leave TTL on Auto.

If the domain is on any other DNS provider

Add the record as shown with TTL set to Auto. There's no proxy toggle outside Cloudflare, so nothing else to change.

Choosing which host is canonical

Once both the bare domain and www are attached and verified, one of them is the Core URL, the single real address the site should be known by, and the other Redirects to it. The redirect is permanent and preserves the path and query, so a visitor who types either version lands on exactly the same page. Having one canonical address, rather than two working URLs, is better for SEO.

By default the bare domain is the Core URL and www redirects to it, but you can switch it either way. In the DNS table, each row has a Role column with a dropdown showing Core URL or Redirect. Picking one on either row automatically flips the other, since they're opposites, so exactly one host is always the Core URL.

Changing which one is canonical rebuilds the site automatically, which takes a minute or two. The DNS records themselves don't change when you flip the role, only the redirect direction does, and Verified status is preserved throughout.

Adopting a site that's already live

If a site was already deployed before it had a TrustPager website record (an existing hosted site you want to bring under management here), use Adopt an existing site. This links the already-live site to its TrustPager record without recreating or redeploying it.

Deleting the repository

Delete Repo permanently deletes the website's code repository and its live deployment. This is irreversible: there is no undo, so only use it when the client's hosting is genuinely being retired for good.

Clicking it opens a warning dialog. You need to type the repository's name to confirm before the delete button enables, so it can't be triggered by mistake.

If you just want to take the site down without losing the code, use Take offline instead. That stops the live deployment but keeps the repository intact, so the site can be brought back later. Reach for Delete Repo only when nothing about the site needs to survive.

Troubleshooting

• Status stuck on Building: click Refresh status. If it's still stuck after a minute or two, click Redeploy to trigger a fresh attempt.
• Build failed: the last push to the site had an error. Redeploy after confirming the site's content is in a valid state, or reach out if it keeps failing.
• Domain won't verify: double-check the record Type, Name, and Value match exactly what TrustPager returned, and that TTL is on Auto. DNS changes can take anywhere from a few minutes to a few hours to propagate depending on the client's provider.
• Rebuild after changing the Core URL: give it a minute or two for the automatic rebuild to finish before checking the site again.