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 analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (not only report on them), use title-tag. For meta description rewrites, use meta-description.
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
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 analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel analysis," "traffic analysis," "traffic diversification," "natural traffic benchmark," or "organic vs paid traffic." For GA4 setup, use analytics-tracking.
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 promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia," "Quora," "Reddit community," "community building," "forum marketing," or "community invite." For Reddit copy, use reddit-posts. For strategy, use integrated-marketing.
When the user wants to submit a product or app to directories, curated lists, launch platforms, or app stores—and needs ready-to-paste copy per platform. Reads project-context.md when present. Also use when the user mentions "directory submission," "get listed," "app store listing," "submit to directories," "curated list," "best tools list," "Taaft," "Product Hunt," "directory ads," "newsletter feature," "directory campaign," "tailor description per platform," "Shopify App Store," "Chrome Web Store," "navigation site," or "product directory." For Product Hunt launch day tactics (hunter, first comment, timing), use product-hunt-launch. For full 0→1 channel planning, use cold-start-strategy.
When the user wants to launch on Product Hunt, prepare a PH submission, or plan launch day (hunter, first comment, timing, upvotes). Also use when the user mentions "Product Hunt," "launch on Product Hunt," "PH launch," "Product Hunt submission," "hunter," "Product of the Day," "upvotes," or "Product Hunt first comment." For multi-platform directory listings and paste-ready copy beyond PH, use directory-submission.