agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/seo-review/SKILL.md

seo-review

Skill2 starsChanged 6 months agoMITView on GitHub

SEO review workflow — technical SEO audit, meta tags, structured data validation, Core Web Vitals, crawlability, indexability, AI search readiness. Applies SEO Engineer role. Use standalone or as part of feature/docs workflows.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user (or extract from parent workflow):

    line 21
  2. Distinctive:

    If implementation changes are needed, delegate to:

    line 32
  3. Distinctive:

    Run automated checks before making changes.

    line 43
  4. Distinctive:

    Check the following (read project files or use browser/curl):

    line 47
  5. Distinctive:

    No orphaned pages (all pages reachable via internal links)

    line 51
  6. Distinctive:

    No crawl traps (infinite URL parameters, calendar widgets)

    line 53
  7. Very specific:

    No accidental noindex on public pages

    line 57
  8. Distinctive:

    No canonical conflicts (canonical vs redirects vs internal links)

    line 59
  9. Distinctive:

    Wait for user to review and approve which fixes to implement.

    line 154
  10. Very specific:

    Follow seo-engineer role standards for all changes.

    line 166

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Review

Systematic SEO audit for public-facing pages. Checks crawlability, indexability, on-page SEO, structured data, Core Web Vitals, and AI search readiness. Applies seo-engineer role for all steps.

Works standalone or as a follow-up skill called by docs skill, feature-dev skill, or bugfix skill.

1. Define Scope

Ask the user (or extract from parent workflow):

  • Target pages: Specific URLs, page group, or entire site
  • Environment: Local dev / staging / production
  • Review type: Full audit / metadata only / structured data / performance / AI search
  • Constraints: What must not change (URL structure, navigation, etc.)

2. Apply Roles

Apply seo-engineer role as primary role.

If implementation changes are needed, delegate to:

Change TypeDelegate To
Frontend code (meta tags, JSON-LD, components)frontend-engineer role
Content / copy improvementscontent-writer role
Server config (redirects, headers, robots.txt)devops-engineer role
Architecture changes (URL structure, routing)solution-architect role

3. Baseline Audit

Run automated checks before making changes.

3a. Crawlability

Check the following (read project files or use browser/curl):

  • robots.txt — allows important pages, Sitemap: directive present
  • XML sitemap — includes all indexable pages, excludes non-indexable
  • No orphaned pages (all pages reachable via internal links)
  • Navigation uses crawlable <a href> links
  • No crawl traps (infinite URL parameters, calendar widgets)

3b. Indexability

  • No accidental noindex on public pages
  • Canonical tags point to correct URLs
  • No canonical conflicts (canonical vs redirects vs internal links)
  • Pages return 200 status codes (check for soft 404s)
  • Critical content rendered server-side (SSR/SSG), not client-only

3c. On-Page SEO

For each target page:

ElementCheck
Title tagUnique, descriptive, matches page intent
Meta descriptionUnique, compelling, relevant
H1Exactly one per page, matches topic
Heading hierarchyLogical H1→H2→H3
Image alt textDescriptive for all meaningful images
Internal linksPresent, descriptive anchor text
Outbound linksQualified with rel attributes where needed

3d. Structured Data

  • JSON-LD present where applicable:
    • Organization / WebSite on homepage
    • Article / BlogPosting on blog posts
    • BreadcrumbList for navigation
    • FAQ where genuinely useful
    • Product, Review, HowTo where applicable
  • Structured data matches visible page content (no misleading markup)
  • Validate with Rich Results Test

3e. Core Web Vitals

MetricTargetTool
LCP (Largest Contentful Paint)< 2.5sPageSpeed Insights
INP (Interaction to Next Paint)< 200msPageSpeed Insights
CLS (Cumulative Layout Shift)< 0.1PageSpeed Insights

3f. Mobile Optimization

  • Responsive design across viewports
  • Tap targets ≥ 48×48px
  • No horizontal scrolling
  • Font size ≥ 16px body text
  • No intrusive interstitials

3g. AI Search Readiness

  • Pages crawlable and well-structured (SSR/SSG, semantic HTML)
  • Content is clear, factual, and authoritative
  • Structured data present and accurate
  • llms.txt present (optional, experimental — not a ranking factor)
  • Pages indexed and snippet-eligible (prerequisite for AI features)

3h. GEO/AEO Audit

Apply geo-writer skill to audit extractability for AI engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews):

  • Schema coverage — Article or BlogPosting + Person with sameAs + Organization on blog pages; FAQPage where FAQ present; HowTo for tutorials; Product / Review on commercial pages. JSON-LD must mirror visible text (no marketing-only prose in schema).
  • Answer-first structure — each H2/H3 opens with a self-contained 30-60 word answer. No buried ledes.
  • Macro/meso/micro chunking — single H1, 5-9 H2 sections phrased as questions or topics, paragraphs 40-80 words, bold anchors every section.
  • Entity clarity — canonical brand terms used verbatim, no pronoun drift, entity mentions in first 100 words.
  • High-leverage formats — FAQ blocks (4-8 Q&A), comparison tables (2+ entities), HowTo steps (3-8 numbered actions) where natural.
  • Freshness signals — dateModified present and recent; datePublished set; content updated within the pillar's freshness window.
  • Citation-ready — stats/claims attributed to named sources with outbound links where appropriate.

The geo-content rule enforces these for public-facing text. Use pre-publish-checklist.md from geo-writer skill for the full checklist.

4. Present Findings

Compile audit results:

## SEO Audit Report

### Pages Reviewed: [count]

### Critical Issues (blocking indexing/ranking)
- [ ] [issue] — [affected page] — [fix]

### Warnings (affecting quality/performance)
- [ ] [issue] — [affected page] — [fix]

### Opportunities (improvements)
- [ ] [opportunity] — [affected page] — [recommendation]

### Scores
- Crawlability: [OK / issues found]
- Indexability: [OK / issues found]
- On-Page SEO: [OK / issues found]
- Structured Data: [OK / missing / errors]
- Core Web Vitals: [LCP: Xs, INP: Xms, CLS: X.XX]
- Mobile: [OK / issues found]
- AI Search: [OK / opportunities]

Wait for user to review and approve which fixes to implement.

5. Implement Fixes

For approved fixes:

  1. Metadata changes (title, description, OG tags) — implement directly or delegate to frontend-engineer role
  2. Structured data (JSON-LD) — implement directly or delegate to frontend-engineer role
  3. Content changes — delegate to content-writer role
  4. Server config (redirects, headers) — delegate to devops-engineer role
  5. Performance fixes (image optimization, lazy loading, critical CSS) — delegate to frontend-engineer role

Follow seo-engineer role standards for all changes. No black-hat techniques.

6. Verify

Re-run relevant checks from Step 3 for changed pages:

  • Fixed issues no longer present
  • No new issues introduced
  • Structured data validates (Rich Results Test)
  • Pages still indexable (no accidental noindex)
  • Core Web Vitals within targets
  • No broken links introduced

7. Summary

## SEO Review Summary
- **Scope**: [pages/environment reviewed]
- **Issues found**: [critical: X, warnings: X, opportunities: X]
- **Fixes applied**:
  - [fix 1] — [page]
  - [fix 2] — [page]
- **Delegated to**: [roles involved]
- **Verification**: [pass/fail per check]
- **Monitoring**: [what to watch — Search Console, PageSpeed, etc.]
- **Follow-ups**: [items for future attention]

Integration

  • Roles: seo-engineer role (primary), frontend-engineer role (implementation), content-writer role (content fixes)
  • Skills: geo-writer skill (GEO/AEO audit — step 3h), humanizer skill (applied when content fixes are needed)
  • Rules: geo-content (enforces GEO structure and schema on public-facing text), humanize-content (enforces humanizer pass)
  • Called by: feature-dev skill (SEO-relevant features), docs skill (public content)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.