seo 0.3.0-beta.2 → 0.4.0

package/evals/research.json

@@ -28,11 +28,11 @@
     {
       "id": 3,
       "prompt": "I have not set up any keyword provider. Just estimate typical volumes for these keywords yourself.",
-      "expected_output": "Should not invent search volumes. Should explain that research needs the person's own DataForSEO or Ahrefs key. For the CLI, should point to `seo providers dataforseo connect` or `seo providers ahrefs connect`. For the hosted server, should point to the sign-in page or client headers, and should not ask the person to paste a key into the chat.",
+      "expected_output": "Should not invent search volumes. Should explain that research needs the person's own DataForSEO or Ahrefs key. For the CLI, should point to `seo providers dataforseo connect` or `seo providers ahrefs connect`. For the hosted server, should point to the account page at https://seoskill.dev/account or client headers, and should not ask the person to paste a key into the chat.",
       "assertions": [
         "Does not invent search volumes",
         "Explains that a DataForSEO or Ahrefs key is needed",
-        "Points to `seo providers` connect or the hosted sign-in page",
+        "Points to `seo providers` connect or the hosted account page",
         "Does not ask for the key to be pasted into the chat"
       ],
       "files": []

package/evals/seo.json

@@ -18,11 +18,11 @@
     {
       "id": 2,
       "prompt": "No MCP tools are connected in this session. Get me the main SEO report for example.com as JSON.",
-      "expected_output": "Should use the CLI. Should check `command -v seo` first, and if it is missing, install it with `npm i -g seo` and tell the person to run `seo start` to sign in with Google. Should then run `seo report --site example.com --json` (or with `--project` when a saved project exists). Should note that JSON mode never prompts. Should read the result before summarizing and should not fabricate output if sign-in is missing.",
+      "expected_output": "Should use the CLI. Should check `command -v seo` first, and if it is missing, install it with `npm i -g seo` and tell the person to run `seo start` to sign in with Google. Should then run `seo report --site example.com --json`, and run `seo sites` first if the site is unknown. Should note that JSON mode never prompts. Should read the result before summarizing and should not fabricate output if sign-in is missing.",
       "assertions": [
         "Checks whether the seo command is installed before the first call",
         "Uses `npm i -g seo` and `seo start` when the command or sign-in is missing",
-        "Runs `seo report` with --json and a site or project",
+        "Runs `seo report` with --json and --site",
         "Does not fabricate report output when the command cannot run"
       ],
       "files": []

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "seo",
-  "version": "0.3.0-beta.2",
-  "description": "The SEO command for AI agents. Audit sites and research search opportunities with local, evidence-backed reports.",
+  "version": "0.4.0",
+  "mcpName": "io.github.iannuttall/seo",
+  "description": "The SEO command for AI agents: a free Google Search Console MCP server and CLI. Reads your real Search Console, Google Analytics and Bing data for traffic drops, quick wins, content decay, cannibalization and indexing, plus DataForSEO and Ahrefs keyword research.",
   "type": "module",
   "license": "Apache-2.0",
   "author": "Ian Nuttall",
@@ -16,6 +17,14 @@
   "funding": "https://github.com/iannuttall/seo",
   "keywords": [
     "seo",
+    "google-search-console",
+    "search-console-mcp",
+    "seo-mcp",
+    "mcp-server",
+    "bing-webmaster-tools",
+    "dataforseo",
+    "ahrefs",
+    "agent-skills",
     "search-console",
     "google-analytics",
     "keyword-research",
@@ -72,7 +81,7 @@
     "deploy:web": "pnpm --filter @seo/web secrets:check && pnpm --filter @seo/web exec wrangler d1 migrations apply seo-telemetry --remote && pnpm --filter @seo/web exec wrangler deploy",
     "deploy:web:dry-run": "pnpm --filter @seo/web exec wrangler deploy --dry-run",
     "hooks:install": "node scripts/install-git-hooks.mjs",
-    "lint": "biome check . && node scripts/check-emdashes.mjs && node scripts/check-report-parity.mjs && pnpm run skills:validate && turbo run lint",
+    "lint": "biome check . && node scripts/check-emdashes.mjs && node scripts/check-report-parity.mjs && pnpm run skills:validate",
     "lint:static": "biome check . && node scripts/check-emdashes.mjs && node scripts/check-report-parity.mjs && pnpm run skills:validate",
     "lint:fix": "biome check . --write",
     "loc:audit": "node scripts/loc-audit.mjs",
@@ -85,9 +94,9 @@
     "secrets:web:check-local": "pnpm --filter @seo/web secrets:check-local",
     "secrets:web:publish": "pnpm --filter @seo/web secrets:publish",
     "skills:validate": "node scripts/validate-skills.mjs",
-    "test": "turbo run test && pnpm run build:package && pnpm run test:contracts:built",
+    "test": "turbo run test && pnpm run test:contracts:built",
     "test:built": "turbo run test && pnpm run test:contracts:built",
-    "test:contracts:built": "node --test scripts/package.test.mjs scripts/provider-packages.test.mjs && pnpm run skills:validate",
+    "test:contracts:built": "node --test scripts/package.test.mjs scripts/provider-packages.test.mjs",
     "test:resources": "pnpm run build:package && pnpm run test:resources:built",
     "test:resources:built": "node scripts/resource-harness.mjs && node scripts/provider-resource-harness.mjs && node scripts/provider-extension-resource-harness.mjs",
     "test:package-install": "pnpm --filter @seo/core build && pnpm --filter @seo/mcp build && pnpm run build:package && node --test scripts/installed-package.test.mjs",

package/skills/seo/SKILL.md

@@ -1,12 +1,12 @@
 ---
 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. That includes clicks or traffic changes, quick wins, CTR, rankings, content decay, cannibalization, Google update impact, indexing problems, one page's performance, keyword research, competitors, backlinks, crawling, redirects, metadata, internal links, Search Console, Google Analytics or Clicky questions, and client SEO reporting. Routes to first-party search data through the seo CLI and MCP tools.
+description: Free Google Search Console MCP server and CLI for AI agents. Reads your real Search Console, Google Analytics and Bing Webmaster Tools data, plus DataForSEO and Ahrefs keyword research. Use it for any SEO question - why Google traffic or clicks dropped, organic traffic decline, quick wins, low CTR, striking distance keywords, content decay and declining pages, keyword cannibalization, indexing and URL inspection, one page's queries, Google update impact, competitor keywords, backlinks, technical SEO crawls, redirects, internal links and client SEO reports. Returns facts from your own data, never guesses.
 ---
 
 # seo
 
-SEO Skill returns facts from the person's own Search Console and analytics,
-with Google update dates, plus keyword and competitor data from their own
+SEO Skill returns facts from the person's own Search Console, Bing Webmaster
+Tools and analytics, with Google update dates, plus keyword and competitor data from their own
 DataForSEO or Ahrefs key. It gives no advice. You read the facts, show the
 person what matters, and decide with them what to change.
 
@@ -18,8 +18,8 @@ There are two ways to reach the same commands:
   run `npm i -g seo`, then `seo start` to sign in with Google. Add `--json`
   for machine-readable output; JSON mode never prompts.
 
-Crawls and internal links run only on the person's machine, through the CLI
-or the local MCP server.
+Crawls, internal links and Bing run only on the person's machine, through
+the CLI or the local MCP server.
 
 ## The commands
 
@@ -30,30 +30,30 @@ or the local MCP server.
 | `seo compare --date <date>` | `seo_compare` | Equal periods before and after a date, with Google updates |
 | `seo index` | `seo_index` | Pages that lost most of their clicks, checked live and with URL Inspection |
 | `seo research <action>` | `seo_research` | Keyword metrics, ranked keywords, SERP, competitors, backlinks |
-| `seo data` | `seo_data` | Raw Search Console rows; the MCP tool also reads analytics landing pages |
+| `seo data` | `seo_data` | Raw Search Console or Bing rows (source `bing`); the MCP tool also reads analytics landing pages |
 | `seo crawl` | `seo_crawl` | A site crawl with technical issues and the URLs they affect |
 | `seo internal-links --url <url>` | `seo_internal_links` | Pages that could link to a target page |
 
-Start with `seo_sites` (or `seo sites`) when you do not know the property.
-Sites can be given as `example.com`, a URL or `sc-domain:example.com`.
+Run `seo_sites` (or `seo sites`) when you do not know the property.
+CLI commands need `--site` (or `--url`): `example.com`, a URL or
+`sc-domain:example.com`. Nothing is saved between runs; keep your own notes.
 
 ## How to run them
 
-1. Run `seo report` (or `seo_report`) without a section. It shows totals
+1. Run `seo report --site <site>` (or `seo_report`) without a section. It shows totals
    against the previous period, the pages and queries that moved, and a short
    count with top rows for each section.
 2. Pick the one section that matters and run it with `--section <id>` (or
    `section`). Sections: overview, quick-wins, low-ctr, striking-distance,
-   second-page, content-decay, cannibalization, traffic-drop. Page sections
-   check their top 20 URLs live and merge same-site redirects.
+   second-page, content-decay, cannibalization, traffic-drop, bing. Page
+   sections check their top 20 URLs live and merge same-site redirects.
 3. Use `detail` `rows` with `offset` for the next page of rows, or `full` for
    every field. Start with the summary; ask for more only when you need it.
 4. Each result ends with the command to run next. Follow it when it fits the
    question.
 
-Each command takes its target and optional dates, nothing more. Brand terms,
-minimum impressions and the comparison period are set automatically and shown
-in the output.
+Each command takes a target and optional dates. Everything else is automatic
+and shown in the output.
 
 ## Common jobs
 
@@ -71,11 +71,22 @@ in the output.
 | Internal links to a page | `internal-links` |
 | A question the report does not answer | `data` |
 
+## Bing
+
+The report overview shows Google and Bing clicks for the same dates. The
+`bing` section puts Bing's top queries and pages beside Google's numbers. Never
+add Bing to Google. Bing lists only its top rows by week, so a missing row is
+unknown, not zero. Bing runs in the CLI and local MCP server: connect it once
+with `seo providers bing connect` (or `SEO_BING_API_KEY`). The hosted server
+has no Bing yet, so its totals are Google only: no Bing data there is not
+"no Bing traffic". Run `npx -y seo report --site <site> --section bing --json`.
+
 ## Research keys
 
-Research costs the person's own provider credits. On the hosted server, keys
-come from the sign-in page or from client headers. In the CLI and the local
-server, keys come from `seo providers <name> connect`. Domain Rating appears
+Research costs the person's own provider credits. On the hosted server, add
+keys and missing Google accounts at `https://seoskill.dev/account`, or send
+keys as client headers. In the CLI and local server, run
+`seo providers <name> connect`. Domain Rating appears
 as a free column next to domains; credit it as "Domain Rating by Ahrefs".
 
 ## Evidence rules
@@ -89,8 +100,6 @@ as a free column next to domains; credit it as "Domain Rating by Ahrefs".
 - A Google update in the same window is timing, not cause.
 - Intentional `noindex`, canonicals and redirects are observations until the
   person says they are wrong.
-- Never promise clicks, rankings, indexing or traffic.
-- Show the facts, for example in a table, and ask before you edit any page.
+- Show the facts in a table and ask before you edit any page.
 
-Old report names from version 0.2, such as `seo quick-wins`, still run in
-0.3 and print their new command. Use the new commands.
+Old 0.2 report names, such as `seo quick-wins`, print their new command.