Why Is My Website Favicon Missing from Google?
Diagnose a missing Google favicon by checking the homepage icon, crawl access and branding before changing files repeatedly.
Part of our guide: Website SEO: A Beginner’s Guide for Small Businesses
A favicon is the small identifying image associated with your website. If Google shows a generic symbol or an old icon, start by checking which asset the public homepage actually supplies. Uploading a new logo to a page does not necessarily change the favicon.
This is a search-appearance problem, not proof that the website is unindexed or unsafe. Keep your investigation separate from broader ranking work in the business SEO guide.
Identify which image is wrong
Compare the browser tab, Google’s organic result and a link shared in a messaging app. These surfaces can use different instructions and refresh at different times.
If only a shared-link card is wrong, use the social-preview checklist. If the wording beside the icon is wrong, investigate the website name. Replacing every brand asset at once makes it difficult to establish what fixed the original issue.
Save a dated screenshot and the exact homepage address. Include whether the result uses the www hostname or another subdomain.
Check the public homepage
Ask your developer to inspect the homepage’s icon declaration and open its referenced image directly. Does that address return the intended image without a login, broken redirect or access challenge?
Google’s favicon guidance describes the homepage link declaration, crawl access and square-image requirements. It recommends an image larger than 48 pixels square, a stable icon URL and a recognisable representation of the site. Meeting the guidelines does not guarantee display.
A browser showing the right icon is useful evidence, but not proof that Google’s crawler can fetch the same asset. A cached local copy can disguise a broken public file.
Use a compact diagnostic record
Record the following before making changes:
| Check | Evidence to keep |
|---|---|
| Homepage address | Exact public URL and final destination |
| Icon declaration | Referenced asset URL |
| Asset availability | Successful image response without login |
| Brand match | Current icon compared with approved artwork |
| Change date | When the corrected homepage and file became available |
This is a suggested troubleshooting record, not a report exported by Google. It helps the owner and developer discuss one reproducible problem instead of conflicting screenshots.
Avoid artwork that disappears at small size
Test the icon at a small browser-tab size as well as at its original dimensions. A detailed landscape logo or a long business name can become an unreadable patch when reduced.
For an illustrative local plumbing business, the full van graphic might be unsuitable as an icon, while an approved simple mark remains recognisable. That is a design judgement, not a claim that a particular symbol improves rankings.
Retain the master artwork and document who approved the simplified version. Do not quietly invent a different identity just to fill the square.
Allow for retrieval and processing
Once the live declaration and image are correct, record the change and allow time for search systems to revisit them. Avoid changing the filename every morning in response to an unchanged result.
A developer can use the existing Search Console setup to inspect the homepage and request another crawl where appropriate. Google does not guarantee when it will refresh the displayed icon.
Decide what counts as completion
Technical completion means the correct public asset is declared, reachable and visually usable. Search-display confirmation is a separate observation with its own date.
Keep both statuses in the maintenance record. This avoids describing a successful local upload as a verified Google update, and gives the next person a clear starting point if the old image persists.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
