Favicon checker

What is the favicon checker?

The favicon checker is a page-auditing tool that takes a page URL, retrieves the page, and examines how the site declares its favicon. You enter a URL into the form and submit it. The server fetches the page, looks for the favicon declarations in the document head, and checks whether a fallback favicon is available, so you can see both how the icon is announced and whether there is a backup the site can rely on.

A favicon is the small icon associated with a site that appears next to the page name in tabs, bookmarks, and history. Sites declare their favicon with link tags in the page head, pointing to an icon file. If those declarations fail, a fallback such as a default icon file at a standard location may still be picked up, which is why checking both the declarations and the fallback gives a complete picture.

It is a small file, but it represents the brand in some of the most repeated views on the web. Every open tab shows it, every saved bookmark carries it, and it is part of how users tell one site from another at a glance. Because it appears in so many everyday places, a broken or missing icon is visible far more often than any other single asset on the site.

The tool's value comes from the fact that the favicon situation is not guessable from looking at a page. The head markup that declares it is hidden from view, and the fallback file's existence is a separate fact entirely. Submitting the URL returns both pieces of information at once, which is the difference between wondering about the icon and knowing its state.

The check is also useful as a plain inventory. The report lists what the page declares, which means you can see not only whether an icon exists but what formats and sizes the site is offering. That inventory matters when a rebrand or a design refresh is coming, because it shows you exactly what is currently live before you plan what should replace it.

Over time, keeping the favicon setup verified becomes a small part of any launch checklist. A new site, a new domain, or a refreshed template all change the icon situation, and each of them is a moment where the icon can slip. Because the check takes seconds, it is easy to make it part of the routine rather than an occasional afterthought.

What the favicon checker detects

When you submit a URL, the tool fetches the page and reads the favicon declarations in the document head. It looks for the link tags that point to the site icon, including the different formats sites use for different purposes, and reports what it finds. This shows whether the page tells clients where the icon lives and which files it points to.

On the fallback side, the tool checks whether a default favicon file is available at the standard location a client would try if no declaration pointed anywhere useful. The presence of that fallback file matters because it gives the site a safety net: even when the declared icon is missing or misconfigured, a recognized fallback keeps a recognizable icon associated with the site.

The two checks together answer a practical question: does this site have an icon that will actually be shown? A page can declare an icon file that no longer exists, or it can skip declarations entirely and rely on the fallback, and either way the visible result differs. Reading the declarations and the fallback availability together reveals which situation applies to the URL you checked.

The two sources also complement each other in practice. Declarations cover the modern cases, where a site points clients to a dedicated icon file that fits its design and size needs. The fallback covers the simple cases, where a client looks for a default file without being told where it is. A site with both in place is covered from every angle, and a site with neither is relying on chance.

How to use the favicon checker

Checking a site's favicon setup is a quick operation that goes from a URL to a clear verdict.

1. Copy the URL of the page whose favicon setup you want to review.
2. Open the favicon checker page and paste the URL into the form field.
3. Submit the form so the server fetches the page and examines its favicon declarations.
4. Read the returned report, noting which declarations were found and whether a fallback favicon is available.
5. If the icon is missing or broken, add or correct the declarations, then re-check the URL to confirm the fix.

How to get better results

• Check the homepage or a representative page first, since favicon declarations are typically set at the template level and repeat across pages.
• Look at both halves of the report. A working declaration with no fallback is different from no declaration with a fallback, and each needs a different fix.
• If you change the icon file, re-check immediately. Renamed or moved files are the most common reason a valid-looking declaration stops working.
• Use a real icon format that the declarations point to. An empty or missing target file makes a perfectly written declaration useless.
• Test after deploying through a CDN or cache layer, since stale cached pages can serve old head markup that still references a deleted icon.
• Keep the fallback file in place. Even when modern declarations work, a standard fallback protects older clients and simpler contexts.

Why the favicon checker matters

A favicon is a small detail with a disproportionately large effect on how a site is recognized. It is the identity marker that appears in every tab and bookmark, and it is also part of how a site looks in results and saved links. A missing or broken icon makes the site look unfinished in precisely the places where users and search engines encounter it most often.

The checker matters because favicon problems are easy to miss and easy to introduce. The declarations live in the template head, so a single migration, cache purge, or file move can break the icon across the whole site without anyone noticing in normal page views. A tool that inspects the declarations and the fallback together turns that hidden breakage into a visible, checkable result.

It also matters at rebrand time. When a site changes identity, the icon is often the last asset updated or the first one forgotten, and old icons linger in caches and bookmarks for months. Running the check during a rebrand confirms the new icon is being declared and served, which is the difference between a clean transition and a stale one.

When to use the favicon checker

Favicon checks are cheap and quick, so they fit naturally at the milestones where a site's identity and infrastructure change. These are the moments worth a look.

• When a site has been redesigned or rebranded and you want to confirm the new icon is actually declared and reachable.
• When a favicon that used to appear has disappeared, and you want to check whether the declaration or the file is the problem.
• When you are auditing a site's head markup for missing or broken assets and want favicon coverage in the list.
• When you are launching a new site and want to verify the icon setup before the site is widely visited and bookmarked.

Related SEO Tools

Complete your SEO workflow with these related free tools:

• SERP checker - Get the top search engine results for a keyword.
• Indexed pages checker - Check if a domain is indexed by search engines.
• Website status checker - Check the status and availability of a website. Verify a site is online and responding before sharing or monitoring it.
• SSL checker - Check the SSL status and information of a domain. Review certificate validity, issuer, and expiry for a site.

Related SEO Guides

Learn more about this topic with our in-depth guides:

• Meta Tags Checker vs Google Search Console: Which Shows the Real Data?
• Free SSL Certificate Checker: How to Verify HTTPS
• Favicon SEO: Does Your Icon Affect Rankings?

Frequently asked questions

What exactly is a favicon declaration?

It is a link tag in the page head that tells a client where the site's icon file lives. The checker reads these declarations and reports which ones it found on the page you submit.

What is a fallback favicon?

It is a default icon file at a standard location that a client can pick up even when no working declaration points to another icon. The checker verifies whether that fallback is available for the URL.

Why do I need both a declaration and a fallback?

They cover different failure modes. A declaration tells clients exactly where the icon is, while a fallback catches the case where declarations are missing or point to a broken file. Checking both gives a complete picture of the site's icon coverage.

Will the checker display the icon itself?

Its focus is detection: finding the favicon declarations and confirming fallback availability. That tells you whether an icon is declared and reachable, which is the question most site owners need answered.

Does every site need a favicon?

Not technically, but practically it helps. A site with no icon shows a blank or default placeholder in tabs and bookmarks, and for branded sites that reads as unfinished. The checker helps you confirm the icon you intend to show is the one clients will actually load.

Can the checker tell me if my icon is the right size?

Its focus is detection: confirming that declarations exist and point to available files, and that a fallback is present. Size and design considerations are part of how well the icon displays in different contexts, but the checker's job is to verify the icon is declared and reachable.