tools-page-generator
tools-page-generator guides the creation, optimization, and auditing of free standalone utility pages designed to drive traffic and generate leads. Use this skill when the user wants to build or improve free tools pages, calculators, checkers, or toolkit hubs that serve the same audience as a paid product and leverage programmatic SEO for scalability.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/tools-page-generator && cp -r /tmp/tools-page-generator/skills/pages/content/tools ~/.claude/skills/tools-page-generatorSKILL.md
# Pages: Tools (Free Tools) Guides free tools pages that drive traffic and lead generation for the main product. **Tools are free, standalone utilities** — not the primary monetization. They serve the same ICP as the paid product, are often extracted mini-features from the full product (low dev effort), and typically scale via programmatic SEO. Distinct from features (paid capabilities) and resources (content hub). **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, ICP, and conversion goals. Identify: 1. **Tool types**: Calculators, checkers, converters, generators (see Tool Types below) 2. **ICP alignment**: Same audience as paid product; tools solve related problems 3. **Format**: Single tool page vs. toolkit hub + per-tool pages 4. **Gate strategy**: No signup (max traffic) vs. email gate (lead capture) vs. usage limits (taste → upgrade) 5. **Tech**: Often SPA (single-page application); lightweight, fast load ## Tools vs Features | Dimension | Tools | Features | |----------|-------|----------| | **Monetization** | Free; not primary revenue | Paid product capabilities | | **Purpose** | Lead gen, traffic, trust | Conversion, evaluation | | **Content** | Standalone utility; excerpt from product | Full product capability list | | **Scale** | Many tools; programmatic keywords | Fewer, curated | | **Format** | Often SPA; toolkit hub | Benefit-led grid/list | | **User intent** | "I need to do X now" (task) | "What can this product do?" (evaluation) | ## Tool Page Structure | Section | Purpose | |---------|---------| | **Headline** | Task-focused; "Free [X] Checker" or "Calculate [Y] in Seconds" | | **Tool UI** | Input → process → output; minimal friction | | **Instructions** | 1–3 steps; "Enter URL → Click Analyze → Get Results" | | **Tool description** | What it does, who it's for; SEO content | | **FAQ** | Tool-specific: "What is [X]?", "How is [Y] calculated?" | | **CTA** | "Get full access" / "Try [Product] free" — link to main product | | **Related tools** | Internal links to other tools in toolkit | ## Toolkit Hub Page Structure | Section | Purpose | |---------|---------| | **Headline** | "Free [Category] Tools" or "Free Tools to [Outcome]" | | **Category tabs/sections** | e.g., SEO Tools, AI Writing Tools, Local SEO (Semrush pattern) | | **Tool cards** | Name, one-line benefit, CTA to tool page | | **How to use** | Short ordered procedure (often 3 steps for hubs); e.g. Choose tool → Enter info → Get results. Section **H2** per **howto-section-generator**—prefer outcome/tool-led (“How to use these tools”) or “In *N* steps …” **only** when *N* matches the visible steps | | **CTA** | "Access 50+ tools with free account" | | **Social proof** | Logos, "Trusted by X brands" | ## Tool Types (Common Patterns) | Type | Examples | Programmatic potential | |------|----------|-------------------------| | **Calculators** | ROI, LTV, loan, salary, carbon footprint | "[X] calculator" keywords | | **Checkers** | SEO, backlink, plagiarism, grammar, keyword rank | "[X] checker" keywords | | **Converters** | Unit, currency, file format, encoding | "[X] to [Y] converter" | | **Generators** | Sitemap, meta tags, FAQ schema, titles | "[X] generator" keywords | | **Analyzers** | Content, readability, sentiment | "[X] analyzer" keywords | ## Best Practices ### Lead Gen Focus - **Taste of product**: Tool delivers instant value; CTA offers "more" (full product, higher limits) - **No signup preferred** for top-of-funnel; email gate or limits for bottom-of-funnel tools - **Usage limits**: e.g., 3 checks/day free → upgrade for unlimited (Semrush, Ahrefs pattern) ### Same ICP, Lower Friction - **Extract from product**: One capability from full product; low dev cost - **Same keywords**: Tools rank for "[X] tool" while product ranks for "[X] software" - **Bridge**: Tool users → trial signup when they hit limits or need more ### Programmatic SEO - **Keyword patterns**: "[keyword] checker," "[city] [tool]," "[X] calculator" — template + data - **Scale**: Many tools; each targets long-tail; see **programmatic-seo** - **Template**: Same structure per tool; unique input/output, FAQ, meta ### Technical - **SPA-friendly**: Single page, client-side processing; fast load - **Schema**: SoftwareApplication, HowTo for tool pages - **Mobile-first**: Tools often used on-the-go ## URL Structure | Pattern | Example | |---------|---------| | **Hub** | /tools, /free-tools | | **Category** | /free-tools/seo, /tools/calculators | | **Per tool** | /free-tools/seo-checker, /tools/roi-calculator | ## SEO - **Intent**: Informational + Transactional (task completion) - **Title**: "Free [X] Tool \| [Product]" or "[X] Checker — No Signup" - **Programmatic**: Template + keyword/data; avoid thin content; each tool adds unique value ## Output Format - **Tool list** (types, names, keywords) - **Toolkit hub structure** (if multiple tools) - **Per-tool page structure** (sections, CTA placement) - **Gate strategy** (no signup vs email vs limits) - **Internal linking** (hub ↔ tools, tools ↔ product) - **Programmatic template** (if scaling) - **SEO** metadata ## Related Skills - **card**: Tool card structure; name, benefit, CTA; grid layout for toolkit hub - **grid**: Toolkit hub grid layout; responsive columns - **features-page-generator**: Tools ≠ features; tools are free lead gen; features are paid capabilities; link from tools to product/features - **programmatic-seo**: Tools at scale; template + data; keyword patterns - **resources-page-generator**: Tools can be a section in resources; or standalone /tools - **landing-page-generator**: Tool page as lead-capture LP when gated - **schema-m
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.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When 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.
When 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.