SEO Growth Workspace

Contribute within authority. The active workspace contract and current task scope decide whether a run may modify this skill or open an upstream PR. When authorized, fix the canonical source through its normal release flow; otherwise leave the skill untouched and record concrete, non-duplicate friction in the .seo/log.md handoff when that write is already in scope. Invoking this skill never implies product-development scope.

Run a durable SEO operating workspace for a product or local-business website. The goal is not generic advice; it is evidence, prioritization, implementation, verification, and continuity. Use this skill as a mode router: load only the reference the selected mode or ticket needs.

Design rules (the constitution): (1) Prose states intent, invariants, and completion criteria — scripts/loop-state.mjs owns state formats, legal transitions, and crash intermediates. (2) One file per loadable concern; no ownership disclaimers. (3) Fail-closed is reserved for the four outcome-protecting invariants: no silent dry exits; no certificate under drift or stale coverage; no Done without evidence; no publish past integrity gates — everything else degrades gracefully. (4) Field-discovered ambiguity is resolved by judgment and logged (or becomes a fixture), not legislated; a new normative clause requires judgment failing twice on the same point with bad SEO consequences.

Ground Rules

• Speak the user's language; keep code identifiers in English. Match the target site's language, market, and brand voice for public content.
• Use the target repo's package manager, deploy path, auth workflow, and UI validation tool. Bundled scripts are dependency-free (node, 18+).
• Delegate online research legwork through the runtime's research skill when one exists; each mode's evidence contract still governs what gets captured.
• Never print secrets from env files, dashboards, OAuth, or admin surfaces.
• One current focus ticket; no task lists outside .seo/backlog.md; evidence in audit.md, decisions in strategy.md, handoffs in log.md, dated reports in reports/.
• Prefer matrix-shaped audit outputs. Produce actual copy, schema, calendar rows, scripts, code, or admin changes where the mode calls for it.

Workspace