A favicon that appears in your browser tab can still be missing beside a Google result. Work through the image file, the home page link and crawl access separately before replacing the icon again. This checklist helps you identify a concrete fault and keep a record of what you changed.
Check the hostname and home page first
Google associates a search favicon with a hostname, not an individual article or subdirectory. Check the home page of the hostname in the search result. A separate subdomain can have its own icon. Follow Google’s current favicon guidelines: use a square, recognizable brand image, keep its URL stable and allow crawling of both the home page and icon. Googlebot needs the home page; Googlebot-Image needs the file.
Write down the final home page URL, the intended icon URL and the date of your last change. This avoids investigating a different host or repeatedly replacing a working asset while waiting for processing.
Prepare one clear PNG candidate
Google currently requires a square image at least 8 by 8 pixels and recommends a size larger than 48 by 48. PNG is a supported format. For this example, prepare a 96 by 96 PNG from an already square 512 by 512 master. The 96-pixel choice is a practical example, not a special ranking signal.
- Open the Image Resizer and load your square master.
- Choose Pixel dimensions under Resize by and leave Maintain aspect ratio checked.
- Set Width (px) to 96. Confirm the height also becomes 96.
- Choose PNG (.png) under Output format, then select Resize image.
- Check the reported dimensions and use Download result. Open the downloaded file to check its actual dimensions and appearance.
The resizer does not crop a wide logo into a square or install a favicon on your website. Prepare the composition first; unlocking the ratio to squash a rectangular logo is a poor substitute. Keep enough space around a simple mark so its edges remain recognizable when displayed small. Our resizing without stretching guide covers the aspect-ratio decision.
Inspect the published head link
Upload the candidate through your normal website workflow. On a hand-written site, a link in the home page’s <head> could look like this, assuming the file really exists at the example path:
<link rel="icon" type="image/png" sizes="96x96" href="/assets/site-icon-96.png">The sizes value describes the file; it does not resize it. MDN explains the icon relationship and how browsers choose between multiple declared icons. If your CMS already produces these links, update its existing icon setting and inspect the result rather than adding another competing declaration.
Follow the exact URL in the HTML
View the published home page source and find its icon link. Resolve a relative path against that page, then open that exact address. Use the browser’s Network panel to check the final response and image preview. A missing-file page, login screen or HTML error response needs fixing even if the URL ends in .png. Confirm the decoded image is the intended square asset. Reloading the home page alone does not check this separate request.
Check access before requesting another crawl
Review the live robots.txt rules for the home page and icon path, including any relevant crawler-specific groups. Also check whether authentication or a server rule prevents public retrieval. A successful request from your own browser is useful evidence, but does not establish what Google’s crawler received. The robots.txt and noindex guide explains why crawl restrictions and indexing instructions serve different purposes.
In the correct Search Console property, inspect the full home page URL. Compare the indexed result with a live test if the site has changed. Google’s URL Inspection documentation distinguishes those views and explains requesting indexing. Use that request after correcting a verified fault; a successful live test is not a favicon-display confirmation.
Keep the corrected setup stable
Google says recrawling and processing may take days to weeks, and an eligible icon is not guaranteed to appear. Record your checks: home page URL, linked icon URL, actual dimensions, response result and change date. If all remain correct, repeated filename changes make your diagnosis harder. Revisit a specific failing check when new evidence appears instead of assuming every delay needs a new image.