mcpbeat

Footer Generator

kostja94/footer-generator

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.

902 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/kostja94/marketing-skills --skill footer-generator

The instruction itself

14 sections, as written by the author

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
  • 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 |

  • 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
  • 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

How to use it

Copy the folder

Take kostja94/footer-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.