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
- AdeyStudios/skillstheir own version, first seen Nov 1, 2026
- leonardomso/33-js-conceptstheir own version, first seen Oct 8, 2026
- KikaKikaKikaKika/Claude-skillstheir own version, first seen Sep 22, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- leonardomso/33-js-concepts★ 67ksame name
- AdeyStudios/skills★ 1same name
- KikaKikaKikaKika/Claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- marketingSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
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
- Distinctive: line 21
Ask the user (or extract from parent workflow):
- Distinctive: line 32
If implementation changes are needed, delegate to:
- Distinctive: line 43
Run automated checks before making changes.
- Distinctive: line 47
Check the following (read project files or use browser/curl):
- Distinctive: line 51
No orphaned pages (all pages reachable via internal links)
- Distinctive: line 53
No crawl traps (infinite URL parameters, calendar widgets)
- Very specific: line 57
No accidental noindex on public pages
- Distinctive: line 59
No canonical conflicts (canonical vs redirects vs internal links)
- Distinctive: line 154
Wait for user to review and approve which fixes to implement.
- Very specific: line 166
Follow seo-engineer role standards for all changes.
“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.
Files
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 Type | Delegate To |
| Frontend code (meta tags, JSON-LD, components) | frontend-engineer role |
| Content / copy improvements | content-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
noindexon 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:
| Element | Check |
| Title tag | Unique, descriptive, matches page intent |
| Meta description | Unique, compelling, relevant |
| H1 | Exactly one per page, matches topic |
| Heading hierarchy | Logical H1→H2→H3 |
| Image alt text | Descriptive for all meaningful images |
| Internal links | Present, descriptive anchor text |
| Outbound links | Qualified with rel attributes where needed |
3d. Structured Data
- JSON-LD present where applicable:
Organization/WebSiteon homepageArticle/BlogPostingon blog postsBreadcrumbListfor navigationFAQwhere genuinely usefulProduct,Review,HowTowhere applicable
- Structured data matches visible page content (no misleading markup)
- Validate with Rich Results Test
3e. Core Web Vitals
| Metric | Target | Tool |
| LCP (Largest Contentful Paint) | < 2.5s | PageSpeed Insights |
| INP (Interaction to Next Paint) | < 200ms | PageSpeed Insights |
| CLS (Cumulative Layout Shift) | < 0.1 | PageSpeed 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.txtpresent (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 —
ArticleorBlogPosting+PersonwithsameAs+Organizationon blog pages;FAQPagewhere FAQ present;HowTofor tutorials;Product/Reviewon 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 —
dateModifiedpresent and recent;datePublishedset; 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:
- Metadata changes (title, description, OG tags) — implement directly or delegate to
frontend-engineerrole - Structured data (JSON-LD) — implement directly or delegate to
frontend-engineerrole - Content changes — delegate to
content-writerrole - Server config (redirects, headers) — delegate to
devops-engineerrole - Performance fixes (image optimization, lazy loading, critical CSS) — delegate to
frontend-engineerrole
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-engineerrole (primary),frontend-engineerrole (implementation),content-writerrole (content fixes) - Skills:
geo-writerskill (GEO/AEO audit — step 3h),humanizerskill (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-devskill (SEO-relevant features),docsskill (public content)
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
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.

