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