Full Icon-Set Coverage
Goes beyond favicon.ico to detect rel=icon, apple-touch-icon, manifest icons, msapplication tiles, and theme-color in one pass.
Favicon and Touch Icon Checker
TL;DR: Favicon & Touch Icon Checker checks detect and validate the full modern icon set: favicon.ico, rel=icon, apple-touch-icon, manifest icons, and theme-color. so you can confirm the current issue, understand when it matters, and move directly into the next fix without leaving the browser.
Audit the full modern icon set a page references and probe every icon URL for a real, working image response.
更新されました
Loading tool interface...
favicon.ico and rel=icon detection apple-touch-icon size validation Web app manifest icons[] parsing Maskable and theme-color checks Live broken-icon probing
What does Favicon & Touch Icon Checker do?
The Favicon & Touch Icon Checker fetches a live page, parses the <head> for every icon declaration, reads the linked web app manifest, and probes each icon URL to confirm it returns a 200 response with an image content type.
Why it matters for SEO and brand: Your favicon is the first brand impression in a browser tab, a bookmark, and Google's mobile search results, where it appears beside your listing. A missing or broken favicon makes a listing look untrustworthy and lowers click-through. Search engines also fetch and cache these icons independently of the page, so a broken icon URL silently degrades your presence even when the page itself is fine.
The modern icon set is bigger than favicon.ico: Browsers now expect a layered set — a classic favicon.ico, a scalable rel=icon SVG, a 180x180 apple-touch-icon for iOS home screens, manifest icons[] (including a maskable variant) for Android and installable PWAs, and a theme-color for the mobile browser chrome. This tool checks each layer instead of assuming one .ico file is enough.
Manifest validation, not just detection: When a web app manifest is linked, the checker fetches it, validates the JSON, and inspects every entry in icons[] — confirming each src resolves, returns an image, and declares sizes and purpose. It flags manifests that parse but ship no reachable icons, a common cause of blank PWA install prompts.
Catch broken, oversized, and missing icons before users do: Each icon is probed with a HEAD request and a ranged-GET fallback (so CDNs that mishandle HEAD don't trigger false negatives). The report calls out 404s, redirects, non-image content types, undersized apple-touch-icons, and bloated icon files that slow first paint.
When should you use Favicon & Touch Icon Checker?
Favicon & Touch Icon Checker is most useful when you need a direct answer on a live URL or draft before you change templates, ship content, or rerun a wider audit.
このツールの使用方法
- 1 Enter the URL of the page you want to check.
- 2 The tool fetches the head, parses every icon link, and reads the web app manifest.
- 3 Each icon URL is probed for a 200 response and an image content type.
- 4 Review the coverage checklist, fix flagged or broken icons, then rerun.
What should you do next?
After validating your icons, audit the rest of your head with the meta tag checker, confirm social images with the Open Graph checker, and trace any icon redirects with the redirect checker. Then move to the related checks below to confirm the fix on the live canonical page.
得られるもの
Live URL Probing
Probes every icon with a HEAD request plus a ranged-GET fallback to confirm a real 200 and image content type, catching 404s and CDN mishaps.
Manifest Deep Check
Fetches and validates the web app manifest, inspecting each icons[] entry for reachable images, declared sizes, and a maskable purpose.
Frequently Asked Questions
Favicon & Touch Icon Checker についての回答
You should ship both. A root /favicon.ico remains the most compatible default — browsers and crawlers request it implicitly even when no link tag exists. Layer a modern <link rel="icon" type="image/svg+xml"> on top so high-DPI screens render a crisp, scalable mark. This checker flags pages that rely on only one of the two.
180x180 pixels is the recommended size. iOS uses the apple-touch-icon for home-screen shortcuts and downscales it for smaller contexts, so a single 180x180 PNG covers modern devices. The tool warns when an apple-touch-icon is declared at a smaller size or is missing entirely, since iOS otherwise renders a blurry screenshot instead of your icon.
Because the manifest controls your installed and PWA icon, not the favicon. Android and installable web apps pull their icon from the manifest's icons[] array, and a maskable icon is needed for adaptive shapes. The checker fetches the manifest, validates the JSON, and probes each icon src so a parse error or an unreachable icon doesn't silently break your install experience.
It hurts visibility and trust more than rankings directly. Google shows your favicon next to mobile search listings, and a missing or broken icon makes the result look less credible, which can lower click-through. Search engines cache icons separately from the page, so a 404 icon URL degrades your presence even when the page returns 200. Fixing broken icons is a quick, high-visibility win.