# Favicons in Google Search: Review the Icon Google Can Crawl

<a id="main-content"></a>

SEO &amp; Search

October 28, 2026  ·  7 min read  ·  Victor Valentine Romo

On this page

1. [Name the Surface Under Review](<#name-the-surface-under-review>)
2. [Follow the Homepage Declaration to the File](<#follow-the-homepage-declaration-to-the-file>)
3. [Check the Image Before Proposing a Replacement](<#check-the-image-before-proposing-a-replacement>)
4. [Inspect Homepage and Asset Access Separately](<#inspect-homepage-and-asset-access-separately>)
5. [Walk Through a Fictional Missing-Icon Case](<#walk-through-a-fictional-missing-icon-case>)
6. [Copy an Icon Review Worksheet](<#copy-an-icon-review-worksheet>)
7. [Keep the Correction Bounded](<#keep-the-correction-bounded>)
8. [Sources](<#sources>)

The browser tab shows the company mark. The search screenshot shows a generic icon. Someone opens a design ticket to export the same artwork again.

First inspect the path from the homepage declaration to the image.

This review follows one icon across that path. The worksheet is a proposed operating method. The business, image properties, access records, and search captures below are fictional. They illustrate an investigation without claiming a private inspection or a search result.

<a id="name-the-surface-under-review"></a>

## Name the Surface Under Review

Google's favicon guidance concerns organic results. Advertising logos have separate requirements. A favicon can be eligible without appearing. [Google's documentation](<https://developers.google.com/search/docs/appearance/favicon-in-search>) makes those boundaries explicit.

Open the review with a concrete complaint: “The saved organic result for the consultancy homepage shows a generic icon.” Attach the capture and its destination. Keep the browser-tab observation in a separate field.

For a fictional business called Alder Advisory, the initial record might contain three entries:

| Surface | Synthetic observation | Review assignment |
| --- | --- | --- |
| Browser tab | Alder mark visible in the editor's browser | Record browser and page used |
| Organic search result | Generic icon in saved capture | Inspect homepage declaration and asset access |
| Advertising result | Not examined | Outside this review |

The browser observation remains useful. It identifies what the editor saw in that environment. It does not answer the access questions assigned to the website maintainer.

Avoid a ticket titled “Google logo broken.” It leaves the surface, host, asset, and observed problem unspecified. Another person could spend the review examining an advertising account that nobody intended to change.

Keep social cards and body images outside this record. Use the [B2B diagram image review](</articles/image-seo-b2b-diagrams/>) for an explanatory asset inside an article. Here the object is a small site identifier and the route that supplies it.

<a id="follow-the-homepage-declaration-to-the-file"></a>

## Follow the Homepage Declaration to the File

Google reads the homepage's favicon `link`. It supports `icon`, legacy `shortcut icon`, and two Apple touch-icon relations. The image address can be relative, absolute, or [hosted elsewhere](</articles/image-sitemap-cdn-audit-b2b/>). Search supports one icon per hostname, including its subdirectories. [The implementation guidance](<https://developers.google.com/search/docs/appearance/favicon-in-search#implementation>) describes this setup.

For the proposed review, copy the declaration before opening the image. Preserve the attribute values exactly. Record which homepage revision supplied them.

This synthetic declaration points to a fictional asset:

```html
<link href="/brand/alder-mark.png" rel="icon" type="image/png">
```

In the worksheet, resolve that path against the reviewed homepage and record the complete destination. Give the asset its own row. A declaration review and a file review should produce separate evidence.

If the homepage contains several candidates, list them. Ask the maintainer which component generated each declaration. Do not delete unfamiliar markup during an inspection. First establish the intended asset and the system responsible for maintaining it.

Record alternate hosts separately. In the fictional inventory, `alder.example.com` serves the consultancy while `learn.alder.example.com` serves teaching material. The `/resources/` path belongs under the consultancy host. Use that inventory to keep assignments bounded.

If an asset lives on another service, name its owner in the worksheet. The website editor may control the homepage without controlling the image host. An unresolved ownership question is a concrete handoff item.

<a id="check-the-image-before-proposing-a-replacement"></a>

## Check the Image Before Proposing a Replacement

Google currently requires a square image of at least 8 by 8 pixels and recommends dimensions above 48 by 48. Its supported formats are BMP, GIF, ICO, PNG, JPEG, PPM, and TIFF. Keep the URL stable and the artwork representative. [The current image guidance](<https://developers.google.com/search/docs/appearance/favicon-in-search#guidelines>) supplies those criteria.

Record actual properties from the reviewed file. Separate [filename](</articles/file-delivery-manifest-business-handoffs/>), decoded format, width, and height. A file ending in `.png` should still receive a format inspection in the proposed process. Copying its name alone does not complete that row.

For Alder's invented image, assume the inspection reports PNG, 96 pixels wide, and 96 pixels high. The width-to-height ratio is one. The example clears the stated minimum and the larger-size recommendation.

Keep that conclusion limited to the properties examined. The record still needs access evidence and an owner to accept the artwork as the intended identifier. Passing a dimension check does not complete the review.

Ask the owner to view the proposed mark at a small display size. In this editorial exercise, the question is whether the selected file is recognizable as [the intended business identifier](</articles/google-site-names-b2b-websites/>). Avoid turning the review into an unsolicited logo redesign.

If a replacement is necessary, record why. “Wrong artwork supplied” and “file cannot be decoded” describe different defects. Preserve the original evidence before attaching a proposed correction.

<a id="inspect-homepage-and-asset-access-separately"></a>

## Inspect Homepage and Asset Access Separately

Googlebot needs access to the homepage and its redirect path. Googlebot-Image needs access to the favicon. [Robots rules](</articles/technical-seo-checklist-b2b-websites/>) or other restrictions must not block these requests. [Google names both crawlers](<https://developers.google.com/search/docs/appearance/favicon-in-search#guidelines>).

Use two access rows in the worksheet. One addresses discovery on the homepage. The other addresses retrieval of the referenced file. Give each row a method, [timestamp](</articles/event-time-processing-time-business-reports/>), reviewed URL, and result.

Ask the maintainer to distinguish an inspection of configured policy from [an observed crawler request](</articles/crawl-stats-serving-diagnosis-b2b/>). Both can be relevant, but they answer different questions. Label a configuration check as a configuration check.

If logs enter the review, keep identity verification with the evidence. The [Googlebot server-log guide](</articles/verify-googlebot-server-logs/>) covers that separate task. A row should identify how the requester was verified before calling a logged request Googlebot [traffic](</articles/seo-roi-measurement-b2b/>).

Keep a successful browser fetch in its own field. It demonstrates that the tested browser could obtain the file under that request's conditions. Record those conditions before using the result to discuss another requester.

Leave uncertainty explicit. “Image access not examined” calls for an inspection. “Image request denied under reviewed policy” calls for a policy owner. “Crawler retrieved asset” needs evidence supporting both the requester and the retrieved resource.

<a id="walk-through-a-fictional-missing-icon-case"></a>

## Walk Through a Fictional Missing-Icon Case

Assume Alder's editor saves a generic-icon search capture on October 27. The website maintainer reviews the homepage and file the following day. Every result in this sequence is invented.

| Item | Synthetic evidence on October 28 | Current conclusion |
| --- | --- | --- |
| Homepage declaration | Points to `/brand/alder-mark.png` | Intended file identified |
| Image inspection | PNG, 96 by 96 pixels | Reviewed properties fit the documented criteria |
| Ordinary browser fetch | Image opens | Browser retrieval recorded |
| Homepage access review | No block found in reviewed configuration | Configuration evidence recorded |
| Image access review | Applicable rule denies Googlebot-Image | Asset access defect identified |
| Observed recrawl | No verified request supplied | Unknown |
| Later search appearance | No later capture supplied | Unknown |

The image's dimensions do not explain away the access defect. The ordinary browser fetch does not resolve the requester-specific rule. The record has enough information to assign a narrow correction.

The maintainer proposes removing the unintended restriction for this public asset. [The access owner](</articles/small-team-access-review-evidence/>) reviews the intended boundary before any change. Keep unrelated private paths outside that proposal.

Suppose the owner accepts the correction and the maintainer confirms the revised configuration. Record the changed rule, revision, and confirmation date. Do not fill the recrawl row with “complete” because the configuration changed.

Now suppose a verified image request later retrieves the asset. Add that request as new evidence with its timestamp. Leave search appearance pending until the editor captures another result.

Finally, suppose a later synthetic capture displays the Alder mark. Record that observation for its query and context. The sequence now contains configuration evidence, retrieval evidence, and appearance evidence. Preserve all three rather than collapsing them into a single success checkbox.

<a id="copy-an-icon-review-worksheet"></a>

## Copy an Icon Review Worksheet

Use one record per reviewed hostname. Keep long excerpts in linked evidence files so the worksheet remains readable.

| Field | What to record |
| --- | --- |
| Hostname | Exact host under review and excluded hosts |
| Homepage | Address, [redirect destination](</articles/redirect-mapping-large-scale-migrations/>), and source revision |
| Declaration | Copied `link` relation and image reference |
| Asset URL | Complete resolved image address and hosting owner |
| Dimensions | Inspected width, height, and aspect ratio |
| Format | Decoded image format and inspection method |
| Homepage access | Configuration or request evidence, date, and reviewer |
| Asset access | Separate configuration or request evidence and date |
| Changes | Proposed correction, approver, installed revision, and confirmation |
| Recrawl evidence | Verified request record or explicit unknown |
| Observation date | Query, destination, device, language, and capture |
| Owner | Person responsible for the next unresolved question |

The dimensions field needs values, not “looks fine.” The access field needs a method, not “public.” The observation field needs a capture, not “fixed.” Write entries that another reviewer can assess without repeating the entire investigation.

Assign one coordinator to keep the record current. The coordinator does not need to perform every inspection. The editor can own the capture while the maintainer owns source and access checks.

For the fictional case, mark the asset owner and access owner separately if different people control those systems. The worksheet should reveal where a correction needs authorization. It should not imply that editing the homepage grants control over another host.

<a id="keep-the-correction-bounded"></a>

## Keep the Correction Bounded

Write [the implementation request](</articles/seo-audit-implementation-checklist/>) from the evidence: “Review the rule denying the intended public icon to the documented image crawler.” Include the exact asset and the reviewed configuration.

Avoid a broad request to remove access restrictions across the website. The example identifies one public file and one unintended restriction. It provides no reason to change private resources or unrelated crawler policy.

Before installation, confirm that the requested change still matches the current source revision. If another release changed the declaration, update the inspection record. Keep the old evidence for comparison rather than applying an obsolete correction.

After installation, confirm the agreed source change and record its revision. Then hand the observation task back to the editor. Ask for a dated result, whether it matches the request or leaves the appearance question unresolved.

Use the [technical SEO audit checklist](</articles/technical-seo-audit-checklist/>) to organize a wider website inspection when needed. Do not enlarge an icon ticket into that audit without a separate reason and assignment.

Close each task against its own evidence. The designer supplies an accepted asset. The maintainer confirms the declaration and access configuration. The editor records search appearance. Keep unresolved work attached to an owner.

Review the file Google can reach.

<a id="sources"></a>

## Sources

- [Google Search Central: Define a favicon to show in search results](<https://developers.google.com/search/docs/appearance/favicon-in-search>). Organic-search scope, declaration, supported formats, dimensions, access, and URL guidance. Checked 2026.10.28. Worksheets and synthetic inspection records are proposed editorial methods.
