メニュー
Comprehensive SEO, Core Web Vitals, and Semantic HTML review. Use when building any user-facing page, deploying new routes, or auditing search performance. Proactively suggest when new pages or dynamic routes are added to the project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Structured brainstorming for exploring new features or solving complex problems
Scope, architect, and plan new tasks
Multi-angle code review before merging
Summarize the day's work and put it in context
Wrap up work — atomic commits and push to origin
Full end-to-end (E2E) testing skill utilizing the browser. Make sure to use this skill whenever the user asks to "test the app", "run end to end tests", "verify the UI", "check if the app works", or wants you to use the browser to interact with and test the application flow. This skill orchestrates creating a test plan, getting user approval, navigating the application using the browser, independently fixing obstacles, and generating a progressive test report.
| name | seo-review |
| description | Comprehensive SEO, Core Web Vitals, and Semantic HTML review. Use when building any user-facing page, deploying new routes, or auditing search performance. Proactively suggest when new pages or dynamic routes are added to the project. |
| argument-hint | [URL or files to review] |
| disable-model-invocation | true |
Perform a deep technical SEO, Core Web Vitals, and structural review of the provided files or codebase.
title, description, og:image, og:title) correctly implemented and dynamic? Why: Missing or duplicate metadata causes search engines to generate poor snippets, reducing click-through rates.
useHead or useSeoMeta@section('meta') or equivalent<meta> tags in <head><link rel="canonical" href="..."> tag? Why: Without canonicals, duplicate URLs (query params, trailing slashes, pagination) split ranking signals.<meta name="robots" content="noindex, follow">? Why: Indexing internal pages wastes crawl budget and can expose sensitive URLs.srcset? Why: Unoptimized images are the #1 cause of slow LCP (Largest Contentful Paint).loading="lazy"? Why: Eager-loading all images blocks initial render and wastes bandwidth.width and height reserves? Why: Missing dimensions cause layout shifts that degrade user experience and CLS score.<h1> per page? Do subsequent headings follow a strict sequence (<h2> -> <h3> without skipping)? Why: Broken hierarchy confuses screen readers and reduces content comprehension by search engines.<article>, <nav>, <aside>, <main>) instead of pure <div> soup? Why: Semantic HTML enables accessibility tools, improves machine readability, and can trigger rich results.<img> tags have descriptive alt attributes? Why: Missing alt text fails WCAG compliance and removes images from image search results.robots.txt rules blocking helpful AI crawlers unnecessarily? Why: Blocking AI crawlers prevents your content from appearing in AI-generated answers and summaries.llms.txt file or easily parsable markdown variant available? Why: Structured machine-readable content improves discoverability in AI-powered search.Article, Product, Organization, LocalBusiness, FAQPage)? Refer to references/schema-templates.md for ready-to-use templates. Why: Schema markup enables rich results (stars, pricing, FAQs) that dramatically improve CTR.Report your findings categorized strictly by impact:
alt tags, broken heading hierarchy, layout shift risks.SEO REVIEW SUMMARY
──────────────────
Technical SEO: PASS | FAIL — [one-line summary]
Core Web Vitals: PASS | FAIL — [one-line summary]
Semantic Structure: PASS | FAIL — [one-line summary]
GEO/AEO: PASS | FAIL | N/A — [one-line summary]
Schema Markup: PASS | FAIL | MISSING — [one-line summary]
On-Page SEO: PASS | FAIL — [one-line summary]
E-E-A-T: PASS | FAIL — [one-line summary]
P1 Findings: [count]
P2 Findings: [count]
P3 Findings: [count]