Google Search Favicons and Site Names: A Troubleshooting Guide for Small Businesses
A missing logo beside a Google result is usually not one problem. It may involve the favicon file, the homepage declaration, the hostname Google indexed, crawl access or simply the time needed to process a change.
- Identify whether the wrong element is the favicon, site name, page title or organization logo.
- Verify a square, crawlable favicon and a stable homepage icon declaration.
- Confirm the canonical hostname and its redirects agree.
- Use one valid
WebSiteentity on the homepage for the preferred site name. - Keep organization identity and logo markup consistent, but do not treat it as a favicon control.
- Inspect the live homepage, request one recrawl and allow processing time.
First identify the search element that is wrong
Business owners often call every brand image in Google a “logo,” but the search interface contains several independent elements. The small image beside an organic result is the favicon. The text beside or above the result is the site name. The blue result heading is the page title link. A logo in a business or knowledge panel is another asset. A Google Business Profile photo or logo belongs to the profile rather than the organic website result.
That distinction matters because each element has a different source. Replacing a Google Business Profile logo will not directly replace the favicon that Google reads from the website. Adding an organization logo to structured data does not substitute for a homepage favicon declaration. Rewriting a page title does not set the site name.
For a new Charlottesville or Central Virginia business website, the fastest route is to name the exact element that is missing, confirm its source, and test only the relevant layer.
What Google requires for an organic-result favicon
Google’s current favicon guidance says a site becomes eligible by providing a qualifying icon and adding a supported icon link in the homepage header. The icon must be square, at least 8 by 8 pixels, and crawlable by Googlebot-Image; Google recommends a size larger than 48 by 48 pixels for appearance across surfaces. The favicon URL should remain stable.
Eligibility is the correct expectation. Google explicitly notes that a favicon is not guaranteed to appear even when a site follows the requirements. Treat the work as removing preventable obstacles, not as a promise about the final presentation.
A practical implementation normally includes a root-relative declaration such as <link rel="icon" href="/favicon.ico"> or a supported image type. The declaration belongs in the homepage <head>. A browser tab showing the right icon is encouraging, but it does not prove that Google can crawl the file or that the indexed homepage contains the same declaration.
Use a dedicated square mark—not a wide wordmark
A wide business logo usually becomes unreadable when reduced to favicon size. Create a simple square brand mark with enough contrast and clear negative space. Test it against both light and dark browser surfaces and at very small sizes. A recognizable initial, monogram or compact symbol is often more useful than the full company name.
Do not stretch or crop the wide header logo at runtime and assume the result will be legible. Maintain a dedicated source asset and export the favicon variants intentionally. The broader image SEO guide explains how dimensions, formats and descriptive context affect other website images, but the favicon has its own search-specific rules.
Check the hostname Google is actually using
Google supports one favicon per site, with the site defined by hostname. That means www.example.com and portal.example.com can use different favicons, while a subdirectory cannot define a separate favicon for organic results. This becomes important after a domain change or when a site serves both www and non-www versions.
Choose one canonical hostname and make the alternatives redirect to it consistently. Then verify that the final homepage—not only a preview or staging deployment—returns the intended icon declaration. A common failure is updating the icon on the noncanonical version while Google indexes the redirected destination.
The website ownership and handoff checklist covers domain, DNS, hosting and source control because search appearance can drift when nobody knows which environment is authoritative.
Verify the favicon file as a crawler would
Open the favicon URL directly. It should return a successful response, the intended image, and an appropriate image content type without requiring a login, cookie or browser-only script. Confirm that robots rules do not block the file and that Google can crawl the homepage itself. A working image inside a logged-in content manager does not establish public crawl access.
Also check that the live HTML contains the icon declaration after deployment. Theme settings, build pipelines, caching layers and content-delivery networks can leave production serving an older head section even when the source file looks correct. The technical SEO audit guide provides a broader crawlability and metadata review when the issue is not limited to the favicon.
The site name is a separate homepage signal
Google’s site-name documentation explains that the displayed site name is generated automatically. Google considers the homepage, references elsewhere on the web, og:site_name, titles, headings and other homepage text. The strongest direct preference is WebSite structured data on the domain or subdomain homepage.
The required fields are the preferred name and the canonical homepage url. An alternateName can supply a recognized abbreviation or domain-based fallback. Keep the preferred name consistent with the visible header, homepage copy, metadata and organization identity. Do not create several competing WebSite nodes or attempt to assign a different site name to each service folder.
Google also notes that site-name processing can take days or weeks after a recrawl. A correct deployment can therefore coexist temporarily with an old or domain-based label in search.
Do not confuse Organization logo markup with the favicon
Google’s Organization structured-data guidance allows a representative organization logo and says the logo image must be at least 112 by 112 pixels, crawlable and indexable. This markup can help Google understand the logo a business prefers for supported search and knowledge experiences.
That is useful identity information, but it does not replace the favicon link or the homepage WebSite site-name entity. A sound homepage may contain all three: a favicon declaration for the small result icon, WebSite data for the site-name preference, and Organization or an appropriate LocalBusiness subtype for the business identity.
Use one coherent entity graph when possible and keep names, URLs, telephone numbers and logo references consistent. The service-business schema guide explains why accurate, visible facts are more useful than adding every possible property.
Why changing the file may not change Google immediately
Favicons and site names depend on Google revisiting and processing the homepage. A browser may show a new icon immediately because it fetched the asset directly, while search results continue to reflect previously processed information. CDN caches, browser caches, production build caches and Google’s own crawl timing are different systems.
Keep the favicon URL stable after the correct asset is in place. Repeatedly renaming the file or adding new versioned URLs can make the source harder to follow. If a cache must be invalidated during deployment, verify that the stable public URL ultimately returns the new bytes.
Request one recrawl, then monitor
Google’s recrawl guidance recommends the URL Inspection tool for a small number of changed URLs and a sitemap when many URLs need discovery. For a favicon or site-name change, inspect the canonical homepage, test the live URL and request indexing once the rendered HTML and icon response are correct.
Google says recrawling can take from a few days to a few weeks and that repeated requests do not make the process faster. A request also does not guarantee an immediate or particular search appearance. The Search Console setup service can establish the ownership and reporting access needed for this inspection workflow.
A reliable troubleshooting order
- Name the element. Decide whether the issue is the favicon, site name, page title, organization logo or Business Profile media.
- Confirm the canonical homepage. Follow redirects and identify the hostname Google should index.
- Inspect the live head. Verify the canonical tag, icon link and any
WebSitedata on the public production response. - Open the icon URL. Check the status, file type, square dimensions, clarity and crawl accessibility.
- Check identity consistency. Match the preferred site name across visible homepage branding, metadata and structured data.
- Validate schema syntax. Confirm that the homepage has one coherent
WebSiteentity and accurate organization information. - Inspect with Search Console. Test the canonical homepage as Google sees it and request one recrawl after deployment.
- Allow processing time. Record the change date and recheck periodically instead of making daily speculative edits.
What not to do
- Do not upload a new Google Business Profile logo and expect the organic favicon to change.
- Do not use a wide wordmark as the only favicon source.
- Do not block the favicon path or homepage from crawlers.
- Do not maintain different brand names across the homepage, structured data and organization references without a real reason.
- Do not add multiple conflicting
WebSiteentities. - Do not switch favicon URLs repeatedly while waiting for a recrawl.
- Do not promise a display date or guarantee that Google will use the preferred presentation.
Favicon and site-name checklist
- The canonical homepage returns HTTP 200 after redirects.
- The homepage contains a supported
rel="icon"declaration. - The favicon URL returns the intended public image without authentication.
- The icon is square, clear at small size and larger than Google’s minimum.
- Googlebot and Googlebot-Image are not blocked from the required resources.
- The favicon URL is stable.
- The homepage has one valid
WebSiteentity with the preferred name and canonical URL. - Visible branding and metadata use the same business name.
- Organization logo markup describes the organization logo rather than substituting for the favicon.
- The canonical homepage has been inspected and, if appropriate, submitted once for recrawling.
- The change date and follow-up check are documented.
Sources
- Google Search Central: Define a favicon to show in search results
- Google Search Central: Provide a site name to Google Search
- Google Search Central: Organization structured data
- Google Search Central: Ask Google to recrawl your URLs
Related services and guides
Make the live site and the search signals agree.
STANDBY Local builds and improves business websites with practical technical SEO, consistent brand assets and maintainable search documentation. Call (434) 872-1893 or email hello@standbylocal.com to discuss a website serving Charlottesville, Albemarle County & Central Virginia.