Promptwatch Logo

Google Favicon

A legacy Google fetcher that retrieved site favicons; Google now documents Googlebot-Image for favicon crawling.
GoogleGoogle Favicon
PreviewSearch Engine Crawler

What is Google Favicon?

Google Favicon is a legacy Google user agent that fetched a site's favicon so Google products could show the icon next to the site. Cloudflare still lists it, with the user agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36 Google Favicon.

Google's current favicon guidelines describe a different setup. Googlebot must be able to crawl the home page and follow redirects to the page where the favicon is declared, and Googlebot-Image must be able to crawl the favicon file. Neither URL may be blocked by robots.txt. The guidelines do not mention a separate Google Favicon fetcher.

Google's older crawler documentation said this fetcher ignored robots.txt for user-initiated requests, which is why compliance is listed as partial here. If you still see it, the request is either a rare legacy fetch or a client copying the string. Verify the source with Google's crawler IP checks before trusting it.

For the icon to show in Google Search, declare it with a <link rel="icon"> tag on the home page, keep the URL stable, and use a square image of at least 8x8 pixels. Google recommends larger than 48x48.

Not relevant for AI search

Is Google Favicon relevant for AI search?

No. Google Favicon fetched site icons for display in Google products; it does not read page content for AI search or training.

This fetcher only retrieved favicons. The icon shows next to your site in Google Search results, which affects how recognizable your listing is, but it carries no text an AI system could use. Google's current guidance says Googlebot-Image fetches favicons, so this legacy user agent now matters mostly for recognizing old log entries.

How to handle Google Favicon

There is no reason to block Google Favicon. It fetches one small file, and blocking favicon access can cost you the icon next to your listing in Google Search. Make sure the rules that matter today are in place: Googlebot can reach your home page and Googlebot-Image can reach the favicon file.

If you want a rule for the legacy token anyway:

User-agent: Google Favicon
Disallow: /

The token contains a space, and support for it is unclear, so do not rely on the rule. Use Google's reverse DNS or IP range checks to confirm that a request really came from Google.

Examples

  • A site owner finds an old `Google Favicon` request in archived logs and confirms with reverse DNS that it came from Google.
  • A team whose favicon disappeared from search results discovers that robots.txt was blocking Googlebot-Image from `/assets/`.

Frequently asked questions about Google Favicon

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard