favicon-generator
# favicon-generator The favicon-generator skill provides guidance for implementing and optimizing favicons and app icons across browsers, mobile devices, and Google Search results. Use this skill when users need to create, audit, or troubleshoot favicon setups, mention specific icon types like apple-touch-icon or PWA icons, or want to ensure brand consistency in browser tabs, bookmarks, and home screens. The skill covers required sizes (16x16 through 512x512), format recommendations (SVG, PNG, ICO), and Google Search display requirements.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/favicon-generator && cp -r /tmp/favicon-generator/skills/components/branding/favicon ~/.claude/skills/favicon-generatorSKILL.md
# Components: Favicon Guides favicon and app icon implementation for brand consistency across browser tabs, bookmarks, mobile home screens, and **Google Search results**. Favicons help users identify sites; missing or incorrect icons hurt trust. **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 brand and visual identity. Identify: 1. **Tech stack**: Next.js, WordPress, static HTML, etc. 2. **PWA**: Is the site a PWA or planning to be? 3. **Existing assets**: Logo, icon files ## Required Sizes | Size | Use | |------|-----| | **16x16** | Browser tabs, standard displays | | **32x32** | Retina/HiDPI browser tabs | | **180x180** | Apple Touch Icon (iOS home screen); no transparency | | **192x192** | Android Chrome home screen, PWA launcher | | **512x512** | PWA splash screens, adaptive icons | **Optional**: 48x48, 96x96, 120x120, 152x152, 167x167, 256x256 for broader coverage. ## Formats | Format | Use | |--------|-----| | **SVG** | Modern browsers; scalable; supports dark mode via media queries; lightweight | | **PNG** | High-DPI; explicit sizes; easy to generate; required for Apple Touch Icon | | **ICO** | Legacy; bundles multiple sizes; fallback for older browsers | **Recommended**: Provide SVG + PNG fallbacks. Never skip Apple Touch Icon (180x180); iOS shows a generic screenshot without it. ## Google Search (SERP Display) See **serp-features** for SERP feature types and optimization. Favicons can appear in Google Search results next to your site's listings. [Google Search Central](https://developers.google.com/search/docs/appearance/favicon-in-search) requirements: | Requirement | Guideline | |-------------|-----------| | **Placement** | Add `<link rel="icon" href="/path/to/favicon.ico">` to **homepage** header | | **One per hostname** | One favicon per hostname; `example.com` and `code.example.com` are separate; `example.com/sub-site` shares the same favicon | | **Crawlability** | Googlebot-Image must crawl favicon; Googlebot must crawl homepage; do not block either in robots.txt | | **Shape** | Square (1:1 aspect ratio); minimum 8x8px; **preferably >48x48px** for quality across platforms | | **Stable URL** | Do not change favicon URL frequently | | **Appropriate** | No inappropriate content (pornography, hate symbols); Google may replace with default icon | | **Timing** | Crawling can take days to weeks; use Search Console URL Inspection to request indexing | **Supported rel values**: `icon`, `shortcut icon`, `apple-touch-icon`, `apple-touch-icon-precomposed`. **href** can be relative (`/favicon.ico`) or absolute; favicon can be hosted on CDN. ## Implementation ### HTML Link Tags ```html <link rel="icon" href="/favicon.ico" sizes="any"> <link rel="icon" href="/icon.svg" type="image/svg+xml"> <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32.png"> <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png"> ``` ### Next.js Place in `/app`: `favicon.ico`, `icon.png`, `apple-icon.png`. Next.js auto-generates tags. ### PWA Manifest Include `icons` array in `manifest.json` with 192x192 and 512x512 for maskable icons. ## Best Practices - **Simplicity**: At 16x16, complex details are illegible; use simplified logo mark; design for brand recognition in SERPs - **Consistency**: Favicon should match logo/brand (logo-generator, brand-visual-generator) - **Cache**: Use long cache; version for updates (e.g. `/favicon.ico?v=2`) - **Tools**: RealFaviconGenerator, favicon.io, or favicons npm package for automation - **Test**: Check across browsers, dark mode, and Search Console (favicon may take days to weeks to appear) ## Output Format - **Size** checklist (16, 32, 180, 192, 512; >48x48 for Google Search) - **Format** recommendations (SVG, PNG, ICO) - **Implementation** notes per tech stack (homepage header placement) - **Google Search** checklist (crawlability, stable URL, appropriate content) - **Manifest** (if PWA) ## Related Skills - **logo-generator**: Favicon typically derived from logo; consistent branding - **media-kit-page-generator**: Media kit should include favicon or link to brand assets - **brand-visual-generator**: Visual identity; favicon aligns with brand colors and mark - **indexing**: Favicon requires crawlable homepage; URL Inspection for indexing
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.