AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

seo-audit

Use when a site is not ranking or needs an SEO audit (technical, on-page, meta tags), before giving advice. Scans pages with seo_checker.py and scores site health with seo_health_scorer.py.

Original source
alirezarezvani
License
MIT
Pinned revision
e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read alirezarezvani--seo-audit at revision e4a1dc3695908dd5a6c811cc76ab7aa4cf95f2f0, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 5

references/cwv-thresholds.md

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.