Official statement
Other statements from this video 4 ▾
- 0:39 Can Google Search Console really measure the performance of your content on TikTok and Instagram?
- 1:10 How can you measure the impact of AI Overviews on your SEO traffic?
- 2:43 How will the new site reputation policy in the EEA transform your SEO strategies?
- 5:48 Could the favorite sources button be a game changer for niche site SEO?
Google Search and Discover do not display favicons in SVG format, unlike traditional raster formats. Essentially, if your site only uses an SVG favicon, it might appear without an icon in the SERPs, reducing your visibility and click-through rate. The immediate solution is to provide at least a PNG or ICO file as a supplement, even though SVG remains relevant for other contexts (PWA, browser tabs).
What you need to understand
What makes the SVG format problematic for Google?
Google has never publicly explained the technical reasons behind this restriction. It is assumed that the favicon processing engine favors simplicity and maximum compatibility with its caching and image resizing systems.
SVG files, while vector and lightweight, introduce additional complexity: they can contain embedded JavaScript (security risks), external calls, or unstable rendering depending on the browsers. Google likely prefers to rely on proven bitmap formats (PNG, ICO, JPEG) whose behavior is perfectly predictable at all resolutions.
Does this limitation apply everywhere?
No. SVG remains fully functional in browser tabs, PWAs (Progressive Web Apps), and all contexts outside of Google Search. Only Search result snippets and Discover cards are affected by this restriction.
In other words, an SVG favicon declared in your HTML will still display correctly when a user visits your site. The issue manifests only in Google SERPs, where the absence of a raster alternative leads to a blank or generic display.
How does Google detect the format to use?
Google analyzes the <link rel="icon"> tags in the <head> of your pages and downloads the referenced files. It generally respects the order of declaration and favors formats it knows how to handle: PNG, ICO, sometimes GIF.
If you declare multiple favicons in your HTML (a common practice to manage different resolutions), Google will choose the first compatible format. This is why it is essential to declare a PNG or ICO before any SVG, even if the latter is present for other uses.
- Google Search and Discover do not display SVG favicons, unlike browsers.
- Supported formats are PNG, ICO, and JPEG (though JPEG is rarely used for icons).
- Declaring an SVG alone leads to a blank display in the SERPs.
- The solution is to provide at least a 48x48 or 192x192 pixel PNG.
- This restriction only affects Google Search, not browser tabs or PWAs.
SEO Expert opinion
Is this statement consistent with field practices?
Yes, absolutely. For several years, tests have shown that Google systematically ignores SVG favicons in the SERPs. Sites that migrate to a single SVG favicon quickly notice the disappearance of their icon in the results, replaced by a generic placeholder or nothing at all.
This contrasts with the general web trend, where SVG is becoming the preferred format for icons (lightweight, scalable, Retina support). Google is lagging behind on this point, likely for reasons of operational reliability across billions of indexed pages.
What nuances should be added to this recommendation?
Google does not explicitly specify which format to favor between PNG and ICO. Observations in the field show a preference for the 192x192 pixel PNG, which offers maximum compatibility with high-resolution screens and PWAs. The ICO format remains functional but less flexible (fixed sizes, sometimes higher weight).
Another nuance: the declaration does not mention the behavior with multiple favicons (multiple sizes). In practice, Google usually chooses the first compatible file in the order of HTML declaration. Placing a good resolution PNG first ensures the best display. [To be verified]: no official documentation details the exact selection algorithm.
Are there cases where this rule does not apply?
No, the restriction seems absolute for Google Search and Discover. Even sites with very high authority or rich results (rich snippets, knowledge panels) do not escape this limitation. No exemptions observed.
In contrast, other engines like Bing or DuckDuckGo sometimes display SVG favicons without difficulty. This fragmentation of behaviors reinforces the need to provide multiple formats in parallel to ensure optimal display everywhere.
Practical impact and recommendations
What should you do to ensure the favicon displays correctly?
Add at least a <link rel="icon" type="image/png" href="/favicon.png"> tag in the <head> of all your pages, declaring a 192x192 pixel PNG file (or at least 48x48). Place this declaration before any SVG tags if you want to keep a vector favicon for other contexts.
Ensure the PNG file is accessible (HTTP 200), weighs less than 100 KB, and meets Google's visual guidelines: transparent or solid background, centered logo, sufficient contrast. Test the display with the rich results test tool or by directly searching your site in Google Search.
What mistakes should be avoided when migrating to modern favicons?
Do not abruptly delete your old favicon.ico from the root of the domain without checking that all your pages correctly declare a PNG in the HTML. Some CMS or frameworks continue to reference the default root file, and its disappearance can lead to massive 404 errors in Search Console.
Also, avoid declaring only an SVG thinking that Google will eventually support it: Mueller's declaration does not mention any deployment timeline. It's better to anticipate and provide a PNG now, even if you have to reassess in a few months if the situation changes. [To be verified]: no public roadmap on this point.
How can you verify that the favicon displays correctly in the SERPs?
Search for your site in Google Search (brand query or exact URL) and visually inspect the results. If the icon appears, everything is in order. If absent, check the Search Console in the Enhancements > Favicon section for any potential issues (file not found, unsupported format, incorrect size).
Also, use Google's rich results test to validate that the favicon is detected properly. At the same time, check the display in browser tabs: an SVG may work there but fail in the SERPs, confirming the need to test both contexts separately.
- Declare a 192x192 pixel (minimum 48x48) PNG file in the <head> of all pages.
- Place the <link rel="icon" type="image/png"> tag before any SVG declaration.
- Check that the PNG file is accessible (HTTP 200) and weighs less than 100 KB.
- Monitor the display in Google Search via a brand query or the exact URL.
- Consult Search Console (Enhancements > Favicon section) for any errors.
- Keep the favicon.ico file at the root of the domain to avoid 404 errors inherited from external links or bookmarks.
❓ Frequently Asked Questions
Google supportera-t-il un jour les favicons SVG dans les résultats de recherche ?
Un favicon SVG déclaré seul empêche-t-il l'indexation de mes pages ?
Quelle taille de PNG faut-il privilégier pour maximiser l'affichage dans Google ?
Puis-je déclarer à la fois un PNG et un SVG dans mon HTML ?
Le format ICO est-il encore pertinent ou faut-il passer exclusivement au PNG ?
🎥 From the same video 4
Other SEO insights extracted from this same Google Search Central video · duration 6 min · published on 26/10/2026
🎥 Watch the full video on YouTube →
💬 Comments (0)
Be the first to comment.