@seoagent-official/seoagent 1.107.1 → 1.107.2

package/index.js

@@ -724,9 +724,10 @@ ${Ol(t)}
    \u2192 product or comparison; \`informational\` \u2192 guide or pillar; \`navigational\` \u2192
    probably already covered elsewhere).
 2. Pick a URL slug from the keyword \u2014 short, hyphenated, no stop words.
-3. Look at \`.seoagent/keywords.md\` for related keywords already in this site's
-   strategy so you can group this new page into the right cluster and weave in
-   the cluster's other keywords as secondaries.
+3. Look at this site's keyword inventory for related keywords already in its
+   strategy \u2014 \`.seoagent/strategy/keywords/<cluster>.md\` once the cloud shards
+   them, \`.seoagent/keywords.md\` otherwise \u2014 so you can group this new page into
+   the right cluster and weave in the cluster's other keywords as secondaries.
 4. **Write the article** following the skill's **content-production protocol**
    (Phase 4 \u2014 match the article type's quality rules, add internal links, etc.).
    Show the user the draft before publishing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.107.1",
+  "version": "1.107.2",
   "description": "The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, real product screenshots from your repo, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.",
   "type": "module",
   "bin": {

package/skills/references/inbox.md

@@ -90,7 +90,7 @@ Start by reading `.seoagent/inbox/README.md` (or `seoagent inbox`) to see the li
 ### `cli_new_landing_page-<id>.md`
 
 - `Read` it. The frontmatter has `action_id`, `keyword`, `opportunity` (`easy_win` | `competitor_gap`), `volume`, `difficulty`, and `intent`. The body explains why this keyword is worth a page.
-- Cross-reference `.seoagent/keywords.md` for related keywords — they tell you which cluster this page belongs to and which secondary keywords to weave in.
+- Cross-reference the site's keyword inventory for related keywords — they tell you which cluster this page belongs to and which secondary keywords to weave in. It is `.seoagent/strategy/keywords/<cluster>.md` (plus `unclustered.md`) once the cloud shards it, and `.seoagent/keywords.md` otherwise; a synced workspace usually has only one of the two.
 - Pick an article type from `intent` (commercial/transactional → product or comparison page; informational → guide or pillar). Pick a clean URL slug from `keyword`.
 - Write the article following the content-production protocol (Phase 4 — match the article type's quality rules, add internal links from related cluster pages, etc.). Show the user the draft before publishing (interactive sessions can use the visual review loop — `references/draft-review.md`).
 - **If the action body has a "Screenshots to capture" section** (SaaS product), follow `references/screenshots.md` — a landing page for a SaaS product should lead with a real product screenshot in the hero + feature sections, captured from this repo's UI.