| name | treg-page |
| description | Write a treg.to agent page (/agents/<client>) or use-case page (/use-cases/<category>/<job>). Researches the real problem on Reddit and X with agent-reach BEFORE writing, so the page targets the words buyers actually use and quotes their own questions. Use when adding a page from marketing/pseo-ship-plan.md, or when asked to "write the <job> page" / "add the <agent> page". |
| argument-hint | [use-case <category>/<job> | agent <slug>] |
treg-page — research first, then fill in the spec
Both page types are templates fed by one dict entry. No HTML is written by hand: the route in
api.py renders titles, prices, provider rows, reliability and schema from catalog_store at
request time. Your job is the copy, and the copy is only as good as the research behind it.
Read marketing/pseo-ship-plan.md for what to write next and docs/context/interface/seo.md for
how the pages work. Never invent a number: if it is not in the catalog, it does not go on the page.
The order matters. Do not skip step 1.
1. Find the words buyers use (measure, never guess)
The catalog's vocabulary is not the buyer's. "People enrichment" is our word; "email finder" is
theirs. Measure before titling anything:
uv run --frozen treg call google-ads "v22/customers/2277522568:generateKeywordHistoricalMetrics" \
--method POST --data '{"keywords":["email finder","email finder api","linkedin email finder"],
"geoTargetConstants":["geoTargetConstants/2840"],"language":"languageConstants/1000",
"keywordPlanNetwork":"GOOGLE_SEARCH"}'
Google Ads is an own-key tool, so this costs nothing. Use the tool-scoped form (); the bare endpoint id is ambiguous across three registered accounts. Try 12 to 20
phrasings: the job in our words, the job in the buyer's words, , ,
, and the agent-prefixed forms. Keep whatever clears ~100/month; a term with 0
volume must not become an H1.
