alirezarezvani/claude-skills / marketing-skill/skills/seo-audit
seo-audit
VerifiedFind why a site is not ranking: technical SEO, on-page issues, meta tags, site health. Use whenever the user asks why a page is not on Google, why traffic dropped or for an SEO audit.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| references/cwv-thresholds.md | markdown | 1.7 KB |
| references/eeat-framework.md | markdown | 2.8 KB |
| references/schema-types.md | markdown | 2.5 KB |
| references/seo-audit-reference.md | markdown | 5.8 KB |
| scripts/seo_checker.pyexecutable | script | 13.2 KB |
| scripts/seo_health_scorer.py | script | 11.1 KB |
references/cwv-thresholds.md
View on GitHub# Core Web Vitals Thresholds (2026)
Reference for `seo_health_scorer.py` and the Performance category. Updated per Google's CrUX methodology.
## The three metrics
| Metric | Good | Needs Improvement | Poor | What it measures |
|---|---|---|---|---|
| **LCP** (Largest Contentful Paint) | ≤ 2.5s | 2.5s – 4.0s | > 4.0s | Loading speed — when the main content is visible |
| **CLS** (Cumulative Layout Shift) | ≤ 0.1 | 0.1 – 0.25 | > 0.25 | Visual stability — unexpected layout jumps |
| **INP** (Interaction to Next Paint) | ≤ 200ms | 200ms – 500ms | > 500ms | Responsiveness — delay after user interaction |
## Scoring mapping
```
pass = metric in "Good" range
warn = metric in "Needs Improvement" range
fail = metric in "Poor" range
```
## Common fixes by metric
### LCP > 2.5s
- Optimize largest image (WebP/AVIF, proper sizing, preload)
- Reduce server response time (TTFB < 800ms)
- Remove render-blocking CSS/JS
- Use CDN for static assets
### CLS > 0.1
- Set explicit width/height on images and video
- Reserve space for ads/embeds before load
- Avoid inserting content above the fold after page load
- Use `font-display: swap` for web fonts
### INP > 200ms
- Break up long tasks (> 50ms) into smaller chunks
- Defer non-critical JavaScript
- Use `requestIdleCallback` for low-priority work
- Minimize main-thread blocking from third-party scripts
## Measurement sources
- **Field data:** CrUX (Chrome User Experience Report) — 28-day rolling p75
- **Lab data:** Lighthouse, PageSpeed Insights — synthetic, not real users
- **Monitoring:** web-vitals.js library for RUM (Real User Monitoring)
Field data (CrUX) is what Google uses for ranking signals. Lab data helps debug but doesn't directly affect rankings.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |