seo-regression-validator
Validate SEO and LLM-readability claims against live HTML, local fixtures, and generated artifacts. Use this skill when the user asks to prove whether title, meta description, canonical, hreflang, JSON-LD, NewsArticle.image, OpenGraph, Twitter cards, RSS autodiscovery, robots.txt, llms.txt, sitemap, news-sitemap, crawler access, or performance evidence is actually present, and when subjective audits must become timestamped pass/fail reports.
- License 许可
- MIT
- 最近更新
- 2026-06-12
- Stars
- ★ 40
- Forks
- 4
01 前言 Front Matter
- name
- seo-regression-validator
- description
- Validate SEO and LLM-readability claims against live HTML, local fixtures, and generated artifacts. Use this skill when the user asks to prove whether title, meta description, canonical, hreflang, JSON-LD, NewsArticle.image, OpenGraph, Twitter cards, RSS autodiscovery, robots.txt, llms.txt, sitemap, news-sitemap, crawler access, or performance evidence is actually present, and when subjective audits must become timestamped pass/fail reports.
02 资源文件 9
- 参考文档agents/openai.yaml388 B
- 参考文档evals.json1.8 KB
- 参考文档fixtures/bad-news.html483 B
- 参考文档fixtures/bad-news.report.json2.3 KB
- 参考文档fixtures/good-news.html2.2 KB
- 参考文档fixtures/good-news.report.json1.1 KB
- 参考文档references/regression-checklist.md1.5 KB
- 脚本scripts/audit_static_seo.py9.7 KB
- 参考文档validation-report.md1.9 KB
03 SKILL.md 正文
SEO Regression Validator
Use this skill after technical SEO/schema guidance exists, before claiming a site or skill output is done.
Read references/regression-checklist.md before running a broad audit.
Owns
- live HTML and local fixture checks;
- pass/fail severity model;
- timestamped evidence reports;
- schema/head metadata checks;
- public artifact reachability checks;
- regression report templates;
- negative tests for missing JSON-LD, duplicate canonical, missing image, and fake reports.
Does Not Own
- implementing SEO fixes;
- Search Console credentialed data;
- analytics exports;
- external authority placement;
- mutating target websites.
Workflow
- Define target URLs or fixture files.
- Record timestamp, target, method, and user agent.
- Fetch or read the target without mutation.
- Run deterministic checks using scripts/audit_static_seo.py when HTML is available.
- Separate critical failures, warnings, and skipped checks.
- Record skipped checks instead of treating them as passes.
- Produce or update
seo-regression-report.jsonand a human-readable validation summary. - Route implementation fixes to the appropriate specialist.
Critical By Default
- missing
<title>; - missing meta description;
- missing or duplicate canonical;
- no JSON-LD on pages expected to have schema;
- invalid JSON-LD;
- NewsArticle without usable image;
- public page blocked or unreachable during live check;
- report claims success without fetching or reading target.
Warning By Default
- missing hreflang when a multilingual equivalent is expected;
- missing OG/Twitter social tags;
- missing RSS autodiscovery;
- missing viewport;
- article meta tags missing when an article schema exists;
- no visible breadcrumb when BreadcrumbList is expected;
- performance metrics not measured.
Safety And Privacy Boundaries
- Do not mutate target sites.
- Do not use credentials unless the user explicitly provides them for this task.
- Do not store cookies, tokens, raw private analytics, raw IP logs, or private Search Console rows in reports.
- Do not claim ranking, indexing, citation, or crawler behavior from one HTML check.
Validation
Validate skill edits with:
python3 <codex-skills-dir>/senior-skill-architect/scripts/lint_production_skill.py ./skills/seo-regression-validator
python3 ./skills/seo-regression-validator/scripts/audit_static_seo.py ./skills/seo-regression-validator/fixtures/good-news.html
python3 ./plans/seo-llm-skill-cluster/scripts/lint_skill_cluster.py .
Forward tests live in evals.json.
Output Shape
Return:
- Targets checked.
- Critical findings.
- Warnings.
- Skipped checks.
- Evidence paths or URLs.
- Implementation owner for each fix.
04 同仓库更多 Skills
ux-journey-architect
Map user journeys, onboarding paths, entry points, first actions, trust points, accessibility risks, and SEO/LLM handoffs for public websites without redesigning the visual system. Use this skill when the user asks how new readers, returning users, project reviewers, community members, buyers, or AI agents should move through a site and what each page must make clear before layout implementation.
technical-seo-schema-engineer
Design deterministic technical SEO and schema.org guidance for crawlable public pages. Use this skill when the user asks for title and meta description rules, canonical and hreflang tags, JSON-LD schema, NewsArticle, Article, TechArticle, BreadcrumbList, WebSite, Organization, Person, OpenGraph, Twitter cards, sitemap, news-sitemap, RSS, robots.txt, llms.txt, publisher logo, ImageObject, or metadata templates that must match visible content.
site-growth-orchestrator
Coordinate SEO, LLM-readable site architecture, UX, content, monitoring, security, and external authority work as a task-plan-driven sequence. Use this skill when the user asks to plan, execute, validate, or route multi-skill website growth work; asks what to do next across semantic core, URL structure, internal linking, schema, llms.txt, UX journeys, analytics, citation monitoring, or white-hat link placement; or wants a central architect that preserves evidence, alarms, handoffs, and tests.
server-log-crawler-analyst
Analyze credential-free public website monitoring evidence from server access logs, HTTP fetches, robots/llms/sitemap checks, and exported summaries while protecting raw IP and private query data. Use this skill when the user asks whether crawlers or AI bots reached a site, whether public SEO/LLM discovery files respond, or how to separate observed facts from unknown Search Console, rank, analytics, or citation claims.
semantic-core-architect
Build evidence-labeled semantic cores for SEO, LLM-readable architecture, and site information design. Use this skill when the user asks for semantic core, query clusters, search intents, audience segments, entity/topic maps, language or locale priorities, competitor/source evidence, pillar-topic planning, or a structured handoff before URL architecture and internal linking. It must mark unknown search volume, difficulty, and ranking data as unknown instead of inventing metrics.
llm-friendly-site-architect
Design human-visible, machine-readable website layers for AI assistants, RAG, and agentic search. Use this skill when the user asks for llms.txt, LLM discovery plans, visible TLDR or direct-answer blocks, source trails, entity pages, markdown alternates, AI crawler policy, topic-to-URL maps, assistant-readable public content, or LLM-friendly architecture that must preserve canonical SEO strategy without hidden bot-only facts or duplicate story bodies.