Organization & Corporate Profile Schema Markup (JSON-LD)
Defines primary corporate identity, official logo, social profiles, contact points, and executive leadership for Google Knowledge Graph and brand entity disambiguation.
Displayed below main page header or above the tool container. • Zero CLS Container
Production JSON-LD Code Block
Embed this structured data block directly into your HTML <head> or framework layout template.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://omniseotools.com/#organization",
"name": "OmniSEO Technologies Inc.",
"legalName": "OmniSEO Technologies Incorporated",
"url": "https://omniseotools.com",
"logo": "https://omniseotools.com/images/logo.png",
"description": "Provider of client-side SEO diagnostic tools, metadata generators, and structured data analyzers.",
"foundingDate": "2024-01-15",
"founders": [
{
"@type": "Person",
"name": "Amr Gharz"
}
],
"contactPoint": [
{
"@type": "ContactPoint",
"telephone": "+1-800-555-0199",
"contactType": "customer support",
"email": "support@omniseotools.com",
"areaServed": "Worldwide",
"availableLanguage": [
"English",
"Arabic"
]
}
],
"sameAs": [
"https://twitter.com/omniseotools",
"https://github.com/omniseotools",
"https://www.linkedin.com/company/omniseotools"
]
}Typed Properties Specification (8 Fields)
Key Schema.org properties and sub-objects required to qualify for rich snippet treatment in Google Search.
| Property | Expected Type | Status | Description & Example |
|---|---|---|---|
| name | Text | Required | The official public name of the organization. e.g. OmniSEO Technologies Inc. |
| url | URL | Required | Canonical website URL of the organization. e.g. https://omniseotools.com |
| logo | URL / ImageObject | Required | Direct URL to the company logo image (SVG or PNG). e.g. https://omniseotools.com/images/logo.png |
| sameAs | Array<URL> | Required | Array of official verified social media profile URLs and Wikipedia/Wikidata entries. e.g. ["https://twitter.com/omniseotools"] |
| contactPoint | ContactPoint | Recommended | Dedicated customer support, sales, or press contact points with phone/email. e.g. { "@type": "ContactPoint", "telephone": "+1-800-555-0199" } |
| legalName | Text | Recommended | Official registered legal entity name. e.g. OmniSEO Technologies Incorporated |
| founders | Array<Person> | Recommended | List of corporate founders establishing E-E-A-T entity graph connections. e.g. [{ "@type": "Person", "name": "Amr Gharz" }] |
| foundingDate | Date (ISO 8601) | Recommended | Date the organization was incorporated. e.g. 2024-01-15 |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying Organization schema.
Relative Logo URLs Cause GSC Parser Rejections
Providing a relative path like '/logo.png' instead of an absolute HTTPS URL prevents Google from verifying the image asset.
Always supply a fully qualified absolute URL with HTTPS protocol.
Missing sameAs Social Links Weakens Entity Disambiguation
Omitting verified sameAs social profiles leaves Google uncertain about entity ownership across Google Knowledge Graph.
Include verified links to Twitter, LinkedIn, GitHub, Crunchbase, and Wikipedia.
Duplicate Organization Nodes on Every Page
Defining disparate, conflicting Organization nodes on individual pages without shared @id references fragments the site's Knowledge Graph.
Use a global static @id (e.g. 'https://domain.com/#organization') and reference it across all pages.
Recommended Implementation Scenarios
Related Schema Blueprints
Explore complementary structured data blueprints across the Organization & Identity cluster.
Displayed below main page header or above the tool container. • Zero CLS Container