メニュー
Audits and fixes technical/on-page SEO — meta tags, Open Graph/Twitter cards, JSON-LD structured data, canonicals, sitemap, robots.txt; used when improving discoverability or fixing crawlability.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/Sir-chawakorn/sanook-cli --skill audit-technical-seoコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Gets machine-parseable JSON out of an LLM reliably — prefer provider-enforced grammar (OpenAI `response_format:{type:"json_schema",strict:true}`, Anthropic tool-calling / `tool_choice:{type:"tool"}`, Gemini `responseSchema`) over a "respond in JSON" prompt, define the contract once as a Pydantic/Zod model and validate every response (never trust the string), use constrained decoding / grammars for open weights (Outlines, llguidance, llama.cpp GBNF, vLLM `guided_json`), keep schemas SHALLOW with required fields + enums + `additionalProperties:false`, and build a repair-and-retry loop that handles refusals, `length`/`max_tokens` truncation, and streaming partial JSON (`partial-json-parser`). Schema-guided generation eliminates parse-error retries; validate-and-repair is the backstop, not the primary mechanism.
Builds production data grids that stay fast and accessible at 10k–1M+ rows — decide server-side vs client-side sort/filter/paginate by the dataset-fits-in-memory test (client only under ~10k rows, otherwise push to the API and treat the table as a controlled view of server state), ROW-VIRTUALIZE with TanStack Virtual or react-window so only the visible window mounts (fixed estimateSize, overscan 5–10, measureElement for dynamic rows, contain:strict, and a real scroll container — never table-layout:auto over thousands of rows), build the headless logic with TanStack Table v8 (or AG Grid when you need pinning/grouping/enterprise out of the box), add column resize/reorder/pin, inline edit with optimistic update + rollback on error, row selection with a stable rowId, full keyboard nav with roving tabindex over an ARIA grid (role=grid/row/gridcell, aria-sort, aria-rowcount/aria-rowindex so virtualization stays announced), position:sticky headers, streaming CSV export that doesn't block the main thread, and explici
Builds semantic/vector search — pick an embedding model + dimensionality (and whether to truncate Matryoshka dims) and the matching distance metric (cosine/dot/L2, normalize to unit length so cosine == dot and IP is correct), an ANN index with the recall/latency/memory tradeoff understood (HNSW M/efConstruction/efSearch for low-latency RAM-resident; IVF-PQ nlist/nprobe/PQ for billion-scale compressed; flat/exact for <100k) in pgvector/Qdrant/Milvus/FAISS/Pinecone, chunking + overlap + per-chunk metadata for filtering, HYBRID retrieval fusing BM25 + dense by Reciprocal Rank Fusion (RRF, k≈60) not score addition, a cross-encoder/Cohere reranker over the top-50→k, correct pre-filter-vs-ANN interaction (filterable HNSW, not post-filter that starves k), and offline eval with recall@k / nDCG@10 / MRR against a labeled qrels set. Quantize (scalar/PQ) only after measuring recall loss; tune efSearch/nprobe to a recall target, not a guess.
| name | audit-technical-seo |
| description | Audits and fixes technical/on-page SEO — meta tags, Open Graph/Twitter cards, JSON-LD structured data, canonicals, sitemap, robots.txt; used when improving discoverability or fixing crawlability. |
| when_to_use | When the user wants SEO improvements, mentions meta tags, Open Graph, schema.org/JSON-LD structured data, sitemap, robots.txt, canonical URLs, crawlability, or indexing. |
Trigger this skill when the request involves: improving search discoverability/indexing, adding or fixing <title>/<meta> tags, Open Graph or Twitter Card previews, schema.org / JSON-LD structured data, canonical URLs, sitemap.xml, robots.txt, hreflang, or "why isn't this page showing up / previewing right on social". No API keys, crawler accounts, or paid tools required — this is static analysis + code fixes on the project's own source.
Skip if the ask is about off-page SEO (backlinks, content strategy, keyword research) or Core Web Vitals performance — those are different jobs (use a Lighthouse/perf pass for the latter).
Detect the stack first, then audit head-out. Output a missing-items report with concrete diffs, don't just describe.
Detect framework + render mode. grep -rl "next" package.json etc. Branch:
export const metadata / generateMetadata() in layout.tsx/page.tsx. Do NOT hand-write <head> tags; they get stripped.next/head <Head> component, or _document.tsx for site-wide.<head> directly or the framework's head API.
Find existing tags: grep -rniE "og:|twitter:|application/ld\+json|rel=.canonical|<title|name=.description" src/ app/ public/.Title + meta description. Every indexable page needs a unique <title> (aim ≤60 chars so it isn't truncated in SERP) and <meta name="description"> (≤160 chars, written for click-through, not keyword-stuffed). Flag pages sharing the same title/description as duplicate-content risk. In Next: set title (string or { default, template }) and description in the metadata object.
Open Graph + Twitter Card. Required for correct social previews:
og:title, og:description, og:type (website/article), og:url (absolute), og:image (absolute URL, 1200×630, <5MB), og:site_name.twitter:card = summary_large_image, twitter:title, twitter:description, twitter:image.
In Next, use the openGraph and twitter keys (Next auto-emits the <meta> tags). Images must be absolute — set metadataBase: new URL("https://example.com") so relative image paths resolve, otherwise OG images silently 404 for crawlers.JSON-LD structured data. Pick the type that matches the page: Article/BlogPosting (blog), Product + Offer (commerce), BreadcrumbList (nav trail), FAQPage (Q&A), Organization/WebSite (site-wide, in root layout). Emit as <script type="application/ld+json"> with JSON.stringify — in React use dangerouslySetInnerHTML, never {JSON.stringify(...)} as a text child (React escapes the quotes and breaks parsing). Include all required props for the type (e.g. Article needs headline, image, datePublished, author). Validate the shape against schema.org before declaring done.
Canonical URLs. Each page must self-reference a single absolute canonical (<link rel="canonical"> / Next alternates.canonical). Audit for conflicts: trailing-slash variants, ?utm_/query params, http vs https, www vs apex all resolving to the same content without one canonical winner. Paginated/filtered list pages each canonical to themselves, not page 1.
sitemap.xml + robots.txt.
sitemap.xml: lists only indexable, canonical, 200-status URLs (no redirects, no noindex pages, no admin/auth routes). Next: app/sitemap.ts. Verify <loc> URLs are absolute and match canonicals exactly.robots.txt: must NOT Disallow paths you also list in the sitemap or want indexed. Confirm it points to the sitemap (Sitemap: https://example.com/sitemap.xml). Check no stray Disallow: / left from a staging config.Heading + semantic HTML. Exactly one <h1> per page, no skipped levels (h1→h3), descriptive not styling-driven. Use <main>, <nav>, <article>, <header>; alt on content images. This is the crawler's content map — don't leave it as <div> soup.
hreflang (only if i18n). For multi-locale sites, every locale variant lists reciprocal hreflang tags including a self-reference and x-default. Skip entirely for single-locale sites — wrong/partial hreflang is worse than none.
Report. Produce a table: page · issue · severity · concrete fix (with the diff). Apply the fixes, then re-audit.
<head> in Next App Router — React strips it on the server. Must go through the metadata API.metadataBase — crawlers and social scrapers can't resolve them; previews break and canonicals get ignored. Always absolute, or set metadataBase.<script>{JSON.stringify(data)}</script> HTML-escapes the quotes (") and the data won't parse. Use dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}.noindex/redirected/non-canonical URLs — sends mixed signals; sitemap must only contain final indexable canonicals.robots.txt Disallow vs sitemap conflict — disallowing a URL that's in the sitemap (or carries noindex) wastes crawl budget and confuses indexing.<h1> — common with component-based layouts where a shared header and the page both render an h1, or neither does.noindex left in from staging — grep for noindex / robots: { index: false } before shipping; a single leftover tag silently de-indexes the page.curl -s <url> | grep -iE "og:|twitter:|canonical|<title|ld\+json" (or DevTools → Elements). Tags must exist in the server-rendered HTML, not injected client-side after load — crawlers read the initial response.@type per schema.org (Google Rich Results Test / Schema Markup Validator for a live check)./sitemap.xml (well-formed XML, absolute <loc>, no 404/redirect/noindex entries) and /robots.txt (references sitemap, doesn't block indexable paths).