Open-source SEO, GEO, and marketing skills for AI agents.
docs: strengthen SEO content guardrails
Tongba28a5032c6d
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex ea85e705..f4cf073b 100644--- a/.claude-plugin/marketplace.json+++ b/.claude-plugin/marketplace.json@@ -5,14 +5,14 @@},"metadata": {"description": "The official Google Ads + Meta Ads + SEO + GEO plugin from NotFair. SEO, GEO, Google Ads, and Meta Ads skills for Claude Code.",- "version": "0.25.3"+ "version": "0.25.4"},"plugins": [{"name": "notfair","source": "./","description": "The official Google Ads + Meta Ads + SEO + GEO plugin from NotFair. SEO analysis, Google Ads management, Meta (Facebook + Instagram) Ads management, GSC-driven content planning + local calendar viewer, keyword research, content optimization, schema markup, meta tags optimization, broken link checker, single-page deep audit, and Generative Engine Optimization for AI search.",- "version": "0.25.3",+ "version": "0.25.4","author": {"name": "NotFair","url": "https://notfair.co"diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex c0a017d7..ea689528 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "notfair",- "version": "0.25.3",+ "version": "0.25.4","description": "The official Google Ads + Meta Ads + SEO + GEO plugin from NotFair. SEO analysis, Google Ads management, Meta (Facebook + Instagram) Ads management, keyword research, content optimization, schema markup tools, broken link checker, single-page deep audit, and Generative Engine Optimization (GEO) for AI search engines — powered by Google Search Console, Google Ads, and Meta Marketing APIs.","author": {"name": "NotFair",diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 98e253d6..5dfacb72 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -11,6 +11,14 @@ The format follows [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).---+## [0.25.4] — 2026-05-28++### Changed++- Strengthened SEO content-quality guidance for compliance-sensitive claims, official-source citation requirements, internal links, and image asset validation.++---+## [0.25.3] — 2026-05-28### Removeddiff --git a/VERSION b/VERSIONindex 3d9dcb1b..35aa2f3c 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-0.25.3+0.25.4diff --git a/seo/content-writer/SKILL.md b/seo/content-writer/SKILL.mdindex ee65938f..b8c43821 100644--- a/seo/content-writer/SKILL.md+++ b/seo/content-writer/SKILL.md@@ -189,6 +189,16 @@ key phrases, tables for comparisons. One idea per paragraph.100 words, 1-2 H2s naturally, meta description. After that: synonyms and naturallanguage. No stuffing.+**Compliance-sensitive topics require official sources.** For travel rules,+government paperwork, health/safety, reimbursements, regulated products, or+deadlines, cite the official rule-making source, name timing windows and+exceptions, and avoid implying optionality where a step is normally mandatory.+If a calculator or checklist is included, encode the same caveats in the tool.++**Validate media assets.** Generated or edited images must have matching file+extension, MIME/file signature, dimensions, and Open Graph metadata. Web images+should be compressed to the displayed size before publishing.+### Deliverables for blog posts:1. Full post in markdown with heading hierarchy (H1 → H2 → H3), opening with ahook paragraph (not throat-clearing) and a table of contents that mirrors the@@ -272,6 +282,9 @@ written.- [ ] All inline images uploaded, alt text set, lazy-loaded below the fold- [ ] Table of contents renders with working anchor links- [ ] Internal links placed (both directions)+- [ ] Open Graph image added+- [ ] Open Graph image file format, dimensions, and byte size verified+- [ ] Official sources cited for compliance-sensitive claims- [ ] Canonical URL set to self- [ ] Mobile rendering verified```diff --git a/seo/content-writer/references/content-writing.md b/seo/content-writer/references/content-writing.mdindex daf999b5..c2bbd99b 100644--- a/seo/content-writer/references/content-writing.md+++ b/seo/content-writer/references/content-writing.md@@ -45,6 +45,29 @@ Google evaluates content on four axes:**YMYL topics** (health, finance, safety, legal) require the highest E-E-A-T bar.+### High-Stakes Factual & Compliance Topics+Some SEO topics are not legally YMYL but still create real-world risk if the+answer is wrong: travel requirements, government paperwork, animal welfare,+health certificates, military reimbursement, taxes/fees, regulated products, and+anything with official deadlines or eligibility rules.++For these topics, apply a compliance-quality gate before publishing:+- Link directly to the current official source for each rule-making body+ involved, such as government agencies, regulators, standards bodies, airlines,+ or program owners.+- Separate official requirements from professional planning advice. Do not use+ soft language like "may be required" for a normally mandatory step unless the+ official source actually defines meaningful exceptions.+- Name timing windows, exceptions, and scope boundaries explicitly. If guidance+ applies only to entry, import, export, one country, one state, or one program,+ do not generalize it to the reverse direction or adjacent workflows.+- Include a freshness caveat that tells readers to verify official guidance+ before booking, filing, buying, or traveling.+- If the page includes a calculator, estimator, or checklist, encode known rule+ adjustments and caveats in the tool itself, not only in surrounding prose.+- Treat unsourced compliance claims, ambiguous requirements, or missing official+ links as blockers, not polish items.+---## Helpful Content Signals@@ -215,6 +238,18 @@ list. Example:- Width: 1200px (featured), 800–1000px (inline), 2x for retina- Lazy-load every image except the featured one+### Media and Asset Quality+- Use real, relevant visual assets for published pages when the topic benefits+ from illustration, inspection, or trust. Avoid purely decorative stock-like+ images that do not help the reader understand the product, place, process, or+ outcome.+- Validate generated image files after export. The file extension, MIME/file+ signature, dimensions, and metadata declarations must agree.+- Keep hero images reasonably sized for web delivery. Prefer WebP/AVIF photos at+ the displayed aspect ratio; oversized multi-megabyte source images are a+ technical UX issue, not just an asset issue.+- Open Graph image dimensions in metadata must match the actual asset.+---## Landing Pages@@ -312,7 +347,9 @@ that format — don't fight the SERP.- [ ] Primary keyword in first 100 words naturally- [ ] Internal links to 3-5 related pages- [ ] Images have descriptive alt text+- [ ] Image file signatures, dimensions, and metadata match the published assets- [ ] URL is short, readable, includes keyword slug+- [ ] Compliance-sensitive claims are backed by official sources and scoped correctly### Should-Have- [ ] Structured data (Article, Product, Service, HowTo, FAQPage)diff --git a/seo/shared/seo-best-practices.md b/seo/shared/seo-best-practices.mdindex 937a21e9..4bf71e89 100644--- a/seo/shared/seo-best-practices.md+++ b/seo/shared/seo-best-practices.md@@ -88,12 +88,15 @@ Includes:- first-hand proof, examples, reviews, local details, pricing context- author/site trust signals where relevant- freshness only when substance changes+- official-source grounding and precise scope for regulated, safety, travel,+ reimbursement, health, or other compliance-sensitive topicsTypical actions:- add missing information users need to decide- replace generic copy with specific proof- add comparison, pricing, process, FAQs, or service-area details when useful- prune or merge thin/duplicative content+- fix ambiguous or unsourced compliance language before publishingDo not confuse with: metadata. If the page itself does not satisfy intent, title tweaks are lipstick.@@ -128,12 +131,15 @@ Includes:- intrusive interstitials/dialogs- ad or layout clutter- main-content clarity+- image asset correctness: actual format matches extension, dimensions match+ metadata, and images are compressed to the rendered sizeTypical actions:- improve LCP/INP/CLS bottlenecks- remove intrusive blockers- fix mobile layout issues- make primary content and CTA obvious+- convert oversized or mislabeled generated assets before publishingDo not confuse with: ranking magic. Perfect Lighthouse scores do not compensate for weak intent/content.