check-seo

check-seo

Audit any website's SEO, suggest prioritized fixes, then auto-apply fixes to the local codebase.

When to use

Triggered by: "check SEO", "audit SEO", "fix SEO", "my SEO score", "audit https://...", "improve SEO"

Prerequisites

Check and install if missing:

seomator --version 2>/dev/null || npm install -g @seomator/seo-audit

For Core Web Vitals (optional):

npx playwright install chromium

Phase 1 — Audit

Run the audit with LLM-optimized output:

seomator audit <url> --format llm

Parse the XML output to extract:

• Overall score (0-100) and grade (A-F)
• Per-category scores and weights
• All issues with severity: critical, warning, info

Display a summary table:

Overall: 67/100 (D)

Category         Score  Issues
Core SEO          45    3 critical, 2 warnings
Performance       72    1 critical, 4 warnings
Security          88    0 critical, 1 warning
...

Phase 2 — Suggest

Group all issues by severity and show the top 10 prioritized by impact:

CRITICAL (fix these first):
1. [Core SEO] Missing meta description — affects click-through rate
2. [Core SEO] Title tag too long (87 chars, max 60) — truncated in SERPs
3. [Performance] No image lazy loading — hurts LCP score
...

WARNINGS:
4. [Security] Missing X-Frame-Options header
...

Ask the user:

"Found X critical issues and Y warnings. Fix all critical issues automatically? (yes/no/select)"

If "select", list issues numbered so user can pick which to fix.

Phase 3 — Detect Stack

From the project root, detect the tech stack:

# Check for framework config files
ls next.config.* 2>/dev/null && echo "nextjs"
ls nuxt.config.* 2>/dev/null && echo "nuxt"
ls vite.config.* 2>/dev/null && echo "vite"
find . -name "*.html" -maxdepth 3 | head -5

Detection rules:

• next.config.* OR src/app/layout.tsx OR pages/_app.tsx → Next.js
• nuxt.config.* → Nuxt
• vite.config.* + index.html → Vue SPA
• *.html files, no framework → Plain HTML
• Unknown → treat as Plain HTML