Programmatic SEO

# Not live yet (gaps #2)
curl -X POST "https://api.sb/leaseline.app/campaigns?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"programmatic-seo"}'

 1import { $ } from 'startup-builder'
 2
 3return await $.Campaign.create({ play: 'programmatic-seo' }, { mode: 'try' })   // dry run on the day-0 Startup, 2026-08-24 · Not live yet, gaps #2

npx startup-builder do Campaign.create --json '{"play":"programmatic-seo"}' --try   # Not live yet (gaps #2)

{
  "name": "do",
  "arguments": {
    "code": "return await $.Campaign.create({ play: 'programmatic-seo' }, { mode: 'try' })   // dry run on the day-0 Startup, 2026-08-24 · Not live yet, gaps #2",
    "mode": "try"
  }
}

 1{
 2  "type": "https://startupbuilder.dev/errors/refused",
 3  "title": "Refused",
 4  "status": 422,
 5  "detail": "programmatic-seo can’t start yet: 1 check fails and 2 warn.",
 6  "checks": [
 7    {
 8      "check": "use-when",
 9      "status": "pass",
10      "observed": "62 cities with 30 or more leases; demand for the query in 58",
11      "doc": "/plays/programmatic-seo#check-use-when",
12      "fix": "Keep 30 or more records with a fact of their own, or run editorial-seo.",
13      "then": "Metric.query"
14    },
15  …

curl "https://api.sb/leaseline.app/events?where=name%20in%20(%22Keyword.measured%22%2C%20%22Collection.filled%22%2C%20%22Site.published%22%2C%20%22Page.unindexed%22%2C%20%22Metric.watched%22%2C%20%22Fact.changed%22)&limit=1" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# Not live yet (gaps #7)
curl -X POST "https://api.sb/leaseline.app/triggers/fire?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"like":"event_3150"}'

# Not live yet (gaps #7)
curl "https://api.sb/leaseline.app/decisions?where=on%20%3D%20%22collection_7%22" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# Not live yet (gaps #7)
curl "https://api.sb/leaseline.app/actions?where=on%20%3D%20%22collection_7%22" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

 1import { $ } from 'startup-builder'
 2
 3const { events: [last] } = await $.Event.list({ where: 'name in ("Keyword.measured", "Collection.filled", "Site.published", "Page.unindexed", "Metric.watched", "Fact.changed")', limit: 1 })   // { play } compiled to this Play’s Trigger Events
 4const { subject } = await $.Trigger.fire({ like: last.$id }, { mode: 'try' })   // the same Event again, in try mode · Not live yet, gaps #7
 5const { decisions: [decision] } = await $.Decision.list({ where: `on = "${subject}"` })   // what it chose, and why · Not live yet, gaps #7
 6const { actions } = await $.Action.list({ where: `on = "${subject}"` })   // what it did, with its checks · Not live yet, gaps #7
 7return { decision, actions }

npx startup-builder do Event.list --json '{"where":"name in (\"Keyword.measured\", \"Collection.filled\", \"Site.published\", \"Page.unindexed\", \"Metric.watched\", \"Fact.changed\")","limit":1}'
npx startup-builder do Trigger.fire --json '{"like":"event_3150"}' --try   # Not live yet (gaps #7)
npx startup-builder do Decision.list --json '{"where":"on = \"collection_7\""}'   # Not live yet (gaps #7)
npx startup-builder do Action.list --json '{"where":"on = \"collection_7\""}'   # Not live yet (gaps #7)

{
  "name": "do",
  "arguments": {
    "code": "const { events: [last] } = await $.Event.list({ where: 'name in (\"Keyword.measured\", \"Collection.filled\", \"Site.published\", \"Page.unindexed\", \"Metric.watched\", \"Fact.changed\")', limit: 1 })   // { play } compiled to this Play’s Trigger Events\nconst { subject } = await $.Trigger.fire({ like: last.$id }, { mode: 'try' })   // the same Event again, in try mode · Not live yet, gaps #7\nconst { decisions: [decision] } = await $.Decision.list({ where: `on = \"${subject}\"` })   // what it chose, and why · Not live yet, gaps #7\nconst { actions } = await $.Action.list({ where: `on = \"${subject}\"` })   // what it did, with its checks · Not live yet, gaps #7\nreturn { decision, actions }",
    "mode": "try"
  }
}

 1{
 2  "decision": {
 3    "$id": "https://api.sb/leaseline.app/decisions/decision_455",
 4    "$type": "Decision",
 5    "choice": "grow-the-batch",
 6    "reason": "52 of batch 3’s 60 Pages are indexed at day 28 (87 %), at 3.4 visits each; 120 more stays under the 400-Page cap",
 7    "stakes": "medium",
 8    "options": [
 9      "release-batch",
10      "grow-the-batch",
11      "hold-for-rework",
12      "recheck-fact",
13      "withdraw-batch",
14      "to-the-marketing-lead"
15  …

action_3 releases batch 4, 120 renewal-rate Pages, once you approve it: the option’s stakes are medium. Each Page links the method Page with its lease count and the date checked.

≈ +$450 ARR a month at 130 Pages

Worth

40 min week 1, then 10 a week

Your time

$0.02 per Page, ~$2.60 a month at 130

Spend

Day 6: the first Page indexed

First signal

30+ records with a fact only you hold

Use it when

Under 30: editorial-seo · no Site of your own: publish one (Site.publish)

Not yet when

Worth’s formula: about +2.8 visits per indexed Page × 130 Pages a month × 0.03 visits to signup × 0.12 signups to paid (your last 90 days) × $347 Pro ARR ≈ +$455. Under First signal: About 5 weeks to tell a +2 lift at 130 Pages a month (1 to read, 4 for the 28-day window); at 30 Pages, about 9 weeks.

Start it this weekCopy Anchor Link

npx startup-builder add play programmatic-seo   # 1 · writes plays/programmatic-seo.mdx (Not live yet, gaps #5)

# 2 · dry run; below, its 422 on 2026-08-24
curl -X POST "https://api.sb/leaseline.app/campaigns?mode=try" \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"programmatic-seo"}'

# 3 · keep it, at You approve the first wave
curl -X POST https://api.sb/leaseline.app/campaigns \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"play":"programmatic-seo"}'

# on
curl -X POST https://api.sb/leaseline.app/processes/content-marketing/enable \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

# off: no batch releases; released Pages stay up
curl -X POST https://api.sb/leaseline.app/processes/content-marketing/pause \
  -H "Authorization: Bearer $STARTUP_BUILDER_API_KEY"

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "programmatic-seo can’t start yet: 1 check fails and 2 warn.",
  "checks": [
    {
      "check": "use-when",
      "status": "pass",
      "observed": "62 cities with 30 or more leases; demand for the query in 58",
      "doc": "/plays/programmatic-seo#check-use-when",
      "fix": "Keep 30 or more records with a fact of their own, or run editorial-seo.",
      "then": "Metric.query"
    },
    {
      "check": "baseline",
      "status": "pass",
      "observed": "0.4 search visits per city a month to your existing Pages, n 120",
      "doc": "/plays/programmatic-seo#check-baseline",
      "fix": "Read it once; it fills Before in Your number.",
      "then": "Metric.query"
    },
    {
      "check": "approved-pages",
      "status": "fail",
      "observed": "no method Page: Dataset, lease count, date checked",
      "doc": "/plays/programmatic-seo#check-approved-pages",
      "fix": "Publish the method Page every city Page links to.",
      "then": "Site.publish"
    },
    {
      "check": "fact-check",
      "status": "warn",
      "observed": "19 of 62 cities hold under 30 leases",
      "doc": "/plays/programmatic-seo#check-fact-check",
      "fix": "Those 19 stay held until each reaches 30 leases.",
      "then": "Content.draft"
    },
    {
      "check": "role-unstaffed",
      "status": "warn",
      "roles": [
        "marketing-lead"
      ],
      "owned": 0,
      "doc": "/plays/programmatic-seo#check-role-unstaffed",
      "fix": "Staff the Marketing Lead, or leave it: incidents and approvals come to you.",
      "then": "Role.staff"
    }
  ]
}

Each Page costs $0.02 to draft and fact-check (Worker cost), and POST /{namespace}/keywords/{keyword}/measure reads cost $0.01 a pattern. Hosting on your own Site costs nothing. That comes to about $2.60 a month at 130 Pages and $0.60 at 30.

When it startsCopy Anchor Link

{
  "$id": "https://api.sb/leaseline.app/events/event_3150",
  "$type": "Event",
  "name": "Site.published",
  "at": "2026-09-21T09:00:00Z",
  "seq": 3150,
  "data": {
    "site": "site_1",
    "collection": "collection_7",
    "batch": 3,
    "pages": 60,
    "kind": "renewal-rate-by-city",
    "readAt": "2026-10-19"
  }
}

npx startup-builder trigger Site.published --like event_3150   # replays the release
npx startup-builder clock advance --by 28d   # fires batch-window-closed on day 28
npx startup-builder listen Site.published --forward-to http://localhost:3000/hook

Who runs itCopy Anchor Link

Content Lead · your agent (role:content-lead, worker_6) holds the Key Result. Growing a batch goes to you (Dana Okafor, person, worker_1) as an Approval, and incidents go to the Marketing Lead Role, which is unstaffed, so you. It writes no Message to anyone. Your number links to Did it work.

What it reads · What it may call. It reads your lease records, the query pattern’s demand and each Page’s index status. A Page states only what its record holds, with the lease count and the date checked. Its tools are POST /{namespace}/sites/{site}/publish, POST /{namespace}/content/draft, Content.withdraw (Not live yet, gaps #2), POST /{namespace}/issues/{issue}/triage, POST /{namespace}/incidents/open, POST /{namespace}/tasks/{task}/assign, and any other call becomes an Approval under the Role’s Mandate.

You hold the Content Lead Key Result: 3.0 visits per indexed Page by 2026-12-31. ← worker, metric
On each Trigger, choose one option and say why.                                  ← triggers, chooses
One Page per city with 30 or more leases, leading with its 2026 renewal share.   ← your file, line 4
State the lead fact in the first 100 words, with the method line.                ← copyRules 1, 4
The updated date moves only when a fact on the Page changes.                     ← copyRules 5
No rating markup, no generated author, no fact another source states.            ← copyRules 3, 12; fact-check

The slow loop, as a Change. decision_391 (2026-09-14, weekly) read that batch 1’s Pages with the lease count in the title indexed at 90 % against 70 % without it, so change_27 moved the count into every title (the Template) and Dana merged it with POST /{namespace}/changes/{change}/merge. Replayed on past batches, POST /{namespace}/changes/{change}/review put the indexed share at 86 %; read back on batch 3 at day 28 it is 87 %, n 60 (Example, day 56).

Bring your own agent (folded) starts at It does it, you can stop it when it matches or beats the seated agent on the eval suite, and at You approve each one when it does not; POST /{namespace}/roles/{role}/staff seats it.

npx startup-builder eval --scenario programmatic-seo-240 --agent "claude -p" --seat content-lead   # seated: 3.2 visits per Page, 0 fact-check fails published, $0.02 a Page · yours: 2.9, 2 fails, $0.03 → You approve each one

What it can do nextCopy Anchor Link

When it hands to youCopy Anchor Link

Growing a batch and every incident come to you: you hold the founder seat, and the Marketing Lead Role has no person. One Brief per Role, as captured (brief is Not live yet, gaps #7).

[
  {
    "$id": "https://api.sb/leaseline.app/approvals/approval_77",
    "$type": "Approval",
    "verdict": null,
    "deadline": "2026-10-20T17:00:00Z",
    "draft": "Release batch 4: 120 renewal-rate Pages for the next 120 cities",
    "route": "grow-the-batch",
    "checks": [
      {
        "check": "fact-check",
        "status": "pass"
      },
      {
        "check": "batch-cap",
        "status": "pass"
      }
    ]
  },
  {
    "$id": "https://api.sb/leaseline.app/tasks/task_533",
    "$type": "Task",
    "assignee": "worker_1",
    "due": "2026-10-06T17:00:00Z",
    "on": "site_1",
    "brief": {
      "who": "leaseline.app on Bing",
      "said": "indexed Pages fell 22 % in 7 days",
      "chose": "to-the-marketing-lead",
      "why": "a Site drop of 20 % or more",
      "paused": "every Page kind on Bing",
      "never": [
        "a release while the Incident is open"
      ]
    }
  }
]

You answer with POST /{namespace}/approvals/{approval}/approve or POST /{namespace}/approvals/{approval}/refuse, POST /{namespace}/tasks/{task}/claim (Take this one), POST /{namespace}/tasks/{task}/return with a reason, or POST /{namespace}/actions/{action}/redirect, each a one-call window. An Approval unanswered by its deadline expires, and the batch stays held. A Task nobody claims by its due time goes up a Role through POST /{namespace}/tasks/{task}/escalate, and person-promise fires.

On time: you, 3 of 3 within 1 business day, median 4 h, n 3, ■□□□ Too early to tell beside Other Startups’ 90 % on time. Your queue: in week 1, 2 approvals (the method Page and batch 1) and 1 weekly review; then 1 weekly review and an approval each time a batch grows.

The fixed line: POST /{namespace}/deals/{deal}/assign sets owner to the receiving person, the agent is never a Deal’s owner, and Meetings land on the owner’s calendar under the owner’s name.

When it won’t sendCopy Anchor Link

The captured refusal, then the Stop that fired as a Campaign.paused reason (Not live yet, gaps #2); the rewrite that published is the Eugene Page in Example.

{
  "type": "https://startupbuilder.dev/errors/refused",
  "title": "Refused",
  "status": 422,
  "detail": "The Eugene Page did not publish: its lead fact is found on another source.",
  "checks": [
    {
      "check": "fact-check",
      "status": "fail",
      "doc": "/plays/programmatic-seo#check-fact-check",
      "fix": "Lead with a fact only your records hold, with its count and date.",
      "then": "Content.draft"
    },
    {
      "check": "duplicate-page",
      "status": "pass"
    }
  ]
}

[
  {
    "reason": {
      "limit": "site-drop",
      "observed": "22 %",
      "bound": "20 %",
      "window": "7d"
    },
    "doc": "/plays/programmatic-seo#stop-site-drop",
    "task": "task_533"
  }
]

Did it workCopy Anchor Link

Cities were assigned at random: 120 got their Page in a batch, 120 were held back 30 days (rules m–o). Each figure’s call is POST /{namespace}/metrics/query by node and by arm; the leaf and every node above it are Not live yet (gaps #4, #6).

{
  "$id": "decisions/decision_455",
  "$type": "Decision",
  "choice": "grow-the-batch",
  "reason": "52 of batch 3’s 60 Pages are indexed at day 28 (87 %), at 3.4 visits each; 120 more stays under the 400-Page cap",
  "stakes": "medium",
  "options": [
    "release-batch",
    "grow-the-batch",
    "hold-for-rework",
    "recheck-fact",
    "withdraw-batch",
    "to-the-marketing-lead"
  ],
  "by": "worker_6",
  "on": "collection_7",
  "expected": "3.0 or more visits per indexed Page for batch 4 at day 28",
  "reopensWhen": "batch 4 under 75 % indexed at day 28"
}

The leaf counts search and AI-answer visits per Page in the index over the 30 days after release; the held-back cities count visits to your existing Pages for the same queries, to 50 matured Pages in each half. Every city has passed that, so this read stands until batch 4 lands.

How it moves it: each Page leads with a renewal share only Leaseline’s records hold, so 80 % were indexed within 28 days.

Guardrails: treated against held back: signups per visit, 2.9 % against 4.2 % (new-leads per visit), and search visits to the Site’s other Pages, 1,180 against 1,210 a week, so the new Pages took nothing from them.

{
  "$id": "https://api.sb/leaseline.app/campaigns/programmatic-seo",
  "$type": "Campaign",
  "play": "play:programmatic-seo@1",
  "path": [
    "indexed-page-yield",
    "icp-reached",
    "new-arr",
    "net-new-arr",
    "arr"
  ],
  "experiment": {
    "metric": "indexed-page-yield",
    "unit": "ratio",
    "heldBack": 120,
    "decision": null
  },
  "readout": {
    "value": 2.8,
    "n": 240,
    "maturing": 24,
    "interval": [
      1.9,
      3.7
    ],
    "readability": "B",
    "basis": "held-back",
    "pooled": false
  },
  "ledger": {
    "spend": 1,
    "workerCost": 5,
    "hours": 1.9,
    "pipelineArr": 0,
    "wonArr": 1041,
    "projectedArr": 455,
    "paybackDays": 5
  }
}

Outside benchmark: the top result gets 1.6 % of clicks on a query that shows an AI overview (a 300,000-Keyword click study, vendor-run).

Before it · After it. Before it: nothing; it starts from your own records. After it: instant-response answers each Page’s form, product-led hears the free signups, and aeo reads the same facts for AI answers.

ExampleCopy Anchor Link

Leaseline ran it from 2026-08-24 to 2026-10-19 (56 days). 284 city Pages were drafted, 44 held for rework, and 240 cities assigned at random: 120 released in 3 batches of 20, 40 and 60, and 120 held back 30 days. Read every captured Page and thread at ?threads=all; three follow the tables.

Search, Oct 2 · “lease renewal rate austin” → the Austin Page, first result.

The Page · Of 412 Leaseline-managed leases in Austin that ended in 2026, 292 renewed (71 %).¹ Method: Leaseline lease records, 412 leases, checked Oct 1.² By Leaseline.³

Its form, 14:20 · “Can I see Leaseline for my 30 units?” instant-response answered in 3 min; a trial started at 14:41, and it paid on Oct 16.

- Eugene renters renew about 64 % of the time, per the city’s 2025 housing report.
+ Of 188 Leaseline-managed leases in Eugene that ended in 2026, 121 renewed (64 %), checked Oct 2.

leaseline.app on Bing, 2026-10-03 09:00 · indexed Pages fell 22 % in 7 days · The agent, 09:01 · paused every Page kind on Bing and opened incident_12 (sev3). The Brief went to you (task_533), due 17:00; you claimed it at 11:10 and Bing recrawled by Oct 7.

¹ The lead fact, from Leaseline’s own records, in the first 100 words. ² The method line: the Dataset, the record count and the date checked. ³ The author line names the Startup, never a made-up person.

Your settingsCopy Anchor Link

---
holdout: 0.5      # half the cities wait 30 days for their Page
---
One Page per city with 30 or more leases, leading with its 2026 renewal share.
Release batches of 20, then grow each by up to double when 75 % index by day 28.
Put the lease count in every title.

$ npx startup-builder show plays/programmatic-seo
holdout 0.5 · city line 30 leases · batch growth 75 % · count in the title     your file  plays/programmatic-seo.mdx:2,4,5,6 (Ask 2026-08-24; line 6 by change_27, 2026-09-14)
worker role:content-lead, owns never · chooses 6 (4 rule, 2 read) · approval first-send, every-send · checks fact-check, duplicate-page, batch-cap, claims-resolve · stops 6 · placements google-search, bing    catalog  play:programmatic-seo@1 (Not live yet, gaps #5)

Every key from the catalogCopy Anchor Link

Compiled, not written: edit the Play record programmatic-seo and its Leaseline run, then regenerate. Every step runs from a sentence or a line of code. In your words: the CRM words you know, and where each lives here.