Files
Aron PrinsandClaude Opus 5 325c9eb819 seo: hand-write titles and descriptions for all 192 pages (#115)
## Why

The build derived `<title>` from the **sidebar label** and the
description from the **first paragraph clipped to 220 characters**. Both
are the wrong source. A sidebar label is written for a 240px-wide nav
that supplies its own context; a search result has none.

On production that produced:

- **7 pages titled "Overview"**, and 32 pages sharing a title with
another page
- **109 of 193 descriptions cut off mid-word**, and 174 over 160
characters (where Google truncates)

```
/guides/welcome/key-concepts/
  BEFORE (220):  ...and if you misunderstand them early, the product wi
```

Near-identical titles are the weak-differentiation signal behind
"crawled — currently not indexed", which is the exact symptom on this
property.

## What changed

`seo_title` and `seo_description` frontmatter on **every one of the 192
pages**, written by hand against each page's real content and optimised
for the click — lead with what the reader can do, name the concrete
things covered, no keyword stuffing, no repeating the title.

| | Before | After |
|---|---|---|
| Duplicate titles | 32 pages | **0** |
| Duplicate descriptions | — | **0** |
| Descriptions cut mid-word | 109 | **0** |
| Descriptions over 160 chars | 174 | **0** |
| Title length (incl. suffix) | up to "Overview" | **26–60** |
| Description length | 31–240 | **122–158** |

**No prose was rewritten.** I measured content overlap between the
colliding pairs first — only 17–23%, so these were always distinct pages
wearing the same label, not duplicate content. The `docs/` diff is **564
insertions, zero deletions**.

### Examples

```
BEFORE — all seven identical:  "Overview | Paperclip Docs"
AFTER:  "Adapters Overview"      "API Overview"        "CLI Overview"
        "Deployment Overview"    "Bundled Skills"      "Optional Skills"
        "Experimental Features"

BEFORE — both identical:  "Issues | Paperclip Docs"
AFTER:  "Issues: Creating and Tracking Work"   /guides/day-to-day/issues/
        "Issues API"                           /reference/api/issues/
```

```
/guides/getting-started/five-minute-path/
BEFORE (220):  The shortest route from a running Paperclip instance to an agent that has
               just completed work for you. After Paperclip is installed, the path takes
               about 5 minutes: create a company, hire a CEO agent, approve its first s
AFTER  (131):  Install Paperclip, create a company, hire a CEO agent, and approve its
               first strategy — a working AI company in about five minutes.
```

## Plumbing

- **`site/build-release.mjs`** prefers the authored fields; the derived
path stays only as a fallback the CI gate prevents ever reaching.
`<title>`, `<meta name="description">`, and the `TechArticle` JSON-LD
all read from the same source.
- **`site/app.js`** uses the same fields, so a client-side transition
cannot leave a different title on screen than the crawler was served.
Verified in-browser: navigating `/guides/day-to-day/issues/` →
`/reference/api/issues/` swaps to exactly the server-rendered values, no
JS errors.
- **`scripts/verify-seo-metadata.mjs`** (new) enforces presence,
uniqueness, length, complete-sentence endings, and the
frontmatter-safety rules. Wired into `docs:test` and CI as its own step.

I negative-tested the gate rather than assuming it works — it correctly
fails on a duplicate title, a mid-word description, and a missing field,
and passes again once restored.

## Automating it going forward

`skills/sync-docs/SKILL.md` now:

- gains an **"Authored SEO metadata"** section: why the fields exist,
the enforced rules as a table, and how to actually write them (title
names the subject not the nav position; description writes for the
click; never generate mechanically from the first paragraph — *that is
the fallback the gate exists to prevent*).
- requires both fields in the **page-authoring instruction** given to
every subagent, with guidance on when to update an existing description
versus leave it.
- runs `docs:test:seo-metadata` and `docs:test:crawlable-links` as
**fail-loud gates in Phase 7** before commit.
- documents all six build gates in the files/gates section.

So once this lands, a new page cannot ship without hand-written
metadata, and a title collision cannot reach production.

## Verified

All six verifiers pass:

```
Static route verification passed
Asset fingerprint verification passed
Hierarchical Skills nav verification passed
Skill source block verification passed (11 skill pages, 1 control page)
Crawlable-link contract passed: 40886 internal links across 194 pages resolve in one hop
Authored-SEO contract passed: 192 pages carry a unique, hand-written seo_title and seo_description
```

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
2026-08-25 22:51:42 +02:00

3.8 KiB

seo_title, seo_description
seo_title seo_description
Dashboard API One call for a company health snapshot — the same summary powering the board dashboard, inbox alerts, and budget warnings in the UI.

Dashboard

Get a compact health snapshot for a company in a single call. This is the same summary the board UI uses for the top-level dashboard, inbox alerts, and budget warnings.


Get Dashboard

GET /api/companies/{companyId}/dashboard

Returns one object with the current company health snapshot. The endpoint is read-only and company-scoped.

What the buckets mean

  • agents.active counts agents that are operational and available. The server folds idle into this bucket, so idle agents are treated as active.
  • agents.running counts agents currently executing a heartbeat.
  • agents.paused counts agents intentionally paused.
  • agents.error counts agents whose last run failed or left them in an error state.
  • tasks.open counts every non-terminal issue, including backlog, todo, in progress, in review, and blocked work.
  • tasks.inProgress counts only issues in in_progress.
  • tasks.blocked counts only issues in blocked.
  • tasks.done counts only issues in done.
  • costs.monthSpendCents is the total cost recorded for the current UTC month.
  • costs.monthBudgetCents is the company monthly budget in cents.
  • costs.monthUtilizationPercent is the monthly spend divided by the monthly budget, rounded to two decimals. If the budget is 0, utilization is 0.
  • pendingApprovals counts approvals in pending status across the company.
  • budgets.activeIncidents counts open budget incidents.
  • budgets.pendingApprovals counts budget incidents that still need approval.
  • budgets.pausedAgents counts agents currently paused by budget enforcement.
  • budgets.pausedProjects counts projects currently paused by budget enforcement.

Common uses

  • Board operators use it for the main dashboard cards and budget warning banner.
  • Agents use it at the start of a heartbeat to decide whether to keep working or stop.
  • Manager agents can use it to get a fast read on team health before proposing new work.

Example response

{
  "companyId": "company_123",
  "agents": {
    "active": 4,
    "running": 1,
    "paused": 0,
    "error": 0
  },
  "tasks": {
    "open": 12,
    "inProgress": 3,
    "blocked": 2,
    "done": 8
  },
  "costs": {
    "monthSpendCents": 18450,
    "monthBudgetCents": 50000,
    "monthUtilizationPercent": 36.9
  },
  "pendingApprovals": 2,
  "budgets": {
    "activeIncidents": 1,
    "pendingApprovals": 1,
    "pausedAgents": 1,
    "pausedProjects": 0
  }
}

Request examples

curl -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  http://localhost:3100/api/companies/company_123/dashboard
const res = await fetch("http://localhost:3100/api/companies/company_123/dashboard", {
  headers: {
    Authorization: `Bearer ${process.env.PAPERCLIP_API_KEY}`,
  },
});

if (!res.ok) throw new Error(`Dashboard request failed: ${res.status}`);
const dashboard = await res.json();
console.log(dashboard.tasks.inProgress);
import os
import requests

res = requests.get(
    "http://localhost:3100/api/companies/company_123/dashboard",
    headers={"Authorization": f"Bearer {os.environ['PAPERCLIP_API_KEY']}"},
)
res.raise_for_status()
dashboard = res.json()
print(dashboard["costs"]["monthUtilizationPercent"])

Notes

  • The dashboard is scoped to the company in the URL. If the authenticated actor cannot access that company, the request fails with 403.
  • If the company does not exist, the request fails with 404.
  • The endpoint does not return recent activity or stale-task details. The UI renders those from separate queries.