Is an icon declared?
Read supported rel values from the hostname homepage and resolve each unique public icon URL.
Verify the homepage declaration, live icon response, actual square dimensions, and Googlebot-Image access. Get a technical readiness verdict without a false promise that Google must display the icon.
RankLatch checks the evidence a site owner can control, then marks Google's later crawl and display decision as outside the result.
Read supported rel values from the hostname homepage and resolve each unique public icon URL.
Follow bounded public redirects, record the final response, content type, format, and byte size.
Inspect PNG, SVG, ICO, GIF, JPEG, or WebP geometry instead of trusting only declared sizes.
Evaluate applicable robots rules for both the homepage and final icon host using Googlebot and Googlebot-Image.
If the declaration, response, square geometry, minimum size, and crawler access pass, the useful next step is stability—not another redesign. Keep the favicon URL unchanged and give Google time to revisit the homepage.
Google Search Central favicon documentation ↗RankLatch stores the approved homepage state and checks it daily. A removed or changed favicon declaration becomes evidence alongside higher-impact title, canonical, robots, response, redirect, and heading drift.
See what RankLatch monitors →A correct new favicon can still show as a globe while Google refreshes its stored result.
Either Google has not processed the current homepage yet or one of the public technical signals is unresolved. This check separates observable setup issues—such as a missing declaration, blocked file, failed response, or non-square image—from the recrawl delay RankLatch cannot control.
Google documents a square image of at least 8×8 pixels and recommends an icon larger than 48×48 for display quality. RankLatch reads actual supported image geometry rather than trusting only the sizes attribute.
No. Google explicitly says favicon display is not guaranteed even when the guidelines are met. A passing result means the checked public technical requirements were observable at scan time.
Google says recrawling and processing a homepage can take from several days to several weeks. Requesting homepage indexing once is reasonable; repeatedly changing the favicon URL can work against the recommendation to keep that URL stable.
No. It checks the hostname-level public homepage, up to six unique declared icon URLs, and the relevant public robots.txt files through bounded read-only requests.
Rerun the checker to confirm the public state, request homepage indexing in Search Console if appropriate, then keep the icon URL stable. RankLatch monitoring can alert if the approved homepage favicon declaration later changes or disappears.