@w2bagency/content-loop

The W2B SEO Kit — a structure-agnostic, additive layer applied onto any migrated Astro client repo. It delivers the deterministic CI gate, the Code/Git content adapter, the .w2b/context/ scaffold, the .claude/ commands, and the onboarding prompt so the SEO specialist can run the 5A/5B content loop (SEO/GEO/AEO) on a client via Claude Code web — branch → preview → review → merge.

First incarnation of the deferred content-loop product, via the Astro/Git adapter.

What's in here

• Library (src/) — published to npm; the w2b-gate binary is fetched on-demand by CI via pnpm dlx (never a client-site dependency):
  • payload/canonical.ts — canonical post payload (zod, mirrors landing/keystatic.config.ts).
  • context/ — SiteMap type + parseSiteMap (the per-client structure description).
  • adapter/code-git.ts — structure-agnostic adapter: listPosts / readPost / writeDraft, driven entirely by site-map.md (never hardcodes paths or field names). Resolves per-post locale.
  • gate/ — five deterministic validators (frontmatter limits, hreflang parity, cannibalization, JSON-LD schema shape, .w2b/context freshness) + the runGate orchestrator.
  • baseline/gsc-snapshot.ts — GSC baseline serializer (proof-of-ROI snapshot).
  • cli/gate.ts — the w2b-gate binary (gate run + --emit-treehash).
• templates/ — the thin scaffold copied ONCE into a client repo at onboarding (.claude/, .w2b/, data/, baseline GEO files, the GitHub Actions workflow, .mcp.json.tpl, .npmrc.tpl).

Apply to a client repo

1. pnpm exec w2b-onboard (the onboarding prompt) walks the repo once and commits .w2b/context/.
2. Copy templates/.npmrc.tpl → .npmrc in the client repo root. This maps the @w2bagency scope to public npm (https://registry.npmjs.org) — no auth token required. Do NOT add @w2bagency/content-loop to the site's package.json — the package is CI tooling, not a site dependency. The .npmrc is harmless to Vercel: because no package.json entry depends on the @w2bagency scope, Vercel never fetches from that registry.
3. Copy templates/.github/workflows/w2b-gate.yml. CI fetches w2b-gate on-demand via pnpm dlx from public npm (no secrets needed) and runs it on every PR. @w2bagency/content-loop is never installed into the client site's node_modules and never reaches the Vercel build.

Local dev

pnpm install
pnpm test          # vitest — 40 tests
pnpm typecheck
pnpm build         # emits dist/, including the w2b-gate bin
node dist/cli/gate.js <path-to-client-repo>             # run the gate
node dist/cli/gate.js --emit-treehash "<blog-glob>"     # canonical treeHash

Hard rule

@w2bagency/site-audit-mcp-style discipline: never hardcode a client's blog path or frontmatter key names — always go through SiteMap. The canonical payload mirrors keystatic; if they diverge, keystatic wins and this mirror is updated. A green gate means "structure is clean", not "publishable" — human E-E-A-T sign-off is still required before merge.