seo-audit
Skill757 starsChanged 8 months agoMITView on GitHub
Audit affiliate blog posts and landing pages for SEO issues. Triggers on: "audit my blog post for SEO", "check my SEO", "SEO review", "improve my rankings", "SEO checklist", "on-page SEO audit", "keyword optimization check", "why isn't my page ranking", "SEO score", "content quality audit", "check my meta tags", "internal linking audit", "quick SEO wins".
185 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- foverse/seoversetheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- figueroaignacio/ignaciofigueroa.devtheir own version, first seen Nov 8, 2026
- ftzi/livespectheir own version, first seen Nov 8, 2026
Used with
Projects with it also use openseo-review-web-content, openseo-release-notes and 10 more.
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.
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 5 projects that use this
JwuthriSkillopenseo-release-notes
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Also in 6 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
akii-technologies-ltdSkillkeyword-clustering
Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.
Also in 12 projects that use this
- +4 more from nicepkg
- +2 more from Jwuthri
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- coreyhaines31/marketingskills★ 59ksame name
- anthropics/knowledge-work-plugins★ 35ksame name
- every-app/open-seo★ 27ksame name
- AgriciDaniel/claude-seo★ 20ksame name
- trycompai/crm★ 12ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- legions-developer/evilcharts★ 3.2ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
175 more not listed
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 repository55 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- affiliate-checkSkill
- ab-test-generatorSkill
- conversion-trackerSkill
- internal-linking-optimizerSkill
- performance-reportSkill
- content-repurposerSkill
- email-automation-builderSkill
- multi-program-managerSkill
- paid-ad-copy-writerSkill
- proprietary-data-generatorSkill
- affiliate-blog-builderSkill
- comparison-post-writerSkill
- content-decay-detectorSkill
- content-moat-calculatorSkill
- how-to-tutorial-writerSkill
- keyword-cluster-architectSkill
- listicle-generatorSkill
- content-pillar-atomizerSkill
- content-research-briefSkill
- infographic-generatorSkill
- reddit-post-writerSkill
- tiktok-script-writerSkill
- twitter-thread-writerSkill
- viral-post-writerSkill
- bio-link-deployerSkill
- email-drip-sequenceSkill
- github-pages-deployerSkill
- social-media-schedulerSkill
- bonus-stack-builderSkill
- grand-slam-offerSkill
- guarantee-generatorSkill
- landing-page-creatorSkill
- product-showcase-pageSkill
- squeeze-page-builderSkill
- value-ladder-architectSkill
- webinar-registration-pageSkill
- category-designerSkill
- compliance-checkerSkill
- create-skillSkill
- funnel-plannerSkill
- self-improverSkill
- skill-finderSkill
- affiliate-program-searchSkill
- commission-calculatorSkill
- competitor-spySkill
- content-angle-rankerSkill
- find-and-verify-affiliate-programSkill
- monopoly-niche-finderSkill
- niche-opportunity-finderSkill
- purple-cow-auditSkill
- submit-programSkill
- traffic-analyzerSkill
- trending-content-scoutSkill
- your-skill-nameSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Chaining context: If S3 (blog) or S4 (landing page) was run in the same conversation, pull the generated content directly for audit.
- Very specific: line 96
All affiliate links have rel="nofollow sponsored" (Google requirement)
- Distinctive: line 131
Before presenting output, verify:
- Distinctive: line 139
If any check fails, fix the output before delivering.
“Common” is measured: kept by at least 6 in 10 of the 167 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 Audit
Audit affiliate blog posts and landing pages for SEO issues — on-page optimization, keyword usage, meta tags, content quality signals, affiliate link attributes, and internal linking. Output is a 10-dimension SEO scorecard with a prioritized fix-it checklist.
Stage
S6: Analytics — 53% of all website traffic comes from organic search. For affiliate bloggers, SEO is the most sustainable traffic source — but most affiliate content has basic SEO mistakes that tank rankings. This skill catches those mistakes and provides quick wins.
When to Use
- User has a blog post or landing page and wants an SEO review
- User asks "why isn't my page ranking?" or "check my SEO"
- User wants to improve search rankings for affiliate content
- User says "SEO audit", "SEO checklist", "on-page optimization"
- User wants to check affiliate link attributes (nofollow, sponsored)
- Chaining from S3 (blog) or S4 (landing): audit content before or after publishing
Input Schema
content: string # REQUIRED — the content to audit (markdown, HTML, or URL)
# If URL, will attempt to fetch and analyze
target_keyword: string # REQUIRED — primary keyword to optimize for
# (e.g., "best AI video tools", "HeyGen review")
content_type: string # OPTIONAL — "blog_post" | "landing_page"
# Default: "blog_post"
competitor_urls: # OPTIONAL — competitor pages to compare against
- string # e.g., ["competitor.com/heygen-review"]
secondary_keywords: # OPTIONAL — additional keywords to check
- string # e.g., ["AI video generator", "HeyGen pricing"]Chaining context: If S3 (blog) or S4 (landing page) was run in the same conversation, pull the generated content directly for audit. The user should not have to paste content just generated.
Workflow
Step 1: Analyze Content Structure
Check:
- Word count: Is it competitive? (blog: 1500+ words, landing: varies)
- Heading structure: H1 present and unique? H2/H3 hierarchy logical?
- Paragraph length: Short paragraphs for readability?
- Content depth: Does it cover the topic comprehensively?
Step 2: Check Keyword Usage
Analyze:
- Title tag: Contains target keyword? Under 60 characters?
- H1: Contains target keyword?
- First 100 words: Keyword appears naturally?
- Keyword density: 1-2% optimal (not stuffing, not absent)
- Keyword in subheadings: At least one H2 contains keyword or variant?
- LSI keywords: Related terms present for topical depth?
Step 3: Evaluate Meta Tags
Check:
- Title tag length: 50-60 characters optimal
- Meta description: Present? 150-160 characters? Contains keyword? Compelling?
- OG tags: Open Graph tags for social sharing
- Canonical URL: Present and correct?
Step 4: Check E-E-A-T Signals
Evaluate:
- Experience: First-person experience with the product?
- Expertise: Author credentials or demonstrated knowledge?
- Authoritativeness: Citing sources, linking to official pages?
- Trustworthiness: Transparent disclosure, balanced (pros AND cons)?
Step 5: Check Affiliate Link Attributes
Verify:
- All affiliate links have
rel="nofollow sponsored"(Google requirement) - Links are not cloaked in a way that violates search guidelines
- FTC disclosure is present and above the fold
- Links open in new tab (
target="_blank") for UX
Step 6: Check Internal Linking
Evaluate:
- Links to related content on the same site?
- Anchor text is descriptive (not "click here")?
- Table of contents for long content?
Step 7: Score on 10 Dimensions
Rate each 1-10:
- Keyword optimization
- Content depth and quality
- Title tag and meta description
- Heading structure
- E-E-A-T signals
- Affiliate link compliance
- Internal linking
- Readability and formatting
- Mobile friendliness indicators
- Technical SEO basics
Step 8: Generate Fix-It Checklist
Prioritize fixes by impact:
- Quick wins: Fix in 5 minutes, big impact (meta tags, keyword in H1)
- Medium effort: Fix in 30 minutes (add sections, improve depth)
- Major revision: Fix in 2+ hours (restructure content, add original research)
Step 9: Self-Validation
Before presenting output, verify:
- All 10 SEO dimensions scored (1-10 each)
- Overall score is weighted sum of dimension scores
- Issues prioritized: quick_win → medium → major
- Each fix is specific and actionable (not generic advice)
- Keyword density recommendation is 1-2% (not higher)
If any check fails, fix the output before delivering. Do not flag the checklist to the user — just ensure the output passes.
Output Schema
output_schema_version: "1.0.0" # Semver — bump major on breaking changes
audit:
url_or_title: string
target_keyword: string
overall_score: number # out of 100 (sum of 10 dimensions × 10)
word_count: number
scores:
- dimension: string
score: number # 1-10
status: string # "good" | "needs_work" | "critical"
notes: string
issues:
- priority: string # "quick_win" | "medium" | "major"
dimension: string
issue: string
fix: string # specific action to take
impact: string # "high" | "medium" | "low"
checklist:
- task: string
priority: string
done: boolean # always false (user checks off)Output Format
- SEO Scorecard — table with 10 dimensions, scores, and status
- Overall Score — X/100 with assessment (Excellent >80, Good 60-80, Needs Work 40-60, Critical <40)
- Quick Wins — fixes that take <5 minutes and have high impact
- Full Fix-It Checklist — all issues ordered by priority with specific actions
- Competitor Comparison — brief notes if competitor URLs were provided
Error Handling
- No content provided: "Paste the content of your blog post or landing page. I'll audit it for SEO issues and give you a prioritized fix-it list."
- No target keyword: "What keyword are you trying to rank for? (e.g., 'HeyGen review', 'best AI video tools'). This helps me check keyword usage and optimization."
- Content is too short (<300 words): "This content is quite short (X words). For competitive keywords, aim for 1,500+ words. I'll audit what's here, but content depth is likely your biggest SEO issue."
- URL provided but cannot be fetched: "I couldn't fetch that URL. Paste the page content directly and I'll audit it."
Examples
Example 1: Blog post with common issues
User: "Audit this blog post for 'best AI video tools': [pastes 2000-word blog post]"
Action: Score each dimension. Common findings: keyword not in H1 (fix: add to title), affiliate links missing rel="nofollow sponsored" (fix: add attributes), no meta description (fix: write one), thin intro section (fix: expand first paragraph). Overall score: 62/100. Quick wins: meta description, H1 keyword, link attributes.
Example 2: Landing page audit
User: "Check the SEO on my HeyGen landing page" [content from S4 in conversation] Action: Pull landing page content from S4 output. Note: landing pages are typically not SEO-optimized (they're conversion-focused). Score accordingly — different expectations for landing pages vs blog posts. Focus on: title tag, meta description, canonical, affiliate link compliance.
Example 3: Competitive comparison
User: "Audit my Semrush review and compare to these competitor pages: [competitor URLs]"
Action: Audit user's content first. Then use web_search or web_browse to analyze competitor content structure (word count, headings, topics covered). Identify content gaps — topics competitors cover that the user doesn't. Recommend additions to improve competitiveness.
References
shared/references/ftc-compliance.md— FTC disclosure requirements for affiliate content. Checked in Step 5.shared/references/affiliate-glossary.md— SEO and affiliate terminology. Referenced throughout.shared/references/flywheel-connections.md— master flywheel connection map
Flywheel Connections
Feeds Into
monopoly-niche-finder(S1) — ranking data reveals niches you're already winning inkeyword-cluster-architect(S3) — ranking gaps reveal keyword opportunitiescontent-decay-detector(S3) — declining pages to investigateinternal-linking-optimizer(S6) — link structure issues to fix
Fed By
github-pages-deployer(S5) — deployed site URL to auditaffiliate-blog-builder(S3) — published articles to audit
Feedback Loop
- SEO audit results feed back to S3 Blog (content improvements) and S1 Research (niche opportunities from ranking data) — closing the SEO flywheel
chain_metadata:
skill_slug: "seo-audit"
stage: "analytics"
timestamp: string
suggested_next:
- "content-decay-detector"
- "internal-linking-optimizer"
- "keyword-cluster-architect"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.

