signup-login-page-generator

$npx mdskill add kostja94/marketing-skills/signup-login-page-generator

Generate, optimize, or audit signup and login pages.

  • Solves creating or improving user registration and authentication flows.
  • Depends on project context files and third-party auth services.
  • Decides based on goal, discounts, auth type, and audience.
  • Delivers structured guidance on domain, modal vs page, and SEO.

SKILL.md

.github/skills/signup-login-page-generatorView on GitHub ↗
---
name: signup-login-page-generator
description: 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.
metadata:
  version: 1.0.1
---

# Pages: Signup / Login

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.

## Initial Assessment

**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product, audience, and offers.

Identify:
1. **Goal**: Account creation, trial, paid signup
2. **Discounts**: Student, annual, promo code—apply at signup?
3. **Auth**: Self-built vs third-party (Auth0, Clerk, etc.)
4. **Audience**: General vs segmented (students, startups)

## Domain & URL

| 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.

## Modal vs Dedicated Page

| 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.

## Page Structure

| 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 |

## Discount Integration

### Student / Education (education-program)

| 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.

### Other Discounts

- **Annual discount**: Show when user selected annual plan from pricing; confirm before submit
- **Promo code**: "Have a code?" link or inline field; validate before or after submit

## Form & Verification

- **Minimal fields**: Email only when possible; add name only if needed; see **newsletter-signup-generator**
- **Social login**: Google, GitHub; reduces friction; faster than email form
- **Verification entry**: .edu (instant), SheerID/UNiDAYS (broader); see **education-program**
- **Progressive**: Collect email first; verify student; then complete profile if needed

## SEO

| 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.

## Output Format

- **Domain** and URL choice
- **Modal vs page** recommendation
- **Structure** (headline, trust, media, form, discount block)
- **Discount** integration (student, annual, promo)
- **SEO** meta tags
- **Related** skills for execution

## Related Skills

- **indexing**: Full noindex page-type list; noindex,follow vs noindex,nofollow
- **education-program**: Student discount at signup (P0); verification; placement
- **landing-page-generator**: Signup is CTA destination; landing page structure applies to signup when signup is conversion endpoint
- **popup-generator**: Modal option for lightweight capture; signup as full form → dedicated page
- **newsletter-signup-generator**: Form design; minimal fields; trust signals
- **trust-badges-generator**: Trust signals on signup
- **pricing-page-generator**: Pricing CTA → signup; annual discount flows to signup
- **website-structure**: /login, /signup in Standalone paths

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen 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.
about-page-generatorWhen 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.
affiliate-marketingWhen 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.
affiliate-page-generatorWhen 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.
ai-traffic-trackingWhen 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.
alternatives-page-generatorWhen 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.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.