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, adding a redirect domain, 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

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 makes the www version (www.example.com) the live site and points the bare domain (example.com) at it, then shows the DNS records to add at the domain's own DNS provider.
3. Add every record 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.

You'll see two kinds of record, each labelled in the Role column:

• Core URL: a CNAME that makes www.example.com the live site.
• Redirect: an A and AAAA record that point the bare example.com at TrustPager's redirect service, which forwards it to the www address over HTTPS, keeping the path intact. An A record works at every registrar, which is why the bare domain uses one instead of a CNAME.

So www.example.com is always the site's single canonical address, and the bare example.com permanently redirects to it (a 301, preserving the path and query). Having one canonical address rather than two working URLs is better for SEO.

Setting the records at your DNS provider

On Cloudflare, add every record exactly as shown and set them to DNS only (the grey cloud), not Proxied. Leave TTL on Auto. On any other provider, there's no proxy setting; just add the records with TTL Auto.

Redirect domains

A redirect domain is a separate old or secondary domain that you forward to a live site. Every visitor is permanently redirected (a 301) to the matching page on the live site, with the full path and query preserved, so links to retired URLs keep their SEO value and land on the live site instead of a dead page. Use it for rebrands, domain consolidations, or capturing traffic from a domain you've stopped using.

This is different from the custom domain above: the custom domain is where the site is served; a redirect domain never shows the site, it only forwards visitors across to it. The Redirect domains section sits just below the custom domain on the same Deployment band.

1. In the Redirect domains section, enter the old domain (for example oldbrand.com) and click Add redirect domain.
2. TrustPager shows the DNS records to add at that domain's provider: an A and AAAA record for both the bare domain and its www, all pointing at TrustPager's redirect service.
3. Add those records at the old domain's DNS provider. On Cloudflare set them to DNS only (grey cloud); on any other provider just use TTL Auto.

Once the old domain resolves to us, TrustPager issues its HTTPS certificate automatically and every visit forwards to the live site, path and all. You can add more than one redirect domain to the same site, and remove any of them with the delete icon next to it.

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, that TTL is on Auto, and (on Cloudflare) that the records are set to DNS only, not Proxied. DNS changes can take anywhere from a few minutes to a few hours to propagate depending on the provider.
• Redirect domain isn't forwarding yet: confirm the A and AAAA records for both the bare domain and its www are in place at that domain's provider (DNS only on Cloudflare). The certificate is issued on the first visit once the domain resolves to us, so give it a few minutes after the DNS propagates.