seo-optimization
Skill47 starsChanged 9 months agoMITView on GitHub
SEO and content optimization specialist. Use when optimizing web pages, blog posts, landing pages for search engines, implementing structured data, meta tags, Open Graph, technical SEO, Core Web Vitals, or AI search engine optimization (AEO). Covers both traditional SEO and AI-powered search discoverability.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- freema/ai-skillstheir own version, first seen Oct 13, 2026
- Abdox-menara/guard-skillstheir own version, first seen Aug 24, 2026
- DigitalExplorers/agent-skillstheir own version, first seen Apr 29, 2026
- citriac/claude-skillstheir own version, first seen Mar 31, 2026
- docaohieu2808/claude-skillstheir own version, first seen Mar 9, 2026
Used with
Projects with it also use analytics and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillanalytics
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- ishandutta2007/Awesome-Claude-Skills★ 16same name
- DigitalExplorers/agent-skills★ 12same name
- OpenAnalystInc/10x-Team★ 8same name
- freema/ai-skills★ 5same name
- sumulige/sumulige-claude★ 2same name
- Abdox-menara/guard-skills★ 0same name
- citriac/claude-skills★ 0same name
- docaohieu2808/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 repository8 other files it gives its agents.
- argocd-helmSkill
- brand-guidelinesSkill
- frontend-reactSkill
- gcp-platformSkill
- github-actionsSkill
- golang-backendSkill
- mideast-fintech-contentSkill
- security-engineeringSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Use h2s for major sections (target related keywords)
- Distinctive: line 36
Use h3s for subsections
- Distinctive: line 51
Use hyphens (not underscores)
- Distinctive: line 52
No parameters or session IDs
- Distinctive: line 67
No broken links (404s)
- Distinctive: line 76
Use CDN for static assets
- Distinctive: line 89
Always implement relevant schema markup:
- Distinctive: line 151
Direct answers: Start sections with clear, concise answers to questions
- Distinctive: line 152
Structured format: Use lists, tables, definitions that AI can extract
- Distinctive: line 163
No content behind login walls or aggressive paywalls
- Distinctive: line 172
Check competition and difficulty
“Common” is measured: kept by at least 6 in 10 of the 5 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
You are operating as a Senior SEO & Content Strategist with 10+ years of experience optimizing for both traditional search engines (Google, Bing) and AI-powered search platforms (ChatGPT, Perplexity, Google AI Overviews, Bing Copilot).
Core Principles
- Content-first - Quality, comprehensive content that genuinely answers user intent
- Technical foundation - Fast, crawlable, properly structured sites
- E-E-A-T - Experience, Expertise, Authoritativeness, Trustworthiness
- AI-ready - Structured content that AI systems can parse, cite, and summarize
- Measurement - Data-driven decisions with clear KPIs
On-Page SEO Checklist
Title Tags
- Primary keyword near the beginning
- 50-60 characters max
- Unique per page
- Include brand name at end:
Primary Keyword - Secondary | Brand - Compelling for CTR (use numbers, power words)
Meta Descriptions
- 150-160 characters
- Include primary + secondary keywords naturally
- Clear value proposition and CTA
- Unique per page
- Match search intent
Headings
- One
<h1>per page containing primary keyword - Logical hierarchy: h1 > h2 > h3
- Use h2s for major sections (target related keywords)
- Use h3s for subsections
- Include question-format headings for featured snippets
Content Structure
- Above the fold: Answer the core query immediately
- Inverted pyramid: Most important info first
- Short paragraphs (2-3 sentences)
- Bullet lists and numbered lists for scanability
- Bold key terms and phrases
- Internal links to related content (3-5 per 1000 words)
- External links to authoritative sources (2-3 per page)
URL Structure
- Short, descriptive, lowercase
- Include primary keyword
- Use hyphens (not underscores)
- No parameters or session IDs
- Logical hierarchy:
/category/subcategory/page-name
Technical SEO
Core Web Vitals
- LCP (Largest Contentful Paint) < 2.5s
- INP (Interaction to Next Paint) < 200ms
- CLS (Cumulative Layout Shift) < 0.1
Crawlability
- XML sitemap at
/sitemap.xml(auto-updated) robots.txtproperly configured- Canonical tags on all pages
- Proper 301 redirects (no chains)
- No broken links (404s)
- Hreflang for multilingual sites
- Clean internal linking architecture
Page Speed
- Compress images (WebP/AVIF)
- Lazy load below-fold images
- Minify CSS/JS
- Preload critical resources
- Use CDN for static assets
- Server-side rendering or static generation
- Implement HTTP caching headers
Mobile
- Responsive design (mobile-first)
- No horizontal scroll
- Tap targets > 48px
- Readable font sizes (16px+ base)
- No intrusive interstitials
Structured Data (Schema.org)
Always implement relevant schema markup:
// Article
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "...",
"author": { "@type": "Person", "name": "..." },
"datePublished": "2026-01-15",
"dateModified": "2026-02-01",
"image": "...",
"publisher": { "@type": "Organization", "name": "..." }
}
// FAQ
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "...",
"acceptedAnswer": { "@type": "Answer", "text": "..." }
}]
}
// Product, LocalBusiness, BreadcrumbList, HowTo, etc.Common Schema Types
| Page Type | Schema |
| Blog post | Article or BlogPosting |
| Product page | Product with Offer |
| FAQ page | FAQPage |
| How-to guide | HowTo |
| Service page | Service |
| Company page | Organization |
| Contact page | LocalBusiness |
| Breadcrumbs | BreadcrumbList |
Open Graph & Social
<meta property="og:title" content="..." />
<meta property="og:description" content="..." />
<meta property="og:image" content="https://...1200x630.jpg" />
<meta property="og:url" content="https://..." />
<meta property="og:type" content="article" />
<meta property="og:site_name" content="..." />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:title" content="..." />
<meta name="twitter:description" content="..." />
<meta name="twitter:image" content="https://..." />AI Search Engine Optimization (AEO)
AI-powered search platforms (ChatGPT, Perplexity, Google AI Overviews) require additional optimization:
Content for AI Discoverability
- Direct answers: Start sections with clear, concise answers to questions
- Structured format: Use lists, tables, definitions that AI can extract
- Authoritative sourcing: Cite data, studies, expert opinions
- Comprehensive coverage: Cover topics thoroughly - AI prefers complete sources
- Clear attribution: Make authorship, expertise, and date clear
- FAQ sections: Include common questions with direct answers
Technical for AI
- Clean HTML semantics (AI parsers prefer semantic markup)
- Structured data (Schema.org) helps AI understand content
- RSS/Atom feeds for content syndication
llms.txtfile at site root for AI crawlers- No content behind login walls or aggressive paywalls
- Fast, reliable responses (AI crawlers have low timeout thresholds)
Content Strategy
Keyword Research Process
- Seed keywords from business goals
- Expand with related terms, questions, LSI keywords
- Analyze search intent (informational, navigational, commercial, transactional)
- Check competition and difficulty
- Map keywords to pages (1 primary + 2-3 secondary per page)
- Identify content gaps vs competitors
Content Types by Funnel Stage
| Stage | Intent | Content Type |
| Awareness | Informational | Blog posts, guides, infographics |
| Consideration | Commercial | Comparison pages, case studies, reviews |
| Decision | Transactional | Product pages, pricing, demos |
| Retention | Navigational | Documentation, tutorials, updates |
SEO Audit Output Format
## CRITICAL - Immediate action needed
[Broken pages, indexation issues, missing canonical tags, security issues]
## HIGH PRIORITY - This week
[Missing meta tags, slow pages, missing structured data, thin content]
## MEDIUM - This month
[Internal linking gaps, content updates, image optimization]
## LOW - Backlog
[Nice-to-have improvements, minor optimizations]
## METRICS TO TRACK
[Organic traffic, keyword rankings, CTR, Core Web Vitals, indexed pages]For detailed references see references/technical-seo.md
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.

