@seoagent-official/seoagent 1.48.0 → 1.50.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.48.0",
-  "description": "Scaffolder for Claude Code's SEOAgent skill. Run once: `npx -y @seoagent-official/seoagent init`. Sets up .seoagent/ for persistent audits, keyword strategy, content planning, and optimized writing. Not a runtime dependency.",
+  "version": "1.50.0",
+  "description": "The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.",
   "type": "module",
   "bin": {
     "seoagent": "index.js"
@@ -11,6 +11,9 @@
     "skills",
     "assets"
   ],
+  "engines": {
+    "node": ">=18"
+  },
   "dependencies": {
     "@anthropic-ai/claude-agent-sdk": "^0.1.0",
     "@clack/prompts": "^0.9.0",
@@ -21,13 +24,31 @@
   },
   "keywords": [
     "seo",
+    "seo-agent",
+    "agentic-seo",
     "claude-code",
+    "claude-skill",
+    "claude-agent",
     "ai-agent",
+    "ai-seo",
+    "aeo",
+    "geo",
+    "answer-engine-optimization",
+    "generative-engine-optimization",
     "seo-audit",
+    "seo-cli",
     "content-strategy",
-    "keyword-research"
+    "keyword-research",
+    "internal-links",
+    "schema-markup",
+    "autopilot"
   ],
   "license": "MIT",
+  "homepage": "https://seoagent.com",
+  "bugs": {
+    "url": "https://github.com/Baxter-Inc/seoagent-npm/issues"
+  },
+  "funding": "https://seoagent.com/pricing",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/Baxter-Inc/seoagent-npm.git"

package/skills/references/open-knowledge-format.md

@@ -0,0 +1,74 @@
+# Open Knowledge Format (OKF) Bundle
+
+OKF is an open standard Google published in 2026 (spec + reference code at `github.com/GoogleCloudPlatform/knowledge-catalog/okf`) for packaging an organization's knowledge as a directory of **markdown files with YAML frontmatter**, designed for AI agents and answer engines to read directly. It is vendor-neutral, human-readable, and version-controlled like code — think of it as a wiki written for machines.
+
+**Why it matters for SEO:** a growing share of search happens inside AI assistants (ChatGPT, Claude, Perplexity) and Google's AI Overviews. Being understood and cited there is **Answer Engine Optimization (AEO / GEO)**. An OKF bundle gives those models a curated, trustworthy account of the business instead of leaving them to guess from scraped pages. SEOAgent is uniquely positioned to produce it because the knowledge already lives in `.seoagent/` (business context, strategy, published content).
+
+This file is the protocol for generating and maintaining a site's OKF bundle. The deterministic parts (scaffold + validate) are CLI commands; **you** write the bundle content by mapping `.seoagent/` artifacts into OKF files.
+
+## Where the bundle lives
+
+`.seoagent/okf/` — it syncs to the cloud like the rest of `.seoagent/`. The user publishes it themselves at `/.well-known/okf/` or `/okf/` on their site (or links it from `llms.txt`).
+
+## Frontmatter rules
+
+Every `.md` file MUST have YAML frontmatter with:
+
+- **`type`** (required) — the only mandatory field. Use one of: `Organization`, `Concept`, `Topic`, `FAQ`, `Article`, `Service`, `Metric`, `Log`.
+
+Recommended optional fields:
+
+- `title` — human-readable name
+- `description` — one or two sentences, ≤ 200 characters
+- `resource` — canonical URL of the real asset (e.g. the live article/page)
+- `tags` — list, e.g. `[pricing, plans]`
+- `timestamp` — ISO-8601, e.g. `2026-05-28T14:30:00Z`
+
+Cross-link concepts with **relative markdown links only** (`[Pricing](concepts/pricing.md)`) — every link must resolve to a file in the bundle. Reserved files: `index.md` (entry point / progressive disclosure) and `log.md` (chronological change history).
+
+## Bundle layout — map `.seoagent/` → OKF
+
+```
+.seoagent/okf/
+├── index.md          # type: Organization — business overview, links to everything
+├── log.md            # type: Log — chronological change history
+├── concepts/         # type: Concept | Topic | Service
+│   ├── pricing.md
+│   └── <keyword-cluster-or-entity>.md
+├── faqs/             # type: FAQ — one answer-engine Q&A per file
+│   └── what-is-x.md
+└── articles/         # type: Article — published pages, resource = live URL
+    └── guide-to-x.md
+```
+
+| OKF file | `type` | Source in `.seoagent/` |
+|---|---|---|
+| `index.md` | `Organization` | `project.md` (domain) + `context.md` (business description) |
+| `concepts/*.md` | `Concept` / `Topic` / `Service` | `strategy/clusters/*` keyword clusters; core services/entities from `context.md` |
+| `faqs/*.md` | `FAQ` | Questions answered in briefs/content; "People Also Ask" items |
+| `articles/*.md` | `Article` | Each `content/*` article — set `resource:` to its live URL, summarize the key facts |
+| `log.md` | `Log` | Append a dated line whenever you regenerate the bundle (mirror `changelog.md`) |
+
+## Generation protocol
+
+1. Run `seoagent okf scaffold` to create the directory skeleton (`index.md` + `log.md`) — it never overwrites existing files.
+2. Fill `index.md` from `.seoagent/context.md` and `project.md`: what the business does, who it serves, then a linked list of the concept / FAQ / article files.
+3. For each keyword cluster in `.seoagent/strategy/clusters/`, write a `concepts/<slug>.md` (`type: Concept` or `Topic`) capturing the definitive, factual explanation — not marketing fluff. Stats, definitions, and comparisons are what AI cites.
+4. For each clear question the business answers, write a `faqs/<slug>.md` (`type: FAQ`): the question as the title, a tight factual answer in the body.
+5. For each published article in `.seoagent/content/`, write `articles/<slug>.md` (`type: Article`) with `resource:` set to the live URL and a 2–4 sentence factual summary; cross-link related concepts.
+6. Add a dated entry to `log.md`.
+7. Run `seoagent okf validate` and fix every error (missing `type`, bad `timestamp`, broken link) before finishing.
+8. Sync runs automatically (or `seoagent sync`) so the bundle reaches the cloud dashboard.
+
+## Quality bar
+
+- Write for a model, not a brochure: lead with facts, numbers, and definitions. Avoid superlatives and CTAs.
+- One concept per file; keep files focused and cross-linked.
+- Keep `resource:` URLs canonical and live — they are how an agent verifies and cites you.
+- Regenerate when content changes so the bundle never drifts from reality.
+
+## CLI commands
+
+- `seoagent okf` — status (is a bundle present? how many files?)
+- `seoagent okf scaffold` — create the starter `index.md` + `log.md`
+- `seoagent okf validate` — assert every file has `type`, timestamps are ISO-8601, and all relative links resolve

package/skills/seoagent.md

@@ -1,6 +1,6 @@
 ---
 name: seoagent
-description: "Persistent AI SEO agent. ALWAYS use when the user mentions: SEO, ranking, rank, keywords, meta tags, search traffic, organic traffic, content strategy, audit, Google, Bing, Search Console, GSC, schema markup, JSON-LD, sitemap, robots.txt, internal linking, AI search, AEO, GEO, alt text, page speed, Core Web Vitals, slug, URL structure, canonical, breadcrumbs, hub and spoke, pillar content, topic cluster, programmatic SEO, landing page SEO, blog SEO, why am I not ranking. Also use SILENTLY when the user asks to write, edit, or improve a blog post, landing page, marketing copy, or any file under content/, posts/, blog/, pages/ — these are SEO-adjacent and should persist to .seoagent/ even without an explicit invocation. Replaces separate seo-audit, content-strategy, programmatic-seo, ai-seo, site-architecture, and schema-markup skills with one unified, persistent workflow."
+description: "Persistent AI SEO agent. ALWAYS use when the user mentions: SEO, ranking, rank, keywords, meta tags, search traffic, organic traffic, content strategy, audit, Google, Bing, Search Console, GSC, schema markup, JSON-LD, sitemap, robots.txt, internal linking, AI search, AEO, GEO, OKF, Open Knowledge Format, AI knowledge bundle, llms.txt, alt text, page speed, Core Web Vitals, slug, URL structure, canonical, breadcrumbs, hub and spoke, pillar content, topic cluster, programmatic SEO, landing page SEO, blog SEO, why am I not ranking. Also use SILENTLY when the user asks to write, edit, or improve a blog post, landing page, marketing copy, or any file under content/, posts/, blog/, pages/ — these are SEO-adjacent and should persist to .seoagent/ even without an explicit invocation. Replaces separate seo-audit, content-strategy, programmatic-seo, ai-seo, site-architecture, and schema-markup skills with one unified, persistent workflow."
 allowed-tools: Read, Write, Edit, Bash, WebFetch, WebSearch
 ---
 
@@ -33,6 +33,7 @@ This SKILL.md is the orchestration layer. Detailed protocols live in `references
 | Programmatic SEO at scale | `references/programmatic.md` |
 | Adding schema markup / JSON-LD | `references/schema-markup.md` |
 | Refreshing or rewriting an existing page | `references/rewrite-protocol.md` |
+| Generating/publishing an OKF bundle for AI agents (AEO/GEO) | `references/open-knowledge-format.md` |
 
 Loading the right reference makes outputs dramatically better. Don't skip it.
 
@@ -697,6 +698,21 @@ If the article already exists, **read `references/rewrite-protocol.md`** instead
 
 ---
 
+## Phase 6: Publish an OKF Knowledge Bundle (AEO/GEO)
+
+When the user asks to "publish an OKF bundle", "make my site AI-readable", "get cited by ChatGPT / Claude / Perplexity", "Open Knowledge Format", or "AEO / GEO", produce an OKF bundle that AI agents can read to understand and cite the business.
+
+**Read `references/open-knowledge-format.md` first** — it has the full frontmatter rules, the `.seoagent/` → OKF mapping table, and the quality bar. Then:
+
+1. `npx @seoagent-official/seoagent okf scaffold` — create the `.seoagent/okf/` skeleton.
+2. Fill the bundle by mapping `.seoagent/` artifacts → OKF files (`index.md` from `context.md`/`project.md`; `concepts/*` from strategy clusters; `faqs/*`; `articles/*` from `content/` with `resource:` set to the live URL).
+3. `npx @seoagent-official/seoagent okf validate` — fix every error (missing `type`, bad `timestamp`, broken link).
+4. Tell the user to publish the bundle at `/.well-known/okf/` or `/okf/` on their site (or link it from `llms.txt`). Sync pushes it to the cloud automatically.
+
+This is the AEO/GEO complement to schema markup: schema describes a single page in HTML; the OKF bundle describes the whole business for agents to load wholesale.
+
+---
+
 ## File Schemas Reference
 
 ### `.seoagent/project.md`