In this guide
- First, separate the three possible causes
- Eight checks, in a practical order
- What an actual UVs archive check can—and cannot—prove
- Troubleshooting matrix: what each result tells you
- What to send a developer instead of “the favicon is broken”
- Frequently asked questions
- A sensible next step for a rebuilt website
Quick answer: If your favicon appears in a browser tab but Google Search shows a generic globe, start with the homepage favicon link, the actual image dimensions, the live file response and crawler access. Google's current rules require a square favicon at least 8 × 8 pixels and recommend a larger image. Once the site is correct, Google still needs time to recrawl and process it; appearing in Search is not guaranteed. Google Search Central: favicons.
A rebuilt website can look correct in Chrome or Safari while its search listing still has the default globe. Re-uploading the logo or repeatedly submitting a sitemap may feel productive, but those actions can miss the problem. The useful distinction is between what the website serves and what Google has processed and chosen to show.
For an HTML/CSS/JS website—particularly one deployed from a ZIP—start with the public homepage and actual server files. Do not base the diagnosis on a local preview or an article page alone.
First, separate the three possible causes
- File problem: the image is rectangular, unreadable, incorrectly sized or no longer available.
- Deployment/crawl problem: the homepage points to the wrong path, the file is blocked, or the old files are still live.
- Processing delay or display decision: the setup appears valid, but Google has not refreshed its information or has not chosen to display the icon.
Google's official instructions explicitly state that compliance gives eligibility, not guaranteed display. This is favicon-specific Search appearance guidance—not a newly launched ranking change.
Eight checks, in a practical order
1. Verify that the icon is square and legible
Inspect the image itself, not the name favicon.png. Google requires a 1:1 aspect ratio with minimum dimensions of 8 × 8 pixels and recommends a favicon larger than 48 × 48 pixels. For a business website, a 96 × 96 or 192 × 192 PNG is a convenient implementation choice. Google's published rules do not require every dimension to be a multiple of 48. Source: Google Search Central.
For example, a 320 × 199 logo is still rectangular after being renamed favicon.png. The correct repair is to use a legible square brand symbol, not to stretch the entire horizontal logo until it is distorted. Google accepts valid favicon formats. A square PNG is a straightforward starting point for this example; the declared type and dimensions must match the file.
2. Check the actual homepage <head>
Open the page source for the public home URL—not a blog article, local HTML file or staging preview. A minimal declaration looks like this:
<link rel="icon" type="image/png" sizes="96x96" href="/favicon-96x96.png">
The filename is illustrative. The path must resolve on the deployed hostname. A matching .ico fallback or Apple touch icon may be supplied for other browsers/devices, but avoid keeping conflicting links to retired icon files. Google also supports certain apple-touch-icon declarations; /favicon.ico is not a mandatory filename. The asset can be served from a CDN if the URL remains accessible. Source: Google Search Central.
3. Test the file with an actual GET request
Open the image URL in a private browser window. For a developer using macOS or Linux, this command checks the live response without assuming that a server handles HEAD requests correctly:
curl -sSL -o /dev/null -w 'HTTP %{http_code} | %{content_type} | %{url_effective}\n' \
https://example.com/favicon-96x96.png
For this illustration, a successful result should normally include HTTP 200, a matching image content type such as image/png, and the intended final URL. Also open the downloaded file and inspect its dimensions. A server can respond 200 while returning an HTML error document instead of an image. A 403, 404, sign-in page, security challenge or redirect to a retired staging domain needs attention before any request to Google.
4. Check Googlebot and Googlebot-Image access separately
Google states that Googlebot must be able to crawl the homepage and Googlebot-Image must be able to crawl the favicon file. Inspect the live /robots.txt and any CDN or server firewall rules. If the favicon lives under /assets/, a broad crawler-specific disallow rule for that directory can matter. Source: Google favicon guidance; robots.txt guidance.
Google Search Console's URL Inspection tool helps you check the homepage, but a successful inspection is not proof that Googlebot-Image fetched the icon. Use server/CDN logs and access rules for that part of the investigation; do not present a browser test as crawler evidence.
5. Keep the favicon URL stable while fixing caches
Google advises keeping the icon URL stable. Verify that the latest image bytes are served at the declared URL, purge the relevant server/CDN cache when appropriate and reload the homepage source. Repeatedly renaming the file does not force Google to refresh it. Clearing your own browser cache only changes what you see locally. Source: Google Search Central.
6. Check the hostname that searchers actually reach
Google supports one Search favicon per hostname. www.example.com and example.com are different hostnames; /blog/ is a path, not a separate site-level favicon. After a redirect, rebuild or host move, confirm the destination homepage has the correct icon link and does not still reference an old staging host or deleted WordPress uploads folder. Source: Google Search Central.
7. Compare the ZIP, the document root and the live response
A ZIP may contain the correct file, yet the hosting file manager may extract it under an extra new-site/ directory. In that case, the public homepage can still be serving the previous version. Record three pieces of evidence side by side: the icon path in the packaged index.html, the matching file inside the archive, and what that same URL returns publicly.
Preserve .htaccess, analytics/verification files, server-side endpoints and unrelated content when correcting a custom HTML website. Do not delete and replace the entire document root merely to repair a favicon.
8. Request a homepage recrawl only after the fixes
Once the public files and crawl access check out, an authorized Search Console user can inspect the homepage URL and request indexing if that option is available. Google says recrawling and processing may take several days to several weeks, and repeated requests do not make crawling faster. A sitemap helps discovery, but it is not a favicon refresh switch. Sources: Google favicon guidance and request recrawling.
What an actual UVs archive check can—and cannot—prove
We checked a retained UVs Digital Hub static-site release archive. Its homepage declared /favicon-48x48.png, /favicon-96x96.png and /favicon.ico, and matching files were present in the ZIP. We measured the two PNGs: they were 48 × 48 and 96 × 96 pixels, respectively. This is a reproducible archive-level check, not a claim about customer traffic or search performance.
Those observations confirm that the package contains internally consistent icon references. They do not establish that a hosting provider deployed those same bytes, that Googlebot-Image fetched the resource or that Google Search showed the brand icon. That distinction is why the live-response and recrawl checks matter.
Troubleshooting matrix: what each result tells you
| Observation | Most useful next check | What the evidence does not prove |
|---|---|---|
| Browser tab shows the icon; Search shows a globe | Dimensions, homepage link, crawler access | That Google has accepted or refreshed the icon |
Packaged icon exists but public URL returns 404 |
Extraction folder, document root and filename case | That requesting indexing will fix a missing file |
Icon URL returns 200 but displays HTML |
Response body, CDN error routing and content type | That the path serves a usable image |
| Correct image loads but Search remains unchanged | Fix date, homepage recrawl and hostname | That the icon will show on a specific date |
www and non-www differ |
Redirect destination and each host's homepage source | That an article-level favicon controls the whole host |
What to send a developer instead of “the favicon is broken”
Share the searched hostname, a screenshot of the actual Google result, the homepage URL, the icon URL, the icon's pixel dimensions, the HTTP response and the deployment date. Add a note about any move from WordPress, a change in hosting or a ZIP replacement. That lets the developer separate an asset issue from a crawl or display delay without guessing.
A wider website review should also check titles, canonicals, redirects and broken resources. Our 20-point website audit checklist covers those broader topics, and UVs's website maintenance service explains how a defined technical review is scoped. The free website audit is a useful first pass, but it does not replace a live favicon/crawler investigation.
Frequently asked questions
Will fixing my favicon improve my rankings?
Do not expect a guaranteed ranking change. Google's favicon documentation describes an aspect of Search-result appearance, not a ranking reward for uploading a square image. Fix it for accurate brand presentation and technical consistency. Google Search Central.
Does Google require exactly 48 × 48 pixels?
No. Google's current published minimum is a square 8 × 8 pixels, with a recommendation for larger than 48 × 48 pixels. A 96 × 96 PNG is one practical option, not a magic size. Google Search Central.
Can Search Console force Google to update the icon today?
No. You can request a homepage recrawl, but Google controls scheduling and display. Repeating the request does not guarantee faster processing. Google's recrawl instructions.
Can each blog page show a different favicon in Google Search?
Not on the same hostname. Google supports one favicon per hostname; separate subfolders do not get independent Search favicons. Social-sharing images are a different asset. Google Search Central.
Is this the same as the business logo in Google Ads?
No. The Google Search favicon guidelines cover organic search results. Google Ads has separate business-logo specifications. Do not assume fixing one asset automatically resolves the other. Google Search favicon documentation.
A sensible next step for a rebuilt website
If the favicon is only one of several problems after a rebuild—missing files, inconsistent redirects, broken forms or unexpected crawl restrictions—start with a file-to-live comparison. UVs Digital Hub can assess a defined technical SEO and website maintenance scope without promising a particular Google display date.
Get in touch with the affected URL and the date of your last deployment. We can review what the website controls and identify the next practical fix.
Official sources and editorial transparency
- Google Search Central — Define a favicon to show in search results (rechecked for this revision on 31 October 2026).
- Google Search Central — Ask Google to recrawl your URLs (verified 27 October 2026).
- Google Search Central — Introduction to robots.txt (verified 27 October 2026).
The archive observation comes from UVs Digital Hub's own retained website ZIP, inspected for this revision. The example example.com command is illustrative. The featured image and flowchart are editorial illustrations; they do not depict Google results or customer data. No ranking, CTR, indexing or client outcome is claimed.