Design-first ideation workflow — explore user intent, clarify constraints, propose approaches, and produce an approved design document before planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before auditing, understand:
Site Context
Current State
Scope
Robots.txt
XML Sitemap
Site Architecture
Crawl Budget Issues (for large sites)
Index Status
Indexation Issues
Canonicalization
Core Web Vitals
Speed Factors
Tools
Check for:
Common issues:
Check for:
Common issues:
Check for:
Common issues:
Primary Page Content
Thin Content Issues
Check for:
Check for:
Common issues:
Per Page
Site-Wide
Experience
Expertise
Authoritativeness
Trustworthiness
Executive Summary
Technical SEO Findings For each issue:
On-Page SEO Findings Same format as above
Content Findings Same format as above
Prioritized Action Plan
Free Tools
Paid Tools (if available)
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Design-first ideation workflow — explore user intent, clarify constraints, propose approaches, and produce an approved design document before planning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate Conventional Commits spec git commits (auto-separate by feature)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. Emphasizes deep research, modular content architecture, and varied section types beyond feature tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," or "content planning." For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," or "CTA copy." For email copy, see email-sequence. For popup copy, see popup-cro.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.