使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/nmor/the-council --skill seo開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
SEO
Size budget: 6 KB. Use for search visibility work; do not load for every UI edit.
Inspect before prescribing
Identify the site, intended public/private sections, target audience, geography, languages, conversion goal and access to crawl logs or Search Console. Inspect the requested pages and relevant routing, rendering, robots, sitemaps and metadata code. Use actual evidence; do not claim to have crawled, inspected Search Console or measured Core Web Vitals without access. Preserve the established plan and site conventions.
Diagnose in order
- Access and indexability: HTTP status, redirects, crawl permissions, noindex,
canonical targets, sitemap URLs and rendered content. robots.txt controls crawling; it is not authentication or a reliable way to remove an indexed page. A crawler must be allowed to read noindex. Protect private content with access controls.
- Site architecture: reachable pages, descriptive internal links, useful hierarchy,
duplicate/faceted routes, pagination and retired URLs. Preserve relevant link equity with appropriate redirects; do not redirect unrelated pages merely to hide errors.
- Intent and content: identify the task behind each query, evidence for the page's
purpose, helpful original content, descriptive titles/headings and accurate snippets. Prefer maintaining useful pages over mass-generated thin location/keyword pages.
- Presentation: mobile behavior, accessibility, image alternatives, performance
and Core Web Vitals. Separate lab diagnostics from field data and establish a baseline.
- Enhancements: use supported structured data only for content actually present;
validate it. Add hreflang when real locale variants need it, with consistent canonical and reciprocal references. Do not invent reviews, ratings or business details.
Make a bounded change plan
For each finding provide the affected URL/template, observed evidence, consequence, recommended fix, priority, verification and rollback where relevant. Map queries to useful pages rather than forcing keyword repetition. Explain uncertainty in search intent if no research is available. Coordinate message claims with marketing-strategy and public copy with content-campaigns.
Verify and monitor
After authorized changes check response/redirect behavior, raw and rendered metadata, links, crawl directives and structured data as applicable. Distinguish local checks, publication, crawling and indexing. Record a Search Console baseline and compare query, page, country and device segments over appropriate windows; account for seasonality and other releases. Neither a local test nor sitemap submission proves indexing or ranking. Do not guarantee position, traffic or a fixed time to improvement.
Use Google Search Central primary guidance for current search behavior: SEO Starter Guide, robots.txt introduction and spam policies. Drafting recommendations does not authorize publishing, buying links or connecting external tools. Reject deceptive cloaking and scaled content made to manipulate search.