Help Centre
Last updated: August 24, 2026
Getting started
Siteicons checks a single URL to find every favicon and touch icon it declares — plus the two files (/favicon.ico and /apple-touch-icon.png) that browsers request by convention even when undeclared.
What to check:
- Your own site — to verify the icons you deployed are reachable and correct
- A client's site — to diagnose why their icon isn't showing up
- Your own site after a deployment — to catch a missing or misconfigured icon before users notice
No account, no sign-up, no stored data. Every check is stateless — the results disappear when you leave or refresh the page.
Frequently asked questions
Siteicons runs on Cloudflare Workers. Cloudflare's own network cannot connect back to sites that are themselves behind Cloudflare. If your site is on Cloudflare (or if you checked a domain like example.com which is hosted on Cloudflare), the check will report it as unreachable.
This is a platform limitation, not a problem with your site. To verify your icons are serving correctly, either try a different site that isn't on Cloudflare, or check your site directly using browser DevTools (right-click → Inspect → Network tab, then look for favicon.ico and any <link rel="icon"> requests).
Several things can cause a false "missing" verdict:
- Broken relative paths. If your HTML uses a relative path like
href="favicon.ico"on a page at/blog/post/, the browser resolves it to/blog/post/favicon.ico— which may not exist. Use absolute paths (/favicon.icoorhttps://yoursite.com/favicon.ico). - Case sensitivity. Your web server likely treats
Favicon.icoandfavicon.icoas different files, even though your local filesystem didn't. - CDN cache. A CDN may not have propagated your latest deployment. Wait a few minutes and re-check.
- Authentication or IP restrictions. Siteicons cannot access icons behind a login wall, IP whitelist, or basic auth.
Check the HTTP status column in the results: a 404 confirms the URL really doesn't resolve. A 301/302 redirect often works fine — Siteicons follows them.
Google Search does not use the same icon signal as a browser tab. For Search results, Google mainly looks at:
- A
<link rel="icon">tag with a square image ≥ 48×48 pixels - The
og:imageOpen Graph meta tag (this is often what actually appears) - Search result icons are cached independently — it can take days or weeks for Google to re-fetch after a change
Siteicons does not check og:image — it only checks icon declarations. If your icon is correct in the tool but Google shows a blank, verify your og:image is present, is at least 1200×630 pixels, and is a supported format (JPEG, PNG, GIF, WebP).
To add a home-screen bookmark icon for iPhone and iPad users, add this tag to your page's <head>:
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
Best practices:
- Use a 180×180 pixel PNG image
- Place it at
/apple-touch-icon.pngin your site root — iOS requests this path by convention even without a declaration - If you don't declare one at all, iOS scales down the
/favicon.ico, which usually looks poor on a Retina display - Siteicons automatically checks both the declared URL and the root
/apple-touch-icon.pngfallback
Siteicons reads pixel dimensions from the binary header of image files. This works for ICO, PNG, JPEG, GIF, WebP, and SVG. If dimensions show as "-":
- The server didn't return the correct
Content-Typeheader, so the parser couldn't determine which format to expect - The icon was served with an HTTP error (non-2xx status), so the content wasn't retrieved
- The file is a format that doesn't embed dimensions in its header
When the icon is fetched successfully but dimensions can't be parsed, the verdict shows Unverified (yellow badge) instead of Present — it's served but we can't confirm its size. Magic-byte sniffing is attempted as a fallback for misconfigured servers, but this doesn't always succeed.
The Pro plan ($12/month) is designed but not yet built. Planned features include batch checking up to 10 URLs, saved check history, recurring scheduled checks, and webhook notifications when icons break.
Before Pro can launch, several things need to happen: the Pro features need to be developed, a payment processor (Stripe) needs to be connected, and a legal entity needs to be registered to accept payments. There is no estimated date for availability.
In the meantime, the Free plan works as described — single URL checks, no account needed, no data stored. It will remain free.
No. Siteicons does not store, log, or retain any data from your checks. Every check is stateless:
- The URL, the fetched page, and the icon responses exist only in memory during the API call
- Results are returned to your browser and discarded immediately after
- No accounts, no cookies, no databases, no external storage
- No analytics or tracking scripts are used on this site
This means you can check sensitive domains without worry — but it also means you can't go back and see what a previous check reported. If you need history, bookmark the results or save them yourself.
Known limitations
Siteicons is a straightforward diagnostic tool with honest boundaries. Here is what it cannot do:
- Cannot reach Cloudflare-hosted sites. The tool runs on Cloudflare Workers, which blocks connections back into its own network. Sites hosted on Cloudflare report as unreachable rather than closed. This is a platform limitation, not a defect.
- Only checks HTTP and HTTPS. FTP, data URIs, and other protocols are not supported.
- No account system. There is no login, no saved history, no dashboard. Every check is ephemeral.
- No payment processing. The Pro plan checkout on the pricing page is a demonstration only. No card data is sent, stored, or processed.
- Icon dimension parsing depends on server headers. Without a correct
Content-Typeheader, dimension extraction may fail even though the file is served. - No scheduled or recurring checks. Every check must be initiated manually. No webhook notifications.
- No API for programmatic access. The /api/check endpoint is intended for the app interface; there are no API keys, rate limit tiers, or documentation for external integrators.
Contact us
If you have found a bug, have a feature request, or need assistance, please be aware that there is no public contact route available today. The operator plans to add a contact method (email address or support form) once a legal entity is registered.
In the meantime, the App page is functional for free-tier use. The Terms and Privacy pages describe what the service does with your data (it does not store anything) and the current legal status.