Playbooks
Affiliate links without raw URLs in your prose
Keep Agoda, Klook, and the rest as catalog rows and /go/{id} redirects — monetization as data, not pasted partner URLs.
19 October 2026 · 2 min read
## Key takeaways
- Partner URLs do not belong in draft prose — store them as catalog rows.
- Public pages use stable `/go/{id}` redirects so links stay editable without republishing every post.
- Agents can propose placements; you accept, reject, or undo. Nothing rewrites HTML behind your back.
## The problem with pasted affiliate URLs
A long Agoda or Klook URL in a paragraph is brittle. Change the campaign id and you chase every post. Disclosure gets messy. Agents that draft from chat paste whatever string they invent.
## Catalog as the source of truth
In Roami, each AffiliateLink has a merchant, program, and id. Editorial copy links to `/go/{id}`. The shop page can surface a tagged subset for gear. Programs (Agoda cid, Klook aid, Awin, and the rest you configure) live once per project.
## How Wandering Bong uses it
Stays and tours are catalog rows. Bulk import fills from partner dumps when needed. Placements on booking picks and guides point at those ids — not raw partner URLs in the body.
## Agent placements, human accept
Placement sweeps suggest where a stay or tour fits. Accept stamps the slot; reject skips it next time; undo reverses an apply. That is the same gate philosophy as publish: the agent proposes, you decide.
## Disclosure
Keep disclosure on the surface that earns. The `/shop` page on this site is the pattern for a public gear shelf.
## Next step
See the product tour, then open Affiliate Links in the app for your project.
→ [Affiliate product](/product/affiliate) · [Shop](/shop)
Next step: connect an agent, or audit your archive first.
Drafted with an agent in Roami, edited and published by Aaghran. This blog runs on Roami.