When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Guides signup and login page structure, domain choice, modal vs dedicated page, discount integration, and SEO. Signup is the conversion endpoint from landing pages and pricing; when discounts apply at registration (e.g., student discount), signup is the P0 placement. Distinct from landing-page-generator (acquisition); newsletter-signup-generator (email capture only).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and offers.
Identify:
| Option | Use |
|---|---|
| Main domain | /signup, /login, /auth; simple; common for SaaS |
| Subdomain | auth.example.com; Universal Login pattern; credentials not cross-origin; requires Cookie domain config for cross-subdomain session |
| Third-party | Redirect to Auth0, Clerk, etc.; provider hosts auth |
Paths: /signup, /login, /register, /auth; keep short and consistent.
| Approach | Use |
|---|---|
| Dedicated page | Account creation; discount verification; student verification; higher-quality leads; fewer fake emails |
| Modal / popup | Lightweight lead capture; newsletter; quick demo request; lower quality, higher volume |
When discount applies at signup (e.g., student 30% off): Use dedicated page—user needs space for verification, discount display, and form. Modal can work for simple email-only capture; avoid for full account + verification flows.
Mobile: Google penalizes intrusive interstitials; dedicated page avoids penalty.
| Section | Purpose |
|---|---|
| Headline | Value-focused; "Start free" or "Students: 30% off today, 15% off ongoing" |
| Trust signals | SSL, payment logos, privacy, customer logos; see trust-badges-generator |
| Media | Product screenshot, short video, or demo GIF above fold; reinforces value |
| Form | Minimal fields; email first; social login (Google, GitHub) reduces friction |
| Discount block | Student discount, annual discount, promo code; verification entry when applicable |
| Privacy / Terms | Links; compliance |
| Element | Placement |
|---|---|
| Headline or subhead | "Students: 30% off today, 15% off ongoing" |
| Verification | .edu, SheerID, UNiDAYS; verify at signup to apply discount |
| Eligibility | Brief eligibility; link to full terms |
P0 placement: When student discount applies at registration, signup page is primary; pricing page and homepage banner are P1.
| Page | Meta | Reason |
|---|---|---|
| Login | noindex, nofollow | No search value; security risk; indexed login pages can confuse users |
| Signup | noindex, follow | Block from SERP; allow crawl of links (Privacy, Terms) |
Implementation: Use <meta name="robots" content="noindex"> or X-Robots-Tag header. robots.txt does not prevent indexing—crawlers must access the page to read the directive. See indexing for full noindex page-type list.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.