seo-audit
Full SEO and performance audit for any website. Use when asked to check SEO, run a lighthouse scan, audit performance, check accessibility, or validate structured data.
What this skill does
# SEO Audit Skill
## When to Use
- User says "SEO audit", "check SEO", "lighthouse scan", "performance check", "site audit"
- Need to validate SEO, accessibility, performance, or structured data
## Workflow
### 1. Lighthouse Scan
Run Lighthouse via CLI for both mobile and desktop:
```bash
# Install if needed
npx --yes lighthouse
# Run scans
npx lighthouse URL --output=json --output-path=./lighthouse-mobile.json --emulated-form-factor=mobile --quiet
npx lighthouse URL --output=json --output-path=./lighthouse-desktop.json --emulated-form-factor=desktop --quiet
```
Extract and report:
- **Performance** (target: 90+)
- **Accessibility** (target: 100)
- **Best Practices** (target: 100)
- **SEO** (target: 90+)
### 2. Core Web Vitals
From Lighthouse results, extract and assess:
- **LCP** (Largest Contentful Paint) — target: <2.5s
- **FID** (First Input Delay) — target: <100ms
- **CLS** (Cumulative Layout Shift) — target: <0.1
- **INP** (Interaction to Next Paint) — target: <200ms
- **TTFB** (Time to First Byte) — target: <800ms
Flag any that fail and identify the cause.
### 3. Meta Tags Audit
Fetch the page HTML and check:
- [ ] `<title>` present, 30-60 chars, unique per page
- [ ] `<meta name="description">` present, 120-160 chars
- [ ] Open Graph tags: `og:title`, `og:description`, `og:image`, `og:url`
- [ ] Twitter Card tags: `twitter:card`, `twitter:title`, `twitter:description`, `twitter:image`
- [ ] `<meta name="viewport">` present
- [ ] `<link rel="canonical">` set correctly
- [ ] `<meta name="robots">` not blocking important pages
- [ ] Hreflang tags for multilingual sites
### 4. Heading Hierarchy
Parse headings and check:
- [ ] Exactly one `<h1>` per page
- [ ] Logical hierarchy (H1 → H2 → H3, no skipping levels)
- [ ] Headings contain relevant keywords
- [ ] No empty heading tags
### 5. Image Audit
Scan all `<img>` tags:
- [ ] All images have `alt` text
- [ ] `width` and `height` attributes set (prevents CLS)
- [ ] Images use modern formats (WebP, AVIF)
- [ ] Lazy loading applied (`loading="lazy"`) for below-fold images
- [ ] No oversized images (check natural vs display size)
- [ ] Decorative images have empty alt (`alt=""`)
### 6. Link Audit
Check all links on the page:
- [ ] No broken internal links (404s)
- [ ] No broken external links
- [ ] External links use `rel="noopener"` for `target="_blank"`
- [ ] Descriptive anchor text (no "click here")
- [ ] No orphaned pages (pages with no internal links to them)
### 7. Sitemap & Robots.txt
- [ ] `sitemap.xml` exists and is valid XML
- [ ] `sitemap.xml` referenced in `robots.txt`
- [ ] `robots.txt` exists and is not overly restrictive
- [ ] All important pages are in sitemap
- [ ] Sitemap last modified date is recent
### 8. Structured Data / Schema
Check for JSON-LD structured data:
- [ ] Valid JSON-LD present
- [ ] Schema type appropriate for page content
- [ ] Common schemas: Organization, WebSite, BreadcrumbList, Article, FAQPage, LocalBusiness
- [ ] No schema errors or warnings (validate with Google Rich Results Test logic)
- [ ] `@id` and `url` fields consistent
### 9. Technical SEO
- [ ] HTTPS enforced (redirects HTTP → HTTPS)
- [ ] WWW/non-WWW canonical redirect
- [ ] No mixed content warnings
- [ ] Proper 404 page
- [ ] 301/302 redirects working correctly
- [ ] No redirect chains (3+ hops)
- [ ] Compression enabled (gzip/brotli)
- [ ] Browser caching headers set
- [ ] No render-blocking resources
### 10. Mobile & Accessibility
- [ ] Responsive meta viewport tag
- [ ] Touch targets >= 48px
- [ ] Text readable without zooming
- [ ] No horizontal scroll on mobile
- [ ] ARIA labels on interactive elements
- [ ] Color contrast ratio >= 4.5:1
- [ ] Form labels present
- [ ] Skip navigation link
## Output Format
```
═══════════════════════════════════════
SEO AUDIT: [URL]
Date: [YYYY-MM-DD]
═══════════════════════════════════════
LIGHTHOUSE SCORES
Desktop Mobile
Performance [XX] [XX]
Accessibility [XX] [XX]
Best Practices [XX] [XX]
SEO [XX] [XX]
CORE WEB VITALS
LCP: [X.Xs] [✓/✗ target: <2.5s]
FID: [Xms] [✓/✗ target: <100ms]
CLS: [X.XX] [✓/✗ target: <0.1]
META TAGS [✓/✗] [issue count]
HEADINGS [✓/✗] [issue count]
IMAGES [✓/✗] [issue count]
LINKS [✓/✗] [broken count]
SITEMAP [✓/✗]
STRUCTURED DATA [✓/✗]
TECHNICAL SEO [✓/✗]
MOBILE/A11Y [✓/✗]
═══════════════════════════════════════
ISSUES FOUND
═══════════════════════════════════════
🔴 CRITICAL
[Issues that severely impact rankings or UX]
🟡 WARNING
[Issues that should be fixed]
🟢 SUGGESTIONS
[Nice-to-have improvements]
═══════════════════════════════════════
RECOMMENDATIONS
═══════════════════════════════════════
1. [Most impactful fix first]
2. [Second most impactful]
3. [Third]
```
## Usage
```
# Single page audit
/seo-audit https://example.com
# Full site audit (crawls linked pages)
/seo-audit https://example.com --full
# Compare before/after
/seo-audit https://example.com --compare ./previous-audit.json
```
## Multi-Page Mode (--full)
When `--full` is specified:
1. Start with the provided URL
2. Crawl all internal links (same domain)
3. Run full audit on each page
4. Generate aggregate report with worst offenders
5. List pages sorted by score (lowest first)
## Confidence Assessment
After completing audit, rate confidence **0.0 to 1.0**:
- **0.9-1.0**: Full Lighthouse + all 10 checks, clear prioritized issues
- **0.6-0.9**: Lighthouse run but some checks incomplete
- **0.3-0.6**: Only partial audit completed
- **0.0-0.3**: Could not access site or run Lighthouse
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".