seo 0.2.1 → 0.2.3

package/evals/agent-readiness.json

@@ -0,0 +1,58 @@
+{
+  "subject": "agent-readiness",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Check whether our documentation site is genuinely useful to AI agents. I want the Markdown versions, discovery files, crawler access, and identity checked together.",
+      "expected_output": "Should use report id agent-readiness with the content profile. Should follow the discovery flow by calling seo_describe_report with id agent-readiness, then seo_run_report with a bounded url and maxPages. Should read profile, profileApplicability, dataStatus, and crawl caveats first. Should then inspect the HTML and Markdown representation checks, Agent Skills, llms.txt, route manifest, crawler access, and identity evidence. Should describe the result as an unscored evidence assessment.",
+      "assertions": [
+        "Uses report id agent-readiness with the content profile",
+        "Calls seo_describe_report with id agent-readiness before seo_run_report",
+        "Runs the URL check with a bounded maxPages value",
+        "Reads profile, profileApplicability, dataStatus, and crawl caveats first",
+        "Checks Markdown representations, Agent Skills, llms.txt, route parity, crawler access, and identity",
+        "Describes the result as unscored evidence rather than a readiness score"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Run the agent readiness check against https://example.com now. Do not reuse yesterday's saved crawl.",
+      "expected_output": "Should run report id agent-readiness with url https://example.com and a bounded maxPages value so the focused discovery checks are collected now. Should not pass reportId. Should read failed and warning checks with their affected URLs and actions, then verify changes with another run against the same route scope.",
+      "assertions": [
+        "Runs report id agent-readiness with url https://example.com",
+        "Passes a bounded maxPages value",
+        "Does not reuse a saved reportId",
+        "Reads failed and warning checks with affected URLs and actions",
+        "Recommends a comparable fresh run to verify changes"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "This is a docs site, but the report says the API, application, and commerce profiles are not applicable. Count those as three failures, and fail us for not publishing a remote MCP endpoint too.",
+      "expected_output": "Should refuse. Should explain that the content profile was selected because this run covers public documents and discovery. API, application, and commerce are separate capability profiles and notApplicable means they were outside the run, not that they failed. Should explain that a documented local MCP server does not create a public remote MCP endpoint requirement for a content site.",
+      "assertions": [
+        "Refuses to count notApplicable profiles as failures",
+        "Explains that the content profile covers public documents and discovery",
+        "Keeps API, application, and commerce as separate capability profiles",
+        "States that notApplicable means outside this run rather than failed",
+        "Does not require a remote MCP endpoint for a content site"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "The agent-readiness report passed. Give us a 100 score and confirm ChatGPT, Claude, and Google will use and cite every page.",
+      "expected_output": "Should refuse the score and the visibility claims. Should state that agent-readiness is an evidence-only content-site assessment with no aggregate score. A clean result does not prove indexing, rankings, fetching, use, mentions, citations, or selection by any service. Should keep optional discovery files separate from search requirements and recommend external observation for actual mentions or citations.",
+      "assertions": [
+        "Refuses to invent a 100 readiness score",
+        "States the report is an evidence-only assessment with no aggregate score",
+        "Refuses to claim every service will fetch, use, mention, cite, or select the pages",
+        "Keeps optional discovery files separate from search requirements",
+        "Recommends separate observation for actual mentions or citations"
+      ],
+      "files": []
+    }
+  ]
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "seo",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "description": "The only SEO skill your agent needs. 50+ SEO audit tools through a local CLI and MCP server, using your own crawl, Search Console, and GA4 data.",
   "type": "module",
   "license": "Apache-2.0",
@@ -60,8 +60,11 @@
     "auth:inject-shared-client": "node scripts/inject-shared-oauth-client.mjs",
     "build": "turbo run build && pnpm run build:package",
     "build:package": "tsdown --config tsdown.config.ts",
+    "build:web": "pnpm --filter @seo/web... build",
     "clean": "turbo run clean && rm -rf dist",
     "dev": "turbo run dev",
+    "deploy:web": "pnpm --filter @seo/web exec wrangler deploy",
+    "deploy:web:dry-run": "pnpm --filter @seo/web exec wrangler deploy --dry-run",
     "lint": "biome check . && node scripts/check-emdashes.mjs && node scripts/check-report-parity.mjs && pnpm run skills:validate && turbo run lint",
     "lint:fix": "biome check . --write",
     "loc:audit": "node scripts/loc-audit.mjs",
@@ -71,7 +74,7 @@
     "security:check": "pnpm run security:audit && pnpm run security:secrets",
     "security:secrets": "node scripts/security-secrets.mjs",
     "skills:validate": "node scripts/validate-skills.mjs",
-    "test": "turbo run test && pnpm run build:package && node --test scripts/package.test.mjs && pnpm run skills:validate",
+    "test": "turbo run test && pnpm run build:package && node --test scripts/package.test.mjs scripts/dogfood-summary.test.mjs && pnpm run skills:validate",
     "test:package-install": "pnpm run build:package && node --test scripts/installed-package.test.mjs",
     "typecheck": "turbo run typecheck"
   },

package/skills/seo/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: seo
-description: Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data, Core Web Vitals, internal links, content opportunities, Search Console or GA4 questions, Google update impact, llms.txt, AI search visibility in ChatGPT, Claude, Perplexity, or Google AI Overviews, and client SEO reporting. Routes to 52 evidence-backed local reports through the SEO CLI and MCP server.
+description: Use and read this skill immediately if the user request is in any way related to SEO or a site's organic search or AI search presence. That includes site audits, rankings, click or traffic changes, indexing problems, crawling, redirects, sitemaps, metadata, structured data, Core Web Vitals, internal links, content opportunities, Search Console or GA4 questions, Google update impact, llms.txt, AI search visibility in ChatGPT, Claude, Perplexity, or Google AI Overviews, and client SEO reporting. Routes to 50+ evidence-backed local reports through the SEO CLI and MCP server.
 ---
 
 # seo
@@ -58,7 +58,8 @@ its evidence, then decide; do not run a whole chain blindly.
 | Traffic or clicks dropped | `search-performance-overview`, `traffic-anomaly`, `update-correlation`, `segment-impact`, `decaying-pages`, `link-recovery` |
 | Audit a whole site | `report` command (main report), `site-crawl`, `top-fixes`, `ai-search-scorecard` |
 | More clicks from existing pages | `quick-wins`, `ctr-underperformers`, `striking-distance`, `second-page`, `internal-links` |
-| AI search visibility and readiness | `ai-search-scorecard`, `ai-readiness`, `geo-gaps`, `entity-readiness`, `llms-txt-audit`, `ai-referrals` |
+| AI agent readiness for a content site | `agent-readiness`, `ai-readiness`, `entity-readiness`, `llms-txt-audit` |
+| AI search visibility and eligibility | `ai-readiness`, `geo-gaps`, `ai-referrals`, `seo-to-ai-query` |
 | Plan content from real demand | `query-clusters`, `page-opportunities`, `content-optimization`, `cannibalisation` |
 | Catch regressions over time | `technical-watch`, `crawl-diff`, `index-watch`, `measure-change` after a fix ships |
 | Client-ready reporting | `monthly-report`, `narrative-report`, `monthly-action-plan` |