Organization logo structured data generator

Organization markup tells Google which name, website and logo belong to your business. Google’s Organization documentation says the logo property can influence which logo appears in Search results and your knowledge panel. This Organization logo structured data generator writes that JSON-LD from a form and checks the rules Google states for it, in your browser.

What does this logo structured data generator build?#

A <script type="application/ld+json"> block with @context set to schema.org and the @type you pick: Organization, or one of six subtypes (OnlineStore, OnlineBusiness, Corporation, NGO, NewsMediaOrganization, EducationalOrganization). Google recommends the most specific subtype that matches your organization.

It then adds only the fields you fill in, all from Google’s list of recommended properties: name, alternateName, legalName, url, logo, description, sameAs as an array, email, telephone, and an address as a PostalAddress with street, city, region, postal code and country. Google lists no required properties, so no field is mandatory. The output escapes < inside values, so no text you type can close the script tag early.

How to read the notes#

• Red: must fix. A url, logo or sameAs value that is not an absolute URL.
• Amber: should fix. An empty name, url or logo; a phone number that does not start with +, since Google asks for the country code and area code; an email that does not look like one; a country that is not a two-letter ISO 3166-1 alpha-2 code.
• Grey: check yourself. A logo URL without a BMP, GIF, JPEG, PNG, WebP, SVG or AVIF extension, and a reminder of Google’s logo rules: at least 112x112px, crawlable and indexable, and legible on a white background.

Logo file check. Choose the logo image and the tool reads its width and height locally, then says whether it meets the 112x112px minimum. Both sides must reach 112px.

Worked example#

The form opens with an Organization named “Example Coffee Roasters”, an example.com website URL, a PNG logo URL on the same domain and one LinkedIn profile in sameAs. It writes:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Coffee Roasters",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example"
  ]
}

inside a script tag, with one grey note repeating the logo rules. Type 555-0100 as the telephone and an amber note asks for the country code. Choose a 100x100px logo file and the check reports it below the minimum.

Where should the markup go?#

Google recommends placing Organization markup on the home page, or on a single page that describes the organization, such as the about page; it does not need to be on every page. For a local business such as a restaurant or a physical store, Google recommends the most specific LocalBusiness subtype, with the required and recommended fields from its local business documentation, on top of the fields here. After deploying, Google suggests testing a few pages with the URL Inspection tool before relying on the result.

Common mistakes it catches#

• Relative logo paths such as /images/logo.png, which are not absolute URLs.
• Undersized logos. Favicons and small header marks often fall under 112px.
• White logos. Google warns that a mostly white or gray logo may not look as intended on a white background, so keep a dark or colored version for markup.
• Phone numbers without a country code.
• Markup on every page. Google says the home page or an about page is enough.

Related tools and reading#

• Schema markup generator for JSON-LD
• JSON-LD validator
• LocalBusiness schema checker
• WebSite leads schema.org type adoption at 12.73% of mobile pages