AboutPage & Trust Signal Schema (JSON-LD Blueprint)
Structured data for corporate About Us pages establishing company mission, founding history, leadership, and verified business registries.
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": "AboutPage",
"name": "About OmniSEO Tools",
"url": "https://omniseotools.com/about",
"description": "Learn about the mission, engineering principles, and core team behind OmniSEO Tools.",
"mainEntity": {
"@type": "Organization",
"name": "OmniSEO Technologies Inc.",
"foundingDate": "2024-01-15",
"founders": [
{
"@type": "Person",
"name": "Amr Gharz"
}
],
"knowsAbout": [
"Technical SEO",
"Next.js Architecture",
"Client-Side Performance Engineering"
]
}
}Typed Properties Specification (6 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 | Page title (e.g. About OmniSEO Tools). e.g. About OmniSEO Tools |
| url | URL | Required | Canonical URL of the About page. e.g. https://omniseotools.com/about |
| mainEntity | Organization | Person | Required | The entity that the page describes in depth. e.g. { "@type": "Organization", ... } |
| description | Text | Recommended | Summary of page contents and company charter. e.g. Learn about the mission and engineering team... |
| inLanguage | Text | Recommended | Language code for page copy. e.g. en-US |
| publisher | Organization | Recommended | Parent publishing company. e.g. { "@type": "Organization", "name": "OmniSEO Tools" } |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying AboutPage schema.
Missing mainEntity Connection
Emitting an empty AboutPage node without connecting it to the primary Organization node.
Always supply mainEntity linking to your Organization @id.
Generic Page Name ('Page 1')
Failing to declare an explicit, descriptive page name.
Set name to 'About [Brand Name]'.
Omitting Leadership / Founder Entities
Lacking named founders weakens E-E-A-T algorithmic verification.
Nest founders and executive team inside the Organization mainEntity.
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