How to install footer-generator
npx skills add https://github.com/kostja94/marketing-skills --skill footer-generatorFull instructions (SKILL.md)
Source of truth, from kostja94/marketing-skills.
name: footer-generator description: When the user wants to design, optimize, or audit website footers. Also use when the user mentions "footer," "page footer," "site footer," "footer links," "footer navigation," "footer SEO," "footer design," "footer CTA," "multi-column footer," or "footer sitemap." For main nav, use navigation-menu-generator. metadata: version: 1.0.1
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:
- Site type: Marketing, e-commerce, SaaS, blog
- Footer goals: Navigation, lead capture, trust, legal
- 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
Related skills
More from kostja94/marketing-skills and the wider catalog.
generative-engine-optimization
When the user wants to optimize for AI search visibility (ChatGPT, Claude, Perplexity, AI Overviews). Also use when the user mentions "GEO," "AEO," "generative engine optimization," "AI search visibility," "LLM optimization," "GitHub GEO," "Grokipedia," "optimize for ChatGPT," "AI Overviews," "Bing Copilot," "Yandex AI," "Perplexity optimization," "GEO strategy," or "AI search optimization." For third-party publishing strategy (which platforms to use), use parasite-seo. For GitHub repos, README, and Awesome lists, use github. For Medium.com only, use medium-posts. For Grokipedia edits, use grokipedia-recommendations. For traditional Google SERP strategy, use seo-strategy.
github
When the user wants to use GitHub for SEO, parasite SEO, GEO, open source marketing, README optimization, or curated Awesome lists. Also use when the user mentions "GitHub," "GitHub SEO," "GitHub parasite SEO," "GitHub GEO," "awesome list," "GitHub README," "profile README," "pinned repositories," "Trending," "Explore," "repository name," "About section," "GitHub description," "GitHub topics," "Website field," "GitHub Pages," "github.io," "user site," "project site," "GitHub gist," "curated list," or "navigation list." Not for Medium or other non-GitHub platforms—use parasite-seo or medium-posts. For OSS business model, use open-source-strategy.
glossary-page-generator
When the user wants to create, optimize, or audit glossary page content and structure. Also use when the user mentions "glossary," "definitions," "terminology," "industry terms," "glossary page," "term definitions," "vocabulary," "glossary SEO," or "definition page." For definitions at scale, use programmatic-seo.
google-ads
When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube ads." For paid mix, use paid-ads-strategy.
google-search-console
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.
grid
When the user wants to design, optimize, or audit grid layouts for content display. Also use when the user mentions "grid layout," "grid design," "multi-column grid," "CSS grid," "responsive grid," "card grid," "product grid," or "feature grid." For cards layout, use card.