Google can show the wrong favicon when it finds an outdated icon, can't crawl your preferred file, or hasn't processed changes. A wrong Google search favicon can also result from a display bug on Google's side.
Your browser tab doesn't confirm Google shows the same image because each uses a separate cache. Check the live setup first, then request an update once you've fixed the issue.
Key Takeaways
- A working browser favicon doesn't guarantee the same icon will appear in Google Search.
- Google needs a square, accessible image and a supported favicon declaration on your homepage.
- Configuration changes can take several days to several weeks to appear, even after you request indexing.
Why Your Google Search Favicon Looks Wrong
An old logo and a default icon, often a globe icon, point toward different starting points. An old logo suggests outdated information somewhere. A globe icon can mean Google couldn't use your icon, hasn't processed it, or encountered a display problem.
Google and your browser store different copies
Your browser can display a locally cached favicon without downloading it again. Google separately crawls and processes your site's favicon for its search listing.
That means either version can be outdated. Your tab might show yesterday's logo while Google shows today's, or the reverse.
Your browser cache and Google's cache are separate. Clearing browser data won't refresh Google Search results. A correct icon in a private window doesn't explain a favicon not showing in results; it only confirms browser behavior.
Your website declares conflicting icons
Themes, plugins, and website builders can leave several icon declarations in the homepage. One may reference your current branding while another still references a platform logo.
A Stack Overflow favicon discussion describes a site showing the Vercel logo in search despite displaying its custom icon in the browser.
We recommend reviewing the actual homepage source for favicon declarations, rather than relying only on the upload screen. Search for rel="icon", touch icons, and references to old filenames.
Check Google’s Favicon Requirements
Google's favicon documentation sets eligibility rules, but meeting them doesn't guarantee a favicon will appear in Google Search.
Use these requirements to review your setup.
| Item | Requirement or recommendation |
|---|---|
| Shape | A square image with a 1:1 aspect ratio. |
| Dimensions | At least 8x8px; Google recommends 48x48px or larger. Common choices include 96x96px and 144x144px. |
| Supported formats | BMP, GIF, ICO, PNG, JPEG, PPM, and TIFF. |
| Link relationship | icon, shortcut icon, apple-touch-icon, or apple-touch-icon-precomposed. |
| File address | The href can be relative, absolute, or hosted on a CDN. |
| URL stability | Keep the favicon at a stable URL instead of changing its address repeatedly. |
| Branding | The image should visually represent your website's brand. |
For most sites, PNG or ICO are practical choices. PNG is straightforward to export and inspect. ICO can contain several resolutions in one file.
The 8x8px minimum is an eligibility floor, not a recommended working size.
An AI Overview may mention SVG, but Google's documented format list doesn't include it.
Google rejects inappropriate imagery, including pornography and hate symbols such as swastikas, and substitutes a default icon. A technically valid favicon can still fail this policy requirement.
Fix the Favicon File and Homepage Declaration
Open the favicon image address directly. It should return the intended image with a successful 200 OK response, without authentication or a security challenge.
Place the favicon link tag in the homepage's <head>. A simple PNG declaration is <link rel="icon" type="image/png" sizes="96x96" href="/favicon.png">.
The sizes value should match the image. For an ICO file, use <link rel="icon" href="/favicon.ico">. You don't need to declare every supported relationship.
Remove obsolete declarations, but keep intentional browser-specific alternatives, such as an apple-touch-icon, consistent with your branding. Then publish the change and purge the relevant hosting or CDN cache.
If your homepage declares the new icon but the CDN still returns the old image at that address, Google can fetch the wrong version.
Older guides describe Google shrinking icons to 16x16px for display. That display size isn't the recommended source size. A square 512x512px image can also qualify, but Google doesn't require that size.
We favor a clear symbol that remains recognizable when reduced. Small text and detailed logos often become unreadable.
Make the Homepage and Favicon Crawlable
A favicon file that loads for you can still be blocked from Google. Check access before changing the image again.
Check robots.txt and security restrictions
Googlebot must be able to crawl your homepage. Googlebot-Image must be able to crawl the favicon file. Neither should be blocked by relevant robots.txt rules.
If your favicon is hosted on a CDN, review that hostname's rules too. A broad block on an image directory can affect it.
Also inspect firewall settings, security plugins, and server responses. A 403, repeated 5xx errors, or a bot challenge can prevent Googlebot from retrieving the file.
Compare the origin response with the CDN response when they differ. Our technical SEO audit guide covers broader checks when access problems affect more than one asset.
Review hostnames and redirects
Google supports one icon per hostname. That means news.example.com can have its own icon, while example.com/news shares the main hostname's icon.
The same distinction applies to www.example.com and example.com. Check the domain shown in Google Search, along with its homepage and path.
One community report described an icon appearing after a 307 temporary redirect changed to a 301 permanent response. That's an anecdotal fix, not proof that every 307 blocks icons.
Use a permanent redirect when the domain move is permanent, and remove unnecessary redirect chains.
Request Indexing and Give Google Time
Once the live setup is correct, use Search Console to request another look at the homepage. Requesting the image URL alone isn't Google's recommended update workflow.
We suggest this sequence:
- Use the URL Inspection tool to inspect the exact homepage URL for the hostname appearing in search.
- Compare the indexed report with a live test to identify remaining access or page-level problems.
- Fix any outstanding issues, then select Request Indexing for the homepage.
- Record the change date and monitor without repeatedly replacing the file.
Our Google Search Console beginner guide explains the main reports and inspection tools.
Google says crawling and processing can take several days to several weeks. Its favicon cache can retain an earlier image after your website has changed. A Google support discussion on favicon refreshes also describes this delay.
A successful live test shows current accessibility, but it doesn't mean the result in Google Search has refreshed. Requesting reindexing doesn't guarantee an immediate update.
If the wrong icon persists beyond that window, revisit the declaration, response, hostname, and cache layers before making another image.
Favicon Fixes for Squarespace and Google Sites
Website builders simplify uploading, but uploading and appearing in Google Search are separate processes.
Squarespace: separate upload success from search refresh
A Squarespace forum user reported success with a 144x144px PNG declared with type="image/png" and sizes="144x144". The reported refresh took a few days to two weeks.
Treat that as one user's experience, not a Squarespace requirement or Google's deadline. The official processing window can be longer.
We recommend confirming that the published homepage references the uploaded icon and that the file is accessible. Replacing a valid image repeatedly won't resolve a processing delay.
Google Sites: publish the favicon change
Google Sites users reported missing search icons in 2024. A reported workaround for Google Sites involved a custom theme and a 48x48px image under Edit > Images > Favicon.
The current general upload route for Google Sites is Settings > Brand Images > Favicon, followed by publishing. Custom themes also have an Images route.
These steps configure the site; they don't force Google Search to refresh. Once published, the same favicon, crawling, and processing rules apply.
Recognize a Google-Side Favicon Bug
A sudden change across unrelated sites can point to Google's systems rather than separate website configurations.
Before changing anything, check for reports of a broader outage. Search Engine Roundtable's incident coverage is one source to review.
This doesn't explain every missing favicon. It does show why you shouldn't rebuild a setup that worked without evidence.
During a similar outage, confirm that your homepage and icon still load, keep the working setup, and follow confirmed updates.
Don't change file formats, rename files, or redirect a hostname just because several search results show a default icon at once.
Frequently Asked Questions
Does a missing favicon mean the page isn’t indexed?
No. A page can appear in search while Google displays a default icon. Icon selection and page indexing aren't the same status.
If the page itself is missing, investigate that separately. Our search indexing troubleshooting guide explains how crawling, indexing, and canonical selection differ. Changing the icon won't resolve a page-level exclusion.
Will a theme-color meta tag fix the search icon?
No. The theme-color meta tag controls interface coloring in supporting browsers. It doesn't tell Google which icon to display.
We recommend fixing the homepage's favicon link and image access instead. Likewise, an in-page logo or social sharing image doesn't replace the homepage declaration. Each has a different purpose.
Focus on the Live Setup, Then Allow Processing
The most reliable fix is a consistent, crawlable favicon on the correct hostname. Refreshing your browser won't confirm Google has processed it.
Fix configuration and access issues first, request homepage indexing, then allow time for processing. Keep the setup stable instead of making repeated changes to chase a cached result.
