메뉴
Use when building or auditing public marketing pages, landing pages, blogs, or SEO metadata (title, description, OG, headings). Not for authenticated app dashboards behind login.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | seo-landing-page |
| description | Use when building or auditing public marketing pages, landing pages, blogs, or SEO metadata (title, description, OG, headings). Not for authenticated app dashboards behind login. |
Apply to public routes only (not app shell behind login). This skill is the entry point for marketing-page SEO.
Deep dives:
seo-meta-tags-spa — per-route titles, OG, canonicals in a SPAseo-structured-data — Schema.org JSON-LDseo-ssr-and-prerendering — populated HTML for crawlersseo-sitemap-generation — sitemap.xml + robots.txtseo-core-web-vitals — LCP, INP, CLSprogrammatic-seo-pages — templates at scale<title> (50–60 chars), meta description (150–160 chars).og:title, og:description, og:image (1200×630), twitter:card.h1; logical h2/h3 hierarchy (no skipped levels for styling).h1 and first paragraph naturally — no stuffing.header, main, footer, article./sitemap.xml and /robots.txt for indexable sites.json-ld Organization or WebSite on homepage when appropriate.Vite + React SPAs render an empty shell by default. For each public route, either:
<title> and meta tags via React 19's built-in tags (or react-helmet-async on older versions), ORVerify with curl -A "Googlebot" https://example.com/ | grep -i '<title' — title must be present in the raw HTML.
h1 hidden for SEO only.When auditing, return a table: URL | issue | fix priority (high/medium/low).
Use when reviewing or fixing accessibility: keyboard navigation, focus order, labels, color contrast, screen reader support, or ARIA attributes. Not for SEO-only or performance-only audits.
Use when adding product analytics (PostHog, GA4, Plausible), event tracking, funnels, or conversion measurement. Not for server logs only or A/B infra unless events are part of the task.
Use when standardizing API and edge function errors: HTTP status codes, error JSON shape, logging, or mapping Supabase/Stripe errors to client responses. Not for UI toast copy only or form field validation messages.
Use when recording audit trails: who changed what, admin action logs, compliance history, or append-only event tables. Not for product analytics (use analytics-events) or debug console logs only.
Use when scheduling background work: cron jobs, digest emails, cleanup tasks, pg_cron, Supabase scheduled edge functions, or job queues. Not for synchronous user-facing API in the request path.
Use when adding dark mode, theme toggle, system theme support, or fixing hardcoded colors that break in dark mode. Not for design-token migration unrelated to dark mode.