ZeroUtil

Organization Schema Generator (JSON-LD)

Generate Organization JSON-LD schema with logo, contactPoint and sameAs for knowledge panel signals.

Maintained by

Organization Schema Generator (JSON-LD)

The Organization schema generator builds JSON-LD describing the company, brand, or publication behind a website. Paste it into your homepage or About page <head> and you give Google a clean set of signals for knowledge-panel eligibility, brand-name disambiguation, and entity linking across the open graph. The generator runs locally in your browser and emits a pasteable <script type="application/ld+json"> block.

What Organization Schema Unlocks

Three concrete SERP features rely on Organization markup:

  • Knowledge panel - the branded sidebar card that appears for navigational queries ("Acme Corporation"). Organization schema does not guarantee a panel, but without it Google has to guess your brand identity from unstructured signals.
  • Logo in branded SERP results - the logo field, combined with a verified homepage, lets Google display your logo next to search results for your domain.
  • Entity linking - the sameAs array tells Google which social profiles, Wikipedia/Wikidata entries, and Crunchbase pages refer to the same organisation. Cleans up duplicate-entity confusion when your brand name overlaps with another company.

Required and Recommended Fields

  • name (required) - the canonical brand name. Use the form that appears on your homepage header, not the legal entity name unless they match.
  • url (required) - absolute HTTPS URL of your homepage. Matches the <link rel="canonical"> of the same page.
  • logo (recommended) - an ImageObject or plain URL to a logo image. Google's guidance: at least 112x112, on a solid background, PNG or JPG (SVG not always parsed). For the best render in the SERP, supply a 600x60 landscape variant plus a 512x512 square.
  • sameAs (recommended) - array of URLs to official profiles: LinkedIn company page, Twitter/X handle, Facebook page, YouTube channel, Wikipedia article, Wikidata entry. Omit aspirational or inactive profiles; Google cross-checks active engagement.
  • contactPoint (optional) - structured contact info with telephone, email, contactType. Useful for customer service discoverability.
  • address (optional) - a PostalAddress if you have a public-facing location. Companies that are also physical businesses usually use LocalBusiness (a subtype of Organization) instead.

LocalBusiness vs. Organization

If your entity has a physical storefront, office, or service area and you want to appear in Google Maps and the Map Pack, use LocalBusiness schema from the generic generator instead of Organization. LocalBusiness is a subtype of Organization with additional fields (openingHoursSpecification, geo, servesCuisine for restaurants, and so on). Organization is the right choice for SaaS companies, digital publications, online-only brands, and anyone without a customer-facing physical location.

Common Validation Errors

  • Logo too small or low contrast - under 112x112 pixels, transparent background with a dark foreground, or a logo that fills its canvas edge-to-edge. Google may reject the logo for SERP rendering while still accepting the structured data as valid.
  • sameAs pointing to personal profiles - Google expects official company or publication profiles, not a founder's personal Twitter. Mixing the two confuses entity linking.
  • Missing url - an Organization without a canonical URL is hard for Google to link to a domain. Always include it.
  • Multiple Organization blocks on the same page - valid if they describe distinct entities (parent company + subsidiary) but generally a mistake. Most sites should have exactly one Organization entity referenced across all pages via @id.
  • Trailing slashes drift - sameAs: ["https://twitter.com/acme/"] versus "https://twitter.com/acme". Pick one and stick with it, or use the canonical URL of the linked page.

Difference From the Generic Generator

The generic Schema Markup Generator exposes eight schema types through a picker. This page lands with Organization pre-selected and adds Organization-specific guidance (knowledge panel signals, logo sizing, sameAs rules) that would be off-topic on the generic page. For Article, Product, or FAQPage schema, switch type or jump to the dedicated sub-page.

Verifying With Rich Results Test

Paste the generated block into Google's Rich Results Test to confirm parse correctness. Organization does not currently unlock a visual rich-result badge the way Product does, so the test reports "Page is valid" without highlighting Organization specifically. Then paste into <head> and monitor Search Console for structured data issues over the following week.

Frequently Asked Questions

Will Organization schema guarantee a knowledge panel?

No. Knowledge panels require Google to recognise your entity as notable enough to surface, which depends on mentions across the web, Wikipedia or Wikidata coverage, search volume, and brand authority. Organization schema improves your odds because it disambiguates your entity and links your profiles, but it is necessary not sufficient. Small brands with strong topical authority and active sameAs profiles sometimes earn a panel; others do not despite perfect markup.

Should every page have the Organization block, or just the homepage?

Best practice is every page, using <code>@id</code> to reference the same entity so Google treats it as one Organization, not many. Add the block to your homepage and template-render it into every page via the site header or footer. Each page's Organization block should carry the same <code>@id</code> (typically your domain URL or a #organization fragment of it) so Google deduplicates correctly.

Is Organization schema different from Person schema for a solo creator?

Yes. Organization describes an entity - a company, publication, or brand. Person describes an individual human. If you run a personal blog under your real name, Person is more accurate. If you run a one-person consultancy under a brand name, use Organization for the brand and Person for yourself (you can reference Person inside Organization via <code>founder</code>). Google supports both and treats them differently for knowledge-panel eligibility.

What should I put in sameAs?

Active, official profiles only. Your LinkedIn company page, your Twitter/X handle, your Facebook page if you use it, your YouTube channel, your Wikipedia article (if one exists), your Wikidata Q-number URL, your Crunchbase profile for startups. Skip abandoned accounts, personal profiles (those go in a Person entity), and aspirational links (a Wikipedia URL that returns a 404 hurts more than it helps). Three to six strong profiles beat a dozen weak ones.

What size and format should the logo be?

Google's documented guidance: at least 112x112 pixels, PNG or JPG with a white or solid background, on the same domain as the website (cross-origin logos from CDNs work but are riskier). For best SERP rendering, provide a square version for the knowledge panel and a landscape or wide version for in-result brand display. SVG logos parse correctly in the JSON-LD but may not render reliably in every Google feature - supply a raster fallback.

Can I include contact information without exposing it on the page?

No. Google's structured data policies require the markup to reflect information accessible on the page. If you emit <code>contactPoint</code> with a phone number, that number should be visible somewhere users can find it (a contact page, footer, or About page). Hidden contact data in schema alone is a policy violation that can trigger a manual action.

Does this tool store my organisation name or logo URL?

No. The generator runs entirely in your browser with pure JavaScript. Your organisation name, URL, logo URL, and social profiles are only in the browser tab and are discarded when you close it. There is no outbound request, no analytics beacon per keystroke, and no telemetry. Open the Network tab in DevTools to confirm.

More SEO & Web Tools

Meta Tag Generator

Generate complete HTML meta tags including Open Graph and Twitter Card tags.

Open tool

Open Graph Preview

Preview how your page looks when shared on Facebook and LinkedIn.

Open tool

Robots.txt Generator

Generate robots.txt files with user-agent rules, allow/disallow paths and sitemap.

Open tool

XML Sitemap Generator

Generate valid XML sitemaps from a list of URLs with changefreq and priority.

Open tool

Keyword Density Checker

Analyze word frequency with single words, bigrams and trigrams with density percentages.

Open tool

Google SERP Preview

Preview how your page appears in Google search results with character count indicators.

Open tool