Trust page finalization checklist
A pre-public-preview checklist for replacing placeholder trust-page details with site-owner-approved contact, privacy, disclosure, and editorial language before affiliate applications.
Getaway Brief Trust Page Finalization Checklist
Status: pre-launch checklist; no publishing, affiliate application, or live tracking is approved by this document.
Use this before the site owner approves a public preview or submits affiliate applications. The current generated pages are structurally present, but several fields must be finalized for the actual public URL, contact method, hosting setup, analytics provider, and affiliate partners.
Pages that exist locally
| Page | Local route | Current state | Finalization required before public use |
|---|---|---|---|
| About | /about.html | Usable project-level description | Confirm final brand/operator wording and whether the site owner wants a personal/business attribution. |
| Contact | /contact.html | Placeholder only | Replace with the site owner-approved email, form, or contact workflow before affiliate applications. |
| Privacy | /privacy.html | Placeholder aligned with tracking-free local build | Update for actual hosting, analytics provider, cookies, affiliate redirects, contact forms, and retention. |
| Affiliate disclosure | /affiliate-disclosure.html | General disclosure present | Confirm final wording once partner programs and link behavior are known. |
| Editorial policy | /editorial-policy.html | Conservative AI-assisted editorial wording present | Confirm whether to name AI-assisted production, human review expectations, and correction workflow. |
| How to use Getaway Brief | /how-to-use-tripsignal.html | Reader-facing method page present | Confirm it still matches the final public navigation and status labels. |
the site owner decisions needed
- Public URL decision — approve either a domain or a deploy-preview URL for applications.
- Contact method — choose the email/form that affiliate networks and readers can use.
- Privacy posture — keep local builds tracking-free; if analytics is enabled after approval, prefer Plausible or Umami. Do not add GA4 unless the site owner explicitly changes the analytics decision.
- Affiliate-link disclosure — approve final disclosure wording before replacing placeholders with partner URLs.
- Editorial accountability — decide what operator name, correction process, and AI-assistance language should appear publicly.
- Representative page policy — keep all 14 article pages at
researcheduntil exact-page verification is recorded; do not use a researched page in applications as if it were fact-final.
Minimum public-preview gate
Before a public preview is approved, complete these checks:
- Rebuild the site and run validation.
- Run affiliate safety audit and confirm no live partner links or unapproved tracking markers exist.
- Run accessibility audit and confirm no static page issues are present.
- Confirm contact/privacy/disclosure wording for the actual public preview URL.
- Confirm robots/sitemap behavior for the preview.
- Confirm no article is labeled
publish_candidateunless its matching verification record exists.
Minimum affiliate-application gate
Before affiliate applications are submitted, complete these checks:
- Public URL is live or deploy-preview URL is approved by the site owner.
- Contact/privacy/disclosure/editorial pages are no longer placeholders.
- Source health is rerun for all article source-note URLs.
- The representative pages listed in
/representative-page-final-check-queue.htmlhave exact-page checks recorded in the ledger or research briefs. - Affiliate signup go/no-go page is reviewed after the above checks.
- No private credentials, API keys, partner IDs, or paid services are introduced without explicit approval.