Application decision

Affiliate signup go/no-go checklist

A strict decision surface for whether Getaway Brief can safely submit affiliate applications. It separates content-base readiness from public-URL, trust-page, and representative-page verification gates.

Getaway Brief Affiliate Signup Go/No-Go Checklist

Status: no-go for external affiliate applications until the site owner approves a public URL/deploy preview and the representative pages below receive exact-page manual verification.

Purpose: give the site owner one short decision surface for affiliate signup readiness. This checklist is stricter than the content count: 10+ researched drafts are necessary, but not enough on their own.

Current decision

AreaCurrent stateDecision
Researched article base14 researched local drafts with demand evidence and factual source notes.Pass for content-base depth.
Publish-candidate pages0 pages marked publish_candidate.No-go for submitting article URLs as externally verified examples.
Trust pagesAbout, Contact placeholder, Privacy placeholder, Affiliate Disclosure, Editorial Policy, and How-to-use pages exist locally.Conditional pass; contact/privacy/disclosure need the site owner-approved public details.
Affiliate linksLocal CTAs remain placeholders; no partner IDs or live affiliate URLs.Pass for pre-approval safety.
AnalyticsLocal build remains tracking-free; Plausible/Umami only after approval; GA4 blocked by default.Pass for privacy posture.
Public URLNo approved domain or deploy-preview URL recorded.No-go for applications.
Representative page verificationShortlist, source packets, final-check queue, and verification template exist, but exact-page manual checks are not completed.No-go until recorded.

Minimum go conditions

Getaway Brief can move from no-go to ready to apply only when all of these are true:

  1. the site owner approves the public URL or deploy-preview URL that will be submitted in applications.
  2. the site owner approves the final contact method shown on /contact.html.
  3. the site owner approves privacy and affiliate-disclosure language for the actual analytics/hosting/partner setup.
  4. At least 3 representative guide URLs have completed exact-page verification recorded in research/ or the representative-page ledger, using affiliates/REPRESENTATIVE_PAGE_SOURCE_PACKETS.md as the source inventory for the first three pages.
  5. Those verified guides are either marked publish_candidate or clearly submitted as pre-launch samples with their research status disclosed.
  6. python3 scripts/audit_source_health.py has been re-run immediately before application prep, with no source URL blockers on submitted representative pages.
  7. python3 scripts/build_site.py has been re-run after any copy/status changes.
  8. The local safety audit still shows 0 live/non-placeholder affiliate CTA hrefs and 0 analytics/tracking markers unless the site owner has explicitly approved otherwise.

First 3 representative pages to verify

Prioritize pages that show the widest commercial fit while keeping claims conservative:

  1. /articles/weekend-trips-from-nyc-without-a-car.html — broad no-car hotel/tour intent; verify MTA, Amtrak, NYC Ferry, Dia Beacon, Hudson, and Visit Philadelphia source support before use.
  2. /articles/where-to-stay-near-zion-without-a-car.html — lodging/tour intent near a major park; verify NPS shuttle/directions/fees, Visit Utah support, and Springdale/tour-pickup assumptions before use.
  3. /articles/things-to-do-in-gatlinburg-when-it-rains.html — strong activities/tickets fit; verify official attraction hours, ticketing, closure days, and NPS/visitor-source framing before use.

Backup pages after those: dog-friendly-weekend-trips-from-atlanta, warm-weekend-trips-from-chicago-in-march, and where-to-stay-in-savannah-without-a-car.

Safe application wording once go conditions pass

Use conservative claims only:

Avoid these claims:

Approval boundary

The agent may keep improving local research, templates, and verification ledgers. The agent must not submit applications, publish/deploy, insert live affiliate links, spend money, register domains, or use the site owner credentials without explicit approval.