Skip to content

seo-skills/seo-audit-skill

seo-audit

Verified

Run the SEOmator CLI on a site and score it against 398 rules across 20 categories (SEO, technical, content, security, JS rendering, AI readiness), with reports an LLM can act on. It can also diff two audits to show what a deploy changed. Reach for it to find out why a site underperforms in search, to review a site's health, or to check a release before and after.

references/rules.md

View on GitHub
# SEOmator Audit Rules Reference

<!-- Updated: 2026-09-01 -->

SEOmator ships **398 rules across 20 weighted categories**. Category weights
sum to exactly 100. Each rule returns `pass` (100), `warn` (50), or `fail` (0);
the category score is the average of its rule results weighted by each rule's
declared `weight`, and the overall score is the weighted average of category
scores.

A check whose input could not be measured (for example Core Web Vitals without
`--cwv`) is reported with weight 0, so it appears in the report but affects
neither side of the average.

## Categories & Weights

| Category ID | Name | Weight | Rules | Covers |
|-------------|------|--------|-------|--------|
| `core` | Core | 11% | 27 | Title, meta description, canonical, viewport, favicon, H1, lang |
| `perf` | Performance | 10% | 30 | LCP, INP, CLS, TTFB, FCP, render-blocking resources, compression |
| `links` | Links | 8% | 27 | Broken links, anchor text, internal linking, nofollow; click depth and inbound links need `--crawl` |
| `images` | Images | 8% | 15 | Alt text, dimensions, lazy loading, WebP/AVIF, srcset, file size |
| `security` | Security | 8% | 26 | HTTPS, HSTS, CSP, X-Frame-Options, mixed content, SSL, leaked secrets, cookie flags |
| `technical` | Technical SEO | 7% | 19 | robots.txt, sitemap, URL hygiene, www redirect, custom 404 |
| `crawl` | Crawlability | 5% | 39 | noindex, robots directives, sitemap coverage, lastmod quality, redirect chains |
| `schema` | Structured Data | 5% | 19 | JSON-LD presence/validity, required fields, deprecated types |
| `content` | Content | 5% | 27 | Word count, thin content, readability, duplicate content |
| `js` | JavaScript Rendering | 5% | 17 | CSR vs SSR, rendered-DOM diff, JS-dependent content, console errors, failed requests |
| `a11y` | Accessibility | 7% | 46 | ARIA, contrast, form labels, skip links, focus management |
| `social` | Social | 3% | 13 | Open Graph, Twitter Card, og:image validity |
| `eeat` | E-E-A-T | 3% | 16 | Author bylines, dates, about/contact pages, external citations |
| `url` | URL Structure | 3% | 14 | Lowercase, hyphens, length, parameters, trailing slash |
| `redirect` | Redirects | 3% | 11 | Chains, loops, 302-vs-301, meta refresh |
| `mobile` | Mobile | 2% | 13 | Viewport, font sizes, tap spacing, mobile-first parity (content, title, canonical, structured data, links) |
| `i18n` | Internationalization | 2% | 13 | hreflang validity, x-default, lang attributes |
| `htmlval` | HTML Validation | 2% | 12 | Duplicate IDs, deprecated tags, DOCTYPE, encoding |
| `geo` | AI/GEO Readiness | 2% | 13 | AI crawler access, llms.txt, citability structure |
| `legal` | Legal Compliance | 1% | 1 | Privacy policy presence |

## Rule ID Convention

Rule IDs follow `<category>-<descriptive-name>`, e.g. `core-canonical-conflicting`,
`cwv-lcp`, `security-hsts`, `geo-llms-txt`. IDs are self-describing; the LLM report
format includes the rule message and a fix suggestion alongside each failing rule.

## Score Interpretation

| Overall Score | Grade | Meaning |
|---------------|-------|---------|
| 90–100 | A | Excellent — minor optimizations only |
| 80–89 | B | Good — address warnings |
| 70–79 | C | Fair — several issues to fix |
| 50–69 | D | Needs work — priority fixes required |
| <50 | F | Poor — critical issues to resolve |

## Listing Rules at Runtime

The authoritative rule list lives in the installed package. To enumerate rules for a
category, run `seomator explain --list <category>` (`seomator explain <rule-id>`
says what one rule checks), read the category's `index.ts` in the SEOmator source
(`src/rules/<category>/index.ts`) or run an audit and inspect per-rule results in
`--format json` output.

## Core Web Vitals Thresholds (used by `perf` rules)

| Metric | Pass | Warn | Fail |
|--------|------|------|------|
| LCP | ≤2.5s | 2.5–4s | >4s |
| INP | ≤200ms | 200–500ms | >500ms |
| CLS | ≤0.1 | 0.1–0.25 | >0.25 |
| TTFB | ≤800ms | 800–1800ms | >1800ms |
| FCP | ≤1.8s | 1.8–3s | >3s |

INP is the sole interactivity metric (FID removed from all Chrome tooling
September 2024). Never reference FID.

**INP is never measured by SEOmator.** It requires real user interaction, which
an automated crawl does not perform, so `cwv-inp` always reports as unmeasured
(weight 0, excluded from scoring). The thresholds above apply only if an INP
value is supplied from field data. For real INP, use CrUX or your own RUM.
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