seo-audit
Audit websites for SEO, technical, content, security, JS rendering, and AI readiness using SEOmator CLI. Returns LLM-optimized reports with health scores across 251 rules and 20 categories. Use when analyzing websites, debugging SEO issues, or checking site health.
What this skill does
# SEO Audit Skill Audit websites for SEO, technical, content, performance, security, JavaScript rendering, and AI readiness using the SEOmator CLI. SEOmator provides comprehensive website auditing by analyzing website structure and content against **251 rules** across **20 categories**. It provides a list of issues with severity levels, affected URLs, and actionable fix suggestions. ## Links * SEOmator npm package: [npmjs.com/package/@seomator/seo-audit](https://www.npmjs.com/package/@seomator/seo-audit) * GitHub repository: [github.com/seo-skills/seo-audit-skill](https://github.com/seo-skills/seo-audit-skill) * Web UI: [seomator.com/free-seo-audit-tool](https://seomator.com/free-seo-audit-tool) ## What This Skill Does This skill enables AI agents to audit websites for **251 rules** in **20 categories**, including: - **Core SEO** (19 rules): Canonical URLs, indexing directives, title uniqueness, canonical conflicts/loops - **Performance** (22 rules): LCP, CLS, FCP, TTFB, INP, compression, caching, minification, HTTP/2 - **Links** (19 rules): Broken links, redirect chains, anchor text, orphan pages, localhost/fragment links - **Images** (14 rules): Alt text, dimensions, lazy loading, modern formats, alt length, background images - **Security** (16 rules): HTTPS, HSTS, CSP, external link safety, leaked secrets, SSL expiry/protocol - **Technical SEO** (13 rules): robots.txt, sitemap.xml, URL structure, 404 pages, soft 404s, error codes - **Crawlability** (18 rules): Sitemap conflicts, indexability signals, canonical chains, pagination issues - **Structured Data** (13 rules): Schema.org markup, Article, Organization, FAQ, Product, Breadcrumb - **JavaScript Rendering** (13 rules): Rendered DOM checks, raw vs rendered mismatches, SSR detection - **Accessibility** (12 rules): ARIA labels, color contrast, form labels, landmarks, touch targets - **Content** (17 rules): Word count, readability, keyword density, duplicate detection, pixel widths - **Social** (9 rules): Open Graph tags, Twitter cards, share buttons, profile links - **E-E-A-T** (14 rules): Author bylines, citations, trust signals, about/contact pages, YMYL detection - **URL Structure** (14 rules): Keyword slugs, stop words, uppercase, underscores, session IDs, tracking params - **Redirects** (8 rules): Redirect loops, types (301/302), meta refresh, JavaScript redirects, broken redirects - **Mobile** (5 rules): Font sizes, horizontal scroll, intrusive interstitials, viewport issues - **Internationalization** (10 rules): lang attribute, hreflang validation (return links, conflicts, mismatches) - **HTML Validation** (9 rules): Doctype, charset, head structure, lorem ipsum, multiple titles/descriptions - **AI/GEO Readiness** (5 rules): Semantic HTML, AI bot access, llms.txt, schema drift - **Legal Compliance** (1 rule): Cookie consent The audit crawls the website, analyzes each page against audit rules, and returns a comprehensive report with: - Overall health score (0-100) with letter grade (A-F) - Category breakdowns with pass/warn/fail counts - Specific issues with affected URLs grouped by rule - Actionable fix recommendations ## When to Use Use this skill when you need to: - Analyze a website's SEO health - Debug technical SEO issues - Check for broken links and redirect chains - Validate meta tags, canonical URLs, and structured data - Audit security headers, SSL, and HTTPS - Check accessibility compliance - Analyze JavaScript rendering and SSR compatibility - Evaluate AI/GEO readiness (semantic HTML, llms.txt, bot access) - Detect duplicate content across pages - Validate hreflang and internationalization setup - Check HTML document structure and validation - Generate site audit reports in multiple formats - Compare site health before/after changes ## Prerequisites This skill requires the SEOmator CLI to be installed. ### Installation ```bash npm install -g @seomator/seo-audit ``` ### Verify Installation Check that seomator is installed and the system is ready: ```bash seomator self doctor ``` This checks: - Node.js version (18+ recommended) - npm availability - Chrome/Chromium for Core Web Vitals and JS rendering - Write permissions for ~/.seomator - Local config file presence ## Setup Running `seomator init` creates a `seomator.toml` config file in the current directory. ```bash seomator init # Interactive setup seomator init -y # Use defaults seomator init --preset blog # Blog-optimized config seomator init --preset ecommerce # E-commerce config seomator init --preset ci # Minimal CI config ``` If there is no `seomator.toml` in the directory, CREATE ONE with `seomator init` before running audits. ## Usage ### AI Agent Best Practices **YOU SHOULD always prefer `--format llm`** - it provides token-optimized XML output specifically designed for AI agents (50-70% smaller than JSON). When auditing: 1. **Prefer live websites** over local dev servers for accurate performance and rendering data 2. **Use `--no-cwv` for faster audits** when Core Web Vitals and JS rendering checks aren't needed 3. **Scope fixes as concurrent tasks** when implementing multiple fixes 4. **Run typechecking/formatting** after implementing fixes (tsc, eslint, prettier, etc.) ### Website Discovery If the user doesn't provide a website to audit: 1. Check for local dev server configurations (package.json scripts, .env files) 2. Look for Vercel/Netlify project links 3. Check environment variables for deployment URLs 4. Ask the user which URL to audit If you have both local and live websites available, **suggest auditing the live site** for accurate results. ### Basic Workflow ```bash # Quick single-page audit with LLM output seomator audit https://example.com --format llm --no-cwv # Multi-page crawl (up to 50 pages) seomator audit https://example.com --crawl -m 50 --format llm --no-cwv # Full audit with Core Web Vitals + JS rendering analysis seomator audit https://example.com --crawl -m 20 --format llm ``` ### Advanced Options Force fresh crawl (ignore cache): ```bash seomator audit https://example.com --refresh --format llm ``` Resume interrupted crawl: ```bash seomator audit https://example.com --resume --format llm ``` Audit specific categories only: ```bash seomator audit https://example.com -c core,security,js --format llm --no-cwv ``` Save HTML report for sharing: ```bash seomator audit https://example.com --format html -o report.html ``` Verbose output for debugging: ```bash seomator audit https://example.com --format llm -v ``` ## Command Reference ### Audit Command Options | Option | Alias | Description | Default | |--------|-------|-------------|---------| | `--format <fmt>` | `-f` | Output format: console, json, html, markdown, llm | console | | `--max-pages <n>` | `-m` | Maximum pages to crawl | 10 | | `--crawl` | | Enable multi-page crawl | false | | `--categories <list>` | `-c` | Comma-separated categories to audit | All | | `--refresh` | `-r` | Ignore cache, fetch fresh | false | | `--resume` | | Resume interrupted crawl | false | | `--no-cwv` | | Skip Core Web Vitals + JS rendering | false | | `--verbose` | `-v` | Show progress | false | | `--output <path>` | `-o` | Output file path | | | `--config <path>` | | Config file path | | | `--save` | | Save to ~/.seomator | false | ### Other Commands ```bash seomator init # Create config file seomator self doctor # Check system setup seomator config --list # Show all config values seomator report --list # List past reports seomator db stats # Show database statistics ``` ## Output Formats | Format | Flag | Best For | |--------|------|----------| | console | `--format console` | Human terminal output (default) | | json | `--format json` | CI/CD, programmatic processing | | html | `--format html` | Standalone reports, sharing | | markdown | `--format markdown` | Documentation, GitHub | | llm | `--format llm` | **AI agents** (recommended) |
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".