Skip to content

sergekostenchuk/seo-llm-skill-cluster / skills/seo-regression-validator

seo-regression-validator

Verified

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.

references/regression-checklist.md

View on GitHub
# SEO Regression Checklist

## Required Evidence

Every report should include:

- target URL or file path;
- fetched/read timestamp;
- method;
- status code or file status;
- user agent when fetched;
- checks run;
- critical findings;
- warnings;
- skipped checks.

## HTML Checks

Critical:

- title missing;
- meta description missing;
- canonical missing;
- duplicate canonical;
- JSON-LD missing on pages expected to have schema;
- invalid JSON-LD;
- NewsArticle.image missing or empty.

Warnings:

- hreflang missing;
- OpenGraph incomplete;
- Twitter card incomplete;
- RSS autodiscovery missing;
- viewport missing;
- article meta missing for article pages.

## Public Artifact Checks

When live URL access is available, also check:

- `/robots.txt`;
- `/llms.txt`;
- `/sitemap.xml`;
- `/news-sitemap.xml` when news exists;
- `/rss.xml` or feed URL;
- markdown alternate URLs when expected.

## Crawler Checks

Crawler allow/block conclusions require:

- current official crawler docs when bot-specific rules are discussed;
- fetched `robots.txt`;
- server/WAF evidence when available;
- caveat that robots policy is not the same as indexing, WAF, or crawler compliance.

## Performance Checks

If Lighthouse/PageSpeed is unavailable, record it as skipped. Do not invent Core Web Vitals.

## Result Semantics

- `pass`: check ran and expected evidence exists.
- `fail`: check ran and expected evidence is missing or invalid.
- `warning`: check ran and non-critical evidence is missing.
- `skipped`: check did not run; reason required.

rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall