How to Get Your Logo Into Google Search Results

To get your logo into Google Search results, add Organization structured data with a logo property to your home page (or your About page), pointing to a crawlable image at least 112×112 pixels. That tells Google which logo to use in places like knowledge panels. The small icon next to your site name in search results is a different thing: that's your favicon, and it's set with a <link rel="icon"> tag, not structured data.

Which "logo" in Google are you trying to change?

People say "logo" for two different images, and mixing them up wastes a lot of time. Here's how they differ:

If the little round icon beside your search results is wrong or missing, you want our guide on why a favicon isn't showing in Google. You can also run your domain through the Google favicon checker to see what Google currently has. The rest of this post is about the Organization logo.

If you're still sorting out which asset is which on your own site, favicon vs app icon vs logo lays out the whole set.

What does Google require for the logo property?

Google's Organization structured data docs list these rules for logo:

• At least 112×112 pixels. That's the minimum. Going bigger is fine and usually smarter, since Google may show it at different sizes.
• Crawlable and indexable. Googlebot has to be able to fetch the image. Don't block it in robots.txt, and don't serve it with a noindex header.
• A format Google Images supports. Google lists BMP, GIF, JPEG, PNG, WebP, SVG, and AVIF.
• Looks right on a white background. Google says to make sure the image looks the way you intend on pure white. A white logo on a transparent background will vanish.

You can give logo as a plain URL or as an ImageObject with a url or contentUrl. Both are valid. The plain URL is simpler and harder to get wrong.

A few practical picks: a PNG at 512×512 or so is a safe default. Keep some padding around the mark so it doesn't touch the edges. If your full wordmark is very wide, consider whether the symbol alone reads better at small sizes. For more on how Google handles images in general, see our post on image SEO for Google Images.

What does the JSON-LD look like?

JSON-LD is a way to add structured data as a block of JSON inside a <script> tag. It's the format Google recommends. Here's a minimal example you can adapt:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Co",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo-512.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-co",
    "https://x.com/exampleco"
  ]
}
</script>

A few notes on the fields:

• url is your site's home page. Use the same version (HTTPS, www or not) that your canonical tags use.
• logo should be an absolute URL. A relative path is asking for trouble.
• sameAs is optional. It lists your official profiles elsewhere, which helps Google connect the dots about who you are.

Google says Organization markup has no required properties, so add what's true and relevant. Other useful ones include description, address, and contactPoint. If you're a local shop, look at the more specific LocalBusiness types, which are subtypes of Organization.

If you'd rather use the ImageObject form, it looks like this:

"logo": {
  "@type": "ImageObject",
  "url": "https://www.example.com/images/logo-512.png",
  "width": 512,
  "height": 512
}

Where should you put Organization markup?

Google suggests the home page, or a single page that describes your organization, like your About page. You don't need to repeat it on every page. Plenty of sites do add it sitewide through a CMS template, and that's not harmful, but it isn't required.

Put the <script> block in the <head> or the <body>. Both work. What matters is that it's in the HTML Google renders. If a plugin or tag manager injects it, confirm with the testing tools below that Google actually sees it.

One thing to avoid: two different Organization blocks on the same page with conflicting logos. SEO plugins and themes love to add their own. View your page source and search for "Organization" to make sure there's only one, or that they agree.

How do you test your logo markup?

1. Publish the markup on your home page.
2. Open the logo URL in a private window. Confirm it loads with a 200 status and an image Content-Type.
3. Paste your home page URL into Google's Rich Results Test. It shows whether Google can read the Organization markup and flags errors and warnings.
4. Check the rendered HTML in the test to confirm your <script> block is really there.
5. In Search Console, use URL Inspection on the home page and request indexing so Google picks up the change sooner.

The Rich Results Test tells you whether your markup is valid. It won't tell you whether or when Google will use it.

How long does it take for your logo to show up?

There's no fixed timeline. Google has to recrawl the page, process the markup, and then decide whether to use it. For favicons, Google's docs say to allow several days to several weeks after a change, and it's reasonable to expect a similar range for logo updates. Some sites wait longer.

And it's not guaranteed. Google's structured data docs say plainly that it doesn't guarantee features that use structured data will show up. Knowledge panels in particular depend on much more than your markup, including whether Google has enough information about your organization at all. Good markup makes you eligible. It doesn't flip a switch.

If Google already shows your brand in a knowledge panel and the logo there is wrong, updated markup is still the right first step. Some organizations can also claim their knowledge panel and suggest changes, but that's a separate process.

Common mistakes

• Expecting structured data to change the search result icon. That's the favicon, and it has its own rules. See our favicon sizes guide for what to ship.
• Using a tiny logo. A 64×64 file is below the 112×112 minimum.
• White or light logo on transparency. On a white background it disappears.
• Blocking the image. A robots.txt rule on /wp-content/ or /assets/ can hide your logo from Googlebot.
• Conflicting markup from a theme and an SEO plugin, each with a different logo URL.
• Reusing your social share image. A wide 1200×630 banner is built for link previews, not a logo slot. Keep them separate; our Open Graph image size post covers the share image.

Don't have a clean square version of your logo yet? The favicon generator turns an image or a few letters into a square icon set you can use for both your favicon and your logo markup.

TL;DR

Add Organization JSON-LD with a logo URL to your home page, using a crawlable image at least 112×112 pixels that looks right on white. Test it in the Rich Results Test and request indexing in Search Console. It can take weeks, and Google doesn't promise to show it. If you meant the small icon next to your search results, that's your favicon, not your logo.

Sources

• Google Search Central: Organization structured data
• Google Search Central: Define a favicon to show in search results
• Google Search Central: Image SEO best practices
• Google Rich Results Test