Organisation Structured Data: Complete Implementation Guide
Organisation structured data helps search engines understand key information about your company or entity. By adding Organisation schema markup to your website, you can influence what appears in Google's knowledge panel — including your logo, official social media profiles, contact details, and founding information. This is one of the most impactful schema types for brand visibility and trust.
Why Use Organization Schema?
- Trigger a branded knowledge panel in Google search results displaying your logo, description, and key details.
- Ensure your official social media profiles are correctly linked and displayed alongside your brand in search.
- Provide search engines with authoritative contact information, improving trust signals for your organisation.
- Help Google disambiguate your brand from similarly named entities, reducing misattribution in search results.
- Strengthen your overall entity profile in Google's Knowledge Graph, benefiting all pages across your domain.
Required Properties
These properties are required by Google for Organization structured data to be eligible for rich results.
| Property | Description |
|---|---|
| @type | Must be set to "Organization" (or a more specific sub-type such as "Corporation" or "LocalBusiness"). |
| name | The official registered name of the organisation as it should appear in search results. |
| url | The canonical URL of the organisation's official website, used to associate the entity with the domain. |
Recommended Properties
Adding these properties improves your chances of appearing in rich results and provides more context to search engines.
| Property | Description |
|---|---|
| logo | A URL pointing to a high-resolution logo image. Google recommends at least 112x112 pixels in a square format. |
| sameAs | An array of URLs for official social media profiles and authoritative external references (e.g. Wikipedia, LinkedIn, Twitter/X). |
| contactPoint | A ContactPoint object specifying customer service telephone numbers, email addresses, and the type of contact (e.g. customer support, sales). |
| description | A concise description of the organisation, typically one to two sentences summarising its purpose and activities. |
| foundingDate | The date the organisation was founded, in ISO 8601 format (e.g. "2015-03-20"). |
JSON-LD Example
Here is a complete Organization structured data example you can use as a starting point. Or use our Organization generator to create one automatically.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Schemai",
"url": "https://schemai.com",
"logo": "https://schemai.com/images/logo.png",
"description": "Schemai provides tools and guides for implementing structured data markup to improve search engine visibility.",
"foundingDate": "2024-01-15",
"sameAs": [
"https://twitter.com/schemai",
"https://www.linkedin.com/company/schemai",
"https://github.com/schemai"
],
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer support",
"email": "[email protected]",
"availableLanguage": [
"English"
]
},
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Schema Lane",
"addressLocality": "London",
"addressRegion": "England",
"postalCode": "EC1A 1BB",
"addressCountry": "GB"
}
}
</script>How to Implement Organization Schema
- 1Gather your organisation's official details: registered name, website URL, logo, social profile URLs, and contact information.
- 2Create the JSON-LD script block with "@context": "https://schema.org" and "@type": "Organization" as the foundation.
- 3Add the required properties — name and url — ensuring the URL matches your canonical domain exactly.
- 4Include recommended properties such as logo, sameAs (with all official social profiles), contactPoint, and description.
- 5Place the JSON-LD script tag in the <head> section of your homepage. Organisation markup is typically only needed on the homepage or an about page.
- 6Validate your markup using Google's Rich Results Test or the Schema Markup Validator, then monitor the Knowledge Panel in Google Search Console.
Common Mistakes to Avoid
- Using an unofficial or outdated logo URL that returns a 404, which prevents Google from displaying your brand image.
- Including social media URLs in sameAs that belong to unofficial fan pages or accounts not controlled by your organisation.
- Placing Organisation markup on every page of the site instead of limiting it to the homepage or about page, which can dilute signals.
- Omitting the url property or using a URL that does not match the canonical domain, breaking the association between entity and website.
- Setting the @type to a generic "Thing" instead of "Organization" or a more specific sub-type, reducing the markup's usefulness.
Testing & Validation
Before deploying your Organization structured data, validate it using these tools:
- 1Google Rich Results Test — Paste your page URL or code snippet to check if your structured data is eligible for rich results.
- 2Schema Markup Validator — Validates your JSON-LD syntax against the schema.org specification.
- 3Google Search Console — After deployment, monitor the Enhancements report for any errors or warnings.
Frequently Asked Questions
Should I use Organisation markup on every page of my website?
No. Google recommends placing Organisation structured data on your homepage or a dedicated about page. Adding it to every page is unnecessary and can create redundant signals. Use other schema types (such as Article or Product) on individual content pages.
What is the difference between Organization and LocalBusiness schema?
LocalBusiness is a more specific sub-type of Organization intended for businesses with a physical location that serves customers in person. If your business has a shopfront, office, or service area, LocalBusiness is typically the better choice as it supports additional properties like openingHours and geo coordinates.
How long does it take for a knowledge panel to appear?
There is no guaranteed timeline. Google must first crawl and process your structured data, then determine that a knowledge panel is appropriate. This can take anywhere from a few weeks to several months, and not all organisations will receive a panel. Having consistent information across your website and third-party sources significantly helps.
Can I include multiple contact points?
Yes. The contactPoint property accepts an array, so you can specify separate entries for customer support, sales, technical support, and other departments. Each ContactPoint can have its own telephone number, email, and available languages.
Do I need to include sameAs for every social media platform?
You should include sameAs URLs for all official profiles your organisation actively maintains. There is no need to list platforms where you do not have an official presence. Prioritise well-known platforms like LinkedIn, Twitter/X, Facebook, and any relevant industry-specific directories or Wikipedia entries.
Ready to Generate Your Organization Schema?
Use our free generator to create valid Organization structured data in seconds.
Open Organization Generator