What it does
Organization schema is the structured-data type for any organization — companies, nonprofits, schools, government agencies. It tells Google about your name, logo, social profiles, contact methods, and basic operational facts. Unlike LocalBusiness, Organization schema is for entities that may not have a physical storefront — remote-first SaaS, online brands, distributed teams.
The output is the schema you typically place on your homepage (or globally in your site layout). It feeds the entity Google builds for your brand across the web — the foundation for the knowledge panel that appears when people search your brand name directly.
Why Organization schema is foundational
Organization schema does three things that compound over time:
- Brand entity recognition. Google builds an entity for your brand by aggregating signals across the web. Organization schema with a complete sameAs array (every social profile, every directory listing) gives Google a single canonical source to anchor that entity.
- Knowledge panel eligibility. The branded knowledge panel that appears for established brand searches requires Organization-level signals. Schema is the entry point.
- SiteLinks Search Box. The internal search box that appears under your top-listed result for branded queries is unlocked by Organization + WebSite schema with a potentialAction property.
How to use this generator
- Pick the right type. Most companies use
OrganizationorCorporation. Educational institutions, nonprofits, and government organizations have their own subtypes. - Fill the basics. Name, description, URL, and logo URL are the foundation. Logo specifically is required by Google for knowledge panel logo display.
- Add sameAs aggressively. Every legitimate external profile should be listed: Twitter/X, LinkedIn, Facebook, Instagram, YouTube, Crunchbase, Wikipedia, Wikidata. The longer this list, the stronger your entity signal.
- Include foundingDate and numberOfEmployees if comfortable disclosing. These build entity completeness.
- Add contactPoint if you have a public customer-facing phone number or contact channel. Multiple ContactPoints (one per type — sales, support, billing) are allowed; this tool supports one for simplicity.
- Place the output globally. Organization schema is best placed in your site's layout (so every page emits it), or at minimum on the homepage. Different pages should not have different Organization schemas.
Organization schema best practices
- One canonical Organization per brand. Use consistent name, logo URL, and sameAs across every page. Different schemas on different pages confuse the entity- building process.
- Logo URL must be a fully-qualified absolute URL. Relative paths fail validation. Should point to a square or wide logo on a transparent or solid background, at least 112×112px.
- Aggressive sameAs. Twitter, LinkedIn, Facebook, YouTube, Instagram, Crunchbase, Wikipedia, Wikidata, GitHub if applicable, your Trustpilot/G2 profiles if you have them, your Google Business Profile URL. The more verifiable signals, the better.
- Use legalName when different from brand name. "Ankivo" might be your brand; "Ankivo, Inc." is the registered legal entity. Both fields help Google build the entity correctly.
- Don't inflate numberOfEmployees. Public-facing data Google can verify against LinkedIn, Crunchbase, etc. Inflated numbers are detected and reduce trust signal.
- Pair with WebSite schema. Adding a companion WebSite schema with a potentialAction unlocks the SiteLinks Search Box in branded SERP results.
Frequently asked questions
What's the difference between Organization and LocalBusiness schema?
Organization is the parent type for any organization. LocalBusiness is a subtype for businesses with a physical storefront and local-search audience. If you have a physical location customers visit, use LocalBusiness. If you're a remote-first SaaS, online brand, or distributed team, use Organization.
Where should Organization schema go on my site?
Best place: your site's global layout (so every page emits it). At minimum, the homepage. Don't put different Organization schemas on different pages — that confuses the entity-building process. One canonical Organization per brand.
What's sameAs and why does it matter?
sameAs is a list of URLs that point to other authoritative profiles of the same entity — your Twitter, LinkedIn, Facebook, Crunchbase, Wikipedia. Google uses sameAs to confirm that all these profiles describe the same organization, strengthening your brand entity signal. The more legitimate sameAs entries, the better.
Will Organization schema get me a knowledge panel?
Schema is necessary but not sufficient. Knowledge panels also require: brand notability (people search your brand name directly), Wikipedia/Wikidata mentions, consistent sameAs across the web, and an established history. Schema is your entry signal — the rest builds over time.
Should I include legalName?
Yes if it differs from your brand name. 'Ankivo' might be the brand; 'Ankivo, Inc.' is the registered legal entity. Both help Google distinguish brand identity from legal entity for compliance and entity-building purposes.
Can I have multiple ContactPoints?
Yes — schema.org allows multiple ContactPoint entries, one per type (sales, support, billing, etc.). This tool supports one for simplicity. To add more, edit the JSON output manually before pasting.
Will this tool log my data?
No. Everything runs in your browser. The fields you fill never leave your device — there is no server endpoint and nothing to log.