footer-generator
footer-generator helps design, optimize, and audit website footers for SEO, UX, and conversion. Use it when discussing footer design, navigation structure, link strategy, legal compliance, or footer-specific features like newsletter signups and sitemap links. The skill guides strategic link placement, accessibility standards, mobile optimization, and best practices for converting users below the fold, where significant engagement occurs.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/footer-generator && cp -r /tmp/footer-generator/skills/components/navigation/footer ~/.claude/skills/footer-generatorSKILL.md
# Components: Footer Guides footer design for SEO, UX, and conversion. Footers provide secondary navigation, support crawlability, and engage users below the fold (66% of engagement happens there). **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 key pages and audience. Identify: 1. **Site type**: Marketing, e-commerce, SaaS, blog 2. **Footer goals**: Navigation, lead capture, trust, legal 3. **Platform**: Web, mobile, both ## Essential Footer Elements ### Navigation & Links - Links to high-priority pages: About, Contact, Services, FAQs - Related blog posts and internal content links - XML or HTML sitemap links - Product/service category links (e-commerce) - **Avoid excessive links**: Google warns that too many internal links can harm SEO; link only to high-priority pages ### Business Information - Physical address, phone, email - Social media profile links (Follow us) -> distinct from **social-share-generator** (share this page) - Copyright and legal information (Privacy Policy, Terms of Service) ### User Engagement - Newsletter signup forms - Call-to-action buttons - Customer testimonials or support resources ## SEO Best Practices | Practice | Purpose | |----------|---------| | **Strategic linking** | Link to important pages; avoid link bloat | | **Descriptive anchor text** | Target keywords; avoid "Click here" | | **Text links** | Prefer text over images for crawlers | | **No dead ends** | Ensure pages link to other content | | **Semantic HTML** | `<footer>`, proper landmark roles | ### Link Strategy - Footer links help crawlers discover pages and understand site structure - Too many links can dilute page context; keep focused - Include sitemap link for comprehensive discovery ## UX Guidelines ### Placement & Visibility - Footer at bottom; visible without dominating desktop view - Mobile: Valuable for users who don't scroll to top - Secondary navigation; complements header nav ### Organization - Group links by category (Product, Company, Legal, Support) - Use clear headings for each column - Prioritize most-used links ### Accessibility | Requirement | Practice | |-------------|----------| | **Contrast** | 4.5:1 for link text | | **Touch targets** | >=44x44px on mobile | | **Keyboard** | Full keyboard navigation | | **Screen readers** | Proper heading hierarchy, landmark roles | ## Output Format - **Footer structure** (columns, link groups) - **Link list** with anchor text suggestions - **SEO** checklist - **Accessibility** checklist ## Related Skills - **navigation-menu-generator**: Footer complements header nav - **social-share-generator**: Footer has profile links (Follow us); social-share has share buttons (share this page) -> different use cases - **xml-sitemap**: Footer can link to sitemap - **internal-links**: Footer is secondary internal linking - **newsletter-signup-generator**: Footer often hosts signup forms
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.