Diagnose an old or missing favicon in Google Search

Identify which image is actually wrong

Distinguish the small organic-search favicon from a Business Profile photo, social sharing image, or ad logo. Those use different publication systems. Save the result's hostname and the actual landing homepage. Editing a profile photo will not necessarily change a favicon served from website code.

Source checks: Google Search Central: Favicon requirements · Google Search Central: Introduction to robots.txt · Google Search Console: URL Inspection

Inspect the active homepage declaration

Open the public homepage and look for the supported icon link and its href. Record whether several templates or plugins emit different files. Check the hostname shown in the result, including www or a subdomain. Google's favicon documentation treats hostname-level sites distinctly, so do not assume a file on another host is the current declaration.

Fetch the icon directly and inspect the asset

Open the referenced file with a fresh request and confirm it is the intended recognizable square icon. Verify the public response, usable format, and actual served version. Google currently recommends an icon larger than 48 by 48 pixels; an illustrative 96 by 96 square provides a practical export target. Do not use an old minimum-size rule as the entire diagnosis.

Publish a stable, accessible correction

Use a small asset-release check.

• Update the actual homepage declaration or generating template.
• Serve the approved recognizable square file from a stable location.
• Check the homepage and icon are accessible to the relevant crawlers.
• Clear the supported website or CDN cache if it still serves the old file.
• Retest the public declaration and asset response.
• Record publication time and request appropriate homepage reevaluation where supported.

Avoid repeated file churn and unrelated image edits

Changing filenames every day can make your own evidence harder to track. Clearing a local browser cache may help verify the current server file but does not directly update Google's stored processing. Likewise, a new social sharing image does not repair an incorrect favicon link. Find the actual declaration before changing the entire brand kit.

Monitor the right result patiently

Recheck the same hostname and keep dated observations. Google's documentation allows for recrawling and processing time and does not guarantee favicon display. Report that the current public declaration and file are correct, then distinguish the remaining search observation from a failed website publication. Do not promise an instant refresh.

Add the icon to the website's brand asset register with file URL, dimensions, source owner, and checked date. Test it when changing a theme, domain, or homepage template. This helps keep a future redesign from quietly restoring an old file while the business assumes its visible header logo controls every external representation.

Illustrative header logo updated but favicon unchanged

An illustrative site displays a new header logo, while its homepage still declares /old-icon.ico. The editor updates the active icon declaration to the approved stable square asset, confirms the public file and crawl access, and records the date. The owner then monitors the organic result separately from Business Profile and social images.

The asset register records the approved icon declaration and file independently of the header logo. If the public file still returns the old image, the website publication is unresolved; if it returns the approved image, monitoring Google's later observation is a different follow-up.

Questions about this task