メニュー
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
Creates GitHub Actions for the Marketplace. Use when scaffolding a new action, implementing composite steps, writing BATS tests, or preparing a Marketplace release.
Audit documentation against its declared hierarchy — broken links, duplicates, misplaced content, stale references, single-source-of-truth enforcement. Use for doc health reviews.
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
Audits website accessibility for WCAG 2.2 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
| name | auditing-website-seo-geo |
| description | Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability. |
| compatibility | Designed for Claude Code |
| metadata | {"allowed-tools":"Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch","argument-hint":["url-or-file-path"],"stability":"stable","content-hash":"sha256:6fc16d33ad7c663af30e578ac2b6fe93b1737781ec4df878ac84c2a52ff3515b","last-verified-cc-version":"1.0.34"} |
Target: $ARGUMENTS
Audits a site for traditional SEO and Generative-Engine Optimization (GEO — visibility in AI search such as ChatGPT, Perplexity, Gemini, and Google AI Overviews) and generates implementable fixes. Prefer configuring the site or static-site generator so tags are emitted once (DRY) over hand-stuffing meta into every page. No over-analysis.
<title> (~30-60 chars, unique per page), <meta name="description">
(~120-160 chars, entity-clear), lang on <html>, charset, viewport
(no maximum-scale — it blocks zoom), robots, author, keywords,
format-detection, and a canonical link.og:title, og:description, og:url, og:type, og:site_name, og:image.twitter:card, twitter:title, twitter:description, twitter:image,
twitter:site, twitter:creator.WebSite / Organization (name, url, logo, sameAs) and per-page
Article / BlogPosting (headline, description, datePublished, author,
publisher, image). Validate against the matching schema.org type.robots.txt AI user-agents (GPTBot, ClaudeBot, Google-Extended, CCBot,
PerplexityBot, OAI-SearchBot) — the highest-leverage, best-honored lever.llms.txt at root — cheap, uncertain adoption; fine to keep.twitter:description and og:image / twitter:image may not be
emitted without explicit config or a per-page image. Fill only the genuine
gaps in a single shared include.Some checkers want mutually-exclusive lengths on a single shared tag:
og:title 25-35 vs twitter:title 50-70 — same tag, cannot satisfy both.og:description 55-65 vs <meta name="description"> 120-160 — same tag.Recommend the real-world optimum (Google limits plus GEO: a ~50-char title and a ~150-char description) and note the tradeoff rather than ping-ponging.
/.well-known/ai.txt is not a recognized standard (competing
vendor proposals, no IANA .well-known registration, no major adopter).
Skip it; do not spend effort on /.well-known/ai.txt.robots.txt AI-agent policy plus a full OG/JSON-LD set are what
actually move GEO and social previews.<head> — converting tools return markdown, so fetch
raw HTML when you need the tags verbatim.HIGH
- [Tag/issue] - Current: [value or "missing"] - Page: [url/path]
Fix: [code/config snippet]
MEDIUM / LOW
- [Tag/issue] - Current: [value or "missing"]
Fix: [code/config snippet]
- [ ] [Fix] - Impact: [High/Medium/Low] - scope: [site-wide | per-page]