skills/pages/utility/signup-login/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills signup-login-page-generatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
testing
When the user wants to create, audit, or optimize sitemap.xml. Also use when the user mentions "sitemap," "sitemap.xml," "sitemap index," "lastmod," "changefreq," "priority," "URL discovery," "URL discovery for search engines," "single source of truth," "URL config," "unify sitemap IndexNow," or "reduce duplicate maintenance." For IndexNow, use indexnow.
development
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
testing
When the user wants to create SEO pages at scale using templates and data—including AI-assisted, grounded copy for per-URL differentiation (vs rigid mail-merge templates). Also use when the user mentions "programmatic SEO," "programmatic SEO pages," "template pages," "scale content," "location pages," "city pages," "comparison pages at scale," "X vs Y pages," "integration pages," "pages from data," "automated landing pages," or "programmatic landing pages." Uses a playbook matrix aligned to skills under skills/pages. For user-facing template galleries or marketplaces (browse → use), use template-page-generator.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.