@seoagent-official/seoagent 1.58.0 → 1.60.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@seoagent-official/seoagent",
3
- "version": "1.58.0",
3
+ "version": "1.60.0",
4
4
  "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.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -220,6 +220,8 @@ Offer **once per session per topic**; if declined, drop it and keep working. Nev
220
220
 
221
221
  **Every session starts here.** Before doing any SEO work:
222
222
 
223
+ 0. **Run `seoagent doctor` first** (when `.seoagent/` exists). It's a fast, local health check that surfaces exactly what the steps below ask you to remember — an untriaged pull receipt, `domain`/`site_type: unknown`, and an image-provider key that's present but not enabled. Use `seoagent doctor --json` if you want to branch on the findings programmatically. Treat each `action` finding as a to-do for the steps below; if it reports healthy, continue. This is the deterministic backstop so none of the checks get skipped.
224
+
223
225
  1. Check if `.seoagent/project.md` exists.
224
226
  - **If yes**: Read it (frontmatter has `domain`, `site_type`, optional `image_provider`, optional `publishing`). Read `.seoagent/roadmap.md` if present. Summarize in one sentence: "You have an SEO project for {domain}. Next priority: {top item from roadmap}."
225
227
  - **If no**: Check the repo for signals to infer domain and site type, then create the project files.
@@ -765,7 +767,7 @@ When the user asks to "publish an OKF bundle", "make my site AI-readable", "get
765
767
  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).
766
768
  3. `seoagent okf validate` — fix every error (missing `type`, bad `timestamp`, broken link).
767
769
  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.
768
- 5. **Measure it.** The OKF bundle makes the business _citable_ — `seoagent citations` checks whether it's _working_. It runs buyer-intent queries through the Claude Agent SDK with live web search and writes `.seoagent/citations/scorecard.md` (which queries surface the business, and where it's missing). Run it after publishing, and again periodically to watch the trend. When the user asks "am I getting cited by AI?", "measure my AI visibility", or "is the OKF bundle working?", this is the command. It's a web-grounded proxy for ChatGPT/Perplexity/AI Overviews — directional, not a per-engine guarantee.
770
+ 5. **Measure it.** The OKF bundle makes the business _citable_ — `seoagent citations` checks whether it's _working_. It runs buyer-intent queries through the Claude Agent SDK with live web search and writes `.seoagent/citations/scorecard.md` (which queries surface the business, and where it's missing). It's a real **tracker**, not a one-shot read: every run is saved to `.seoagent/citations/history/<ts>.json` and the scorecard shows the **trend** vs the last run, the **URL each engine cited** per query (theirs when the business loses — so you know what to beat), and a competitor **share-of-voice** table when you pass `seoagent citations --competitors "Frase,Otterly"` (or set a `competitors:` line in `context.md`). Run it after publishing, and again on a cadence to watch the trend. When the user asks "am I getting cited by AI?", "measure my AI visibility", "how do I compare to a competitor in AI answers?", or "is the OKF bundle working?", this is the command. It's a web-grounded proxy for ChatGPT/Perplexity/AI Overviews — directional, not a per-engine guarantee.
769
771
 
770
772
  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 — and `seoagent citations` closes the loop by measuring whether answer engines actually cite it.
771
773