Google's Favicon Docs Confirm SVG Favicons Are Not Supported
Google Search does not support SVG or WebP favicons. Its documentation, updated on 28 August 2026, now lists the seven image formats it does support: BMP, GIF, ICO, PNG, JPEG, PPM and TIFF.
This is a rule about favicons specifically, not a limit on what Google can decode. Google’s image guidelines list SVG and WebP among the formats Search supports for ordinary images, so the same file that works in an <img> element produces nothing as a site icon.
That matters most for SVG, because a single scalable icon is a common default in modern templates and framework starters. An SVG favicon renders perfectly in a browser tab, so a correct-looking tab is not evidence that Search can use the file. Where an SVG is the only icon a site declares, Google has nothing to display and falls back to a placeholder, in organic results and in AI Overviews and AI Mode citations alike.
The previous wording was less specific. It read “Any valid favicon format is supported”, with “valid favicon format” linking out to the Wikipedia article on favicons, which documents what browsers render, not what Google uses in its search results. That article carries a section headed “SVG favicons” describing them as well supported across modern browsers, and its format table gives SVG its own column. The wording had been in place for some time, appearing in Wayback Machine captures from June 2023, June 2024 and June 2025.
Google describes the update as a documentation change rather than a change in what Search supports:
Previously, the documentation linked to an external reference that evolved over time and caused ambiguity about which favicon file formats are actually supported in Google Search.
The check is quick. Right-click your home page, choose View page source, and search that page for rel="icon". If the only match points at an SVG, add a multi-size .ico or a PNG in one of the supported formats, and keep it at a stable URL, which Google’s guidelines also ask for.
Sources
More news
-
Google Confirms It Is Routing Search Result Links Through a goto Redirect
Google has confirmed it is routing search result links through a google.com/goto redirect, a technical measure that makes results harder to scrape.
-
Google Stops Auto-Correcting Double-Escaped JSON-LD
Googlebot now unescapes JSON-LD once instead of repeatedly, so structured data a template escaped twice is no longer corrected for you. Check your markup.
-
Google Releases an Embeddable Preferred Sources Button for Publishers
Google's new one-click Preferred Sources button keeps readers on the page. Measured: the two-line install pulls 470 KB across 23 requests to render it.