ウェブサイトの技術的な健全性、オンページ最適化、コンテンツ品質、被リンクプロファイルを網羅した包括的なSEO監査を実行します。ユーザーがSEO監査、サイトレビュー、SEOヘルスチェック、「SEOの何が問題か」、ウェブサイト分析、またはサイトの検索パフォーマンスの完全診断を依頼した場合に使用してください。スピード特有の問題についてはaudit-speedを、技術的なクロール/インデックスの問題のみについてはdiagnose-seoを参照してください。
このスキルは、ウェブサイトの包括的なSEO監査を実施するための専門ツールです。技術的な健全性（クロール可能性、インデックス状況、サイトマップ）、オンページ最適化（メタタグ、見出し、コンテンツの関連性）、コンテンツ品質（重複コンテンツ、読みやすさ、キーワードの使用）、および被リンクプロファイル（被リンク数、ドメイン権威、リンク品質）の4つの主要領域をカバーします。ユーザーがSEO監査、サイトレビュー、またはパフォーマンスの問題を報告した際に、問題の根本原因を特定し、改善のための具体的な推奨事項を提供します。このスキルは、あらゆるウェブサイトで動作し、詳細なレポートを生成することで、開発者やマーケターがSEO戦略を最適化するのに役立ちます。スピードに関する問題は別のスキル（audit-speed）を、技術的なクロール/インデックスの問題のみはdiagnose-seoを使用することを推奨します。
npx skills add https://github.com/calm-north/seojuice-skills/tree/main/skills/auditInstalled? Explore more 研究＆データ分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
ウェブサイトの技術的な健全性、オンページ最適化、コンテンツ品質、および被リンクプロファイルを網羅した包括的なSEO監査を実行します。ユーザーがSEO監査、サイトレビュー、SEOヘルスチェック、「SEOの何が問題か」、ウェブサイト分析、またはサイトの検索パフォーマンスの完全診断を依頼した場合に使用してください。スピード特有の問題については、audit-speedを参照してください。技術的なクロール/インデックスの問題のみについては、diagnose-seoを参照してください。
This repo contains 13 individual skills — each has its own dedicated page.
Deep Core Web Vitals and page speed audit. Use when the user asks about page speed, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse scores, why a page is slow, performance optimization, or resource size analysis. For broader technical SEO issues, see diagnose-seo.
Turn competitor SEO data into a prioritized attack plan. Use when the user asks about competitor analysis, competitive gaps, how to outrank competitors, what competitors rank for, keyword overlap, or competitive positioning strategy. For building content to fill gaps, see brief and build-clusters.
Produce an editor-ready content brief for a target keyword or topic. Use when the user asks for a content brief, writing guidelines, article outline, SEO brief, what to include in a blog post, or how to structure content for a keyword. For choosing which topics to write about, see find-keywords. For a full site-wide SEO audit, see audit.
Build a topical authority cluster from a seed keyword or topic. Use when the user asks about topic clusters, content silos, pillar pages, topical authority, content architecture, or how to structure content around a theme. For finding the right keywords, see find-keywords. For writing individual pieces, see brief.
Design a link building campaign with prospect identification, asset creation, and outreach strategy. Use when the user asks about link building, backlinks, domain authority, how to get backlinks, outreach campaigns, digital PR, guest posting, or link acquisition. For internal linking, see fix-linking.
Structured diagnostic for technical SEO problems. Use when the user asks about crawl issues, indexation problems, why pages aren't being indexed, robots.txt questions, canonical errors, sitemap issues, rendering problems, or general technical SEO troubleshooting. For Core Web Vitals and page speed, see audit-speed.
Build a prioritized keyword list for a website, topic, or campaign. Use when the user asks about keyword research, finding keywords to target, building a keyword list, search demand, keyword difficulty, intent mapping, or which keywords to prioritize. For writing content around keywords, see brief. For grouping keywords into clusters, see build-clusters.
Design or audit internal link structure for a website. Use when the user asks about internal linking, link architecture, orphan pages, PageRank flow, anchor text, site structure, silo architecture, or why pages aren't ranking despite good content. For external link building, see build-links.
Guide a website migration without losing rankings — domain moves, CMS switches, URL restructures, HTTP to HTTPS, or redesigns. Use when the user asks about site migration, domain change, CMS migration, URL restructure, redesign SEO impact, redirect mapping, or how to move a site safely.
Optimize content for AI search engines — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews. Use when the user asks about AI SEO, AISO, getting cited by AI, appearing in AI answers, answer engine optimization, AEO, GEO, LLMO, AI Overviews, zero-click search, or how to appear in ChatGPT/Perplexity results. For traditional SEO, see diagnose-seo.
Build a local SEO strategy covering Google Business Profile, local citations, reviews, and NAP consistency. Use when the user asks about local SEO, Google Business Profile, Google Maps ranking, local pack, NAP consistency, local citations, review strategy, or ranking for "[service] near me" searches.
Diagnose and reverse traffic loss on existing pages. Use when the user asks about content decay, pages losing traffic, declining rankings, traffic drops, why a page stopped ranking, content refresh strategy, or when to consolidate vs redirect old content. For creating new content, see brief.
Identify and capture SERP features for target keywords — featured snippets, People Also Ask boxes, knowledge panels, and rich results. Use when the user asks about featured snippets, position zero, PAA optimization, rich results, schema markup for SERP features, or how to get more SERP real estate.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.