FaviconIcon

Google Search · Rules checked

Favicon Not Showing in Google Search? What to Check

On this page

Start by separating the icon your browser can fetch now from the icon in a particular search result. Work through the evidence before replacing files again. This guide covers organic Google Search; advertising logos are a separate feature.

For the rules behind these checks, see Google’s favicon documentation. The steps below help you investigate your own setup; they do not establish what Google has already selected.

1. Confirm the affected site and symptom

Record the search-result URL, its hostname, the expected artwork, and when you last deployed the icon. A result for a subdomain or a different host deserves its own investigation. Compare the same site and artwork throughout the checks.

  • If the browser tab also has a problem, first review the general favicon troubleshooting guide.
  • If the tab looks correct but Search is missing an icon or shows an old one, continue with the public home page and its current image response.
  • Keep a dated note of your observations. A screenshot from your browser is evidence of that session, not of Google’s crawl history.

2. Inspect the home-page declaration

Open the home page for the hostname in the result and inspect its final HTML head. Record the icon links and their resolved URLs, including any redirects. Checking only an inner page can miss a different home-page configuration.

For a site served from the domain root, this example references a PNG included in the downloaded package:

Google Search favicon HTML
<link rel="icon" type="image/png" sizes="192x192" href="/android-chrome-192x192.png">

Place the file at the public URL used by the tag. Merge with existing framework metadata rather than pasting competing declarations. Check for starter icons, intentional route-specific icons, and older manual links before changing anything.

A file listed inside a web manifest is not a substitute for inspecting the home page. For framework-specific placement and metadata, follow the Next.js installation guide.

3. Verify the actual image response

Open the exact icon URL emitted by the page, then inspect its status, final destination, response type, and image content. Compare its dimensions with the Google Search size guidance. Use the existing 192×192 PNG as an example choice, not a requirement to export a new size.

Illustrative responses below are examples, not a live site report:

Observed evidenceWhat it establishesNext step
404 at the declared URLThat request did not return the file.Correct the path or deployment, then retry the same URL.
200 with an HTML error pageThe response is not the intended image.Review rewrites, authentication, and fallback pages.
200 with the expected 192×192 PNGThe image is available to this request.Continue with crawler-access and Google-processing evidence.

The Favicon Checker can help inspect declared icon requests and readable dimensions. Its requests are not Googlebot requests, and a passing score does not confirm search display.

4. Check crawler access, not just your browser

Review robots.txt rules for the home page and icon resources. Also check login requirements, redirect chains, CDN errors, and WAF or bot-challenge responses. A public page in your logged-in browser may behave differently for an automated request.

Googlebot needs home-page access and Googlebot-Image needs image access. When you have server or CDN logs, examine the relevant requests and their responses. Changing a User-Agent string alone does not authenticate a real Google crawler; use Google’s request verification guidance.

If you cannot access logs or the relevant controls, record crawler access as unverified. Keep ordinary HTTP results separate from evidence of actual Google requests.

5. Review Search Console evidence

With access to the appropriate Search Console property, inspect the home-page URL. Review the indexed version’s crawl information and compare it with a live test after correcting issues. These are different observations: a live test does not rewrite the indexed record.

Use the URL Inspection documentation to interpret the report. It is not a dedicated confirmation that a particular favicon is selected for a search result.

After a confirmed fix, an owner or full user can request indexing of the home page when appropriate. Record when you submitted it. Google’s recrawl guidance explains that processing may take days to weeks; repeated requests do not speed it up. Do not promise an appearance date.

6. Choose the next step from the evidence

A problem is confirmed
Fix the observed path, response, declaration, or access issue. Recheck the deployed response before requesting another crawl.
Further verification is needed
If request logs or Search Console data are unavailable, keep that uncertainty in your notes. Avoid changing working assets to compensate for missing evidence.
Files look correct; Search has not changed
Keep the icon URL stable, monitor the available crawl information, and allow time for processing. Clearing your local cache does not trigger that processing.

Frequently asked questions

Does a passing Favicon Checker result mean Google will show my icon?
No. The checker reports HTML declarations, remote icon requests, and readable PNG or ICO dimensions. It cannot confirm Google crawl history, icon selection, or search display.
Will clearing my browser cache update the icon in Google Search?
Clearing your local cache can help compare browser behavior, but it does not request a Google recrawl or establish that Google has processed your new icon. Check the served files and Search Console separately.
Can different folders have different favicons in Google Search?
Google uses one site favicon per hostname. Subdirectories share that site identity; a separate subdomain is a different hostname. Check the home page for the hostname in the search result.

Create and check your favicon files

Use FaviconIcon to generate a text favicon, or convert your own logo. Reuse the files that match your project and inspect your deployed setup with the checker.

For browser and device dimensions alongside the search-specific notes, return to the favicon size guide.