@seoagent-official/seoagent 1.94.0 → 1.95.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seoagent-official/seoagent",
-  "version": "1.94.0",
+  "version": "1.95.1",
   "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/writing-rules.md

@@ -4,6 +4,10 @@ Prose-craft rules for EVERY article, landing page, brief, and rewrite this skill
 
 These rules also ship inside cloud-generated briefs as a "## Writing rules (no AI slop)" section. When a brief carries that section, it is the same contract as this file — don't apply the rules twice, just follow them.
 
+## Language
+
+Write in the site's language — the `language:` value in `project.md` (`nl`, `da`, `de`, `en-GB`…). It applies to everything: headings, meta title and description, FAQ, image alt text, slug words. Brand and product names stay as they are. Cloud briefs carry the same instruction as a `Language:` line in their site context. If `project.md` says `en` but the live site is plainly not in English, fix `project.md` first (`seoagent init` guesses it from the domain's ccTLD; a `.com` site in Dutch needs `language: nl` by hand, an English site on `.nl` needs `language: en-NL`) — the cloud uses that value for keyword data too.
+
 ## Banned words
 
 Never use: delve, foster, leverage, utilize, facilitate, empower, streamline, robust, cutting-edge, paradigm shift, game changer, "this is huge", "this changes everything", tapestry, realm, beacon, multifaceted, meticulous, intricate, paramount, transformative, elevate, embark, supercharge, harness, ever-evolving.

package/skills/seoagent.md

@@ -158,7 +158,7 @@ Then per article in priority order: read the cluster file for role and metadata;
 ## Phase 4 — Article writing
 
 1. Read the brief, `context.md` (tone, audience, banned topics), and the cluster file for link targets.
-2. **Read the page-type reference** (plus `listicle-articles.md` for listicles, `schema-markup.md` for JSON-LD) and **`references/writing-rules.md`** — apply its prose rules while drafting and run its self-check before publishing.
+2. **Read the page-type reference** (plus `listicle-articles.md` for listicles, `schema-markup.md` for JSON-LD) and **`references/writing-rules.md`** — apply its language and prose rules while drafting; self-check before publishing.
 3. **Write the body where it actually renders — one source of truth.** Which file that is, plus screenshots and the never-block-on-images rule, is in `references/publishing.md`.
 4. **Update the link graph** — sub-pillar and long-tail writes link UP to the parent; pillar writes reference all sub-pillars. Then sync.