Favicon: a beginner's guide
Find all favicon and icon URLs
Favicons: the tiny icon that shows up in every browser tab and search result
A favicon (short for favorite icon) is the small image that appears in the browser tab next to a page's title, in bookmark lists, in browser history, and — increasingly — in Google's mobile search results next to your site name. It is one of the smallest pieces of design on the entire web, and one of the easiest to overlook, but it is also one of the few brand elements that follows a user across every place your site appears. A missing or broken favicon shows as a generic globe icon or an empty box, which looks unprofessional in a way most people can't quite articulate but immediately notice.
You should care because favicons are now part of how Google represents your site in mobile search results. Since 2019, Google has shown the favicon next to the site name on mobile organic results, which means a missing or broken favicon costs you a small but real amount of brand recognition on every search result you appear in. Multiplied across thousands of impressions per month, that adds up to a measurable click-through rate difference. This is the kind of detail that distinguishes a well-tended website from a neglected one.
The five things every favicon audit looks at:
Does a favicon file exist at the standard location? Browsers fall back to looking at `/favicon.ico` if the HTML does not specify one explicitly.
Is it referenced in the HTML `<head>`? The proper way is `<link rel="icon" href="...">`, which lets you specify a path and format.
Are multiple sizes provided? Modern best practice is to provide several sizes (16x16, 32x32, 192x192, 512x512) so browsers and operating systems can pick the best fit for each context. iOS and Android both expect higher-resolution icons for home-screen pinning.
Is the file format reasonable? Standard formats are ICO (legacy), PNG (modern), and SVG (scalable). PNG and SVG are recommended in 2025.
Does it match the brand? A favicon should be recognizable at 16 pixels across — usually a single letter, a logomark, or a heavily simplified version of the full logo.
Three questions a favicon audit answers:
Does my site have a favicon at all, and is it loading correctly across browsers?
Are all the modern sizes and formats present, including the high-resolution icons iOS and Android need?
Does my favicon look professional in the contexts where it actually appears (browser tabs, Google mobile search, bookmark lists)?
The cost of ignoring your favicon is the death-by-a-thousand-cuts of looking slightly less professional than every competitor that bothered to set theirs up. The cost of fixing it is one design ticket and one engineering ticket. This is a 30-minute investment with a tiny but permanent payoff in brand consistency.
The Favicon endpoint, in plain language
In one sentence: Find all favicon and icon URLs
Discovers all favicon and icon files for a domain including traditional favicons, Apple touch icons, and modern manifest icons in various sizes.
Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.
What is actually happening when you call it
Here's what's actually happening behind the scenes when you call this endpoint:
Analyzes the HTML (HyperText Markup Language) head section for link tags pointing to icons, checks common favicon locations (/favicon.ico, /apple-touch-icon.png), parses web app manifests for icon definitions, and validates that discovered icons are accessible.
If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.
Why this specific tool matters
Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the Favicon tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.
Favicons are useful for brand identification, UI enhancement (displaying site icons in applications), and can sometimes reveal technology platforms through default icons.
Picture this in real life. Imagine a designer. Here's the situation they're walking into: Collect all icon variations for a brand to ensure consistency across platforms. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the Favicon tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.
Three questions this tool answers in plain English. If any of these have ever crossed your mind, the Favicon tool is built for you:
Are search engines actually able to crawl, understand, and recommend my pages?
What is the single biggest fix I could make today to climb in Google?
How does my site compare against the technical SEO checklist that the top results all pass?
You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.
Who gets the most out of this. Marketers, content writers, freelancers running client sites, founders trying to grow without paying for ads, and SEO specialists running monthly health checks. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.
What happens if you skip this entirely. Skip it and search engines quietly stop sending you traffic and you don't find out until the next quarterly review. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.
Available on the developer plan. The technical details: `GET /v1/domain/favicon`.
When would I actually use this?
If you're still on the fence about whether the Favicon tool belongs in your toolbox, this section is for you. Below you'll meet three real people — a designer, a frontend developer, and a security researcher — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.
Story 1: Brand Asset Collection
Imagine you're a designer. Collect all icon variations for a brand to ensure consistency across platforms.
Why it matters: Audit and standardize favicon implementations across properties.
Story 2: UI Enhancement
Imagine you're a frontend developer. Dynamically display favicons next to links in a bookmark manager or aggregator app.
Why it matters: Improve UI with visual brand identification for external links.
Story 3: Technology Fingerprinting
Imagine you're a security researcher. Identify default CMS (Content Management System) or platform favicons that reveal the underlying technology.
Why it matters: Discover technology platforms through favicon analysis.
Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the Favicon tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:
Before launching a new page, site, or campaign — to catch the dumb mistakes.
During a quarterly SEO health check.
When organic traffic suddenly drops and you need to find out why.
When pitching a new client and you need an audit deck in under an hour.
If you can see yourself in even one of those bullets, the Favicon tool will pay for itself the first time you use it.
Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the Favicon tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.
The easiest way: just ask your AI assistant
If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:
"Use the Favicon tool to check github.com and explain anything that looks wrong in plain language."
The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.
MCP (Model Context Protocol) access is free on every plan, including the free tier. One API key works for both REST and AI — you do not have to choose.
The technical way: call it from code
If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.
# Replace edns_live_YOUR_KEY with your real API key from the dashboard
curl -H "Authorization: Bearer edns_live_YOUR_KEY" \
"https://api.edgedns.dev/v1/domain/favicon?domain=github.com"What you need to provide
There's just one piece of information you need to provide. The table below explains exactly what it is and what a real value looks like.
| Field | Type | Required? | What it means | Example |
|---|---|---|---|---|
domain | string | Yes | The domain to find favicons for | github.com |
What you get back
When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.
| Field | Type | What you'll see in it |
|---|---|---|
domain | string | The queried domain |
icons | array | All discovered icons with URL (web address), type, and size |
primaryFavicon | string | Best available favicon URL (web address) |
count | number | Total number of unique icons discovered |
score | number | Favicon health score (0-100) |
grade | string | Letter grade (A-F) based on score |
recommendations | array | Suggestions to improve favicon coverage |
Words you might be wondering about
If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.
CMS (Content Management System) — Software that lets non-technical people publish web pages without writing code. WordPress, Webflow, and Ghost are popular examples.
HTML (HyperText Markup Language) — The basic language web pages are written in. The tags you see in the source code (<h1>, <p>, <a>) are HTML.
Need Programmatic Access?
Automate domain intelligence with 100+ API endpoints and a free MCP server for AI integration.