Person & Author E-E-A-T Schema (JSON-LD Blueprint)
Detailed entity structured data for authors, researchers, executives, and specialists to reinforce Experience, Expertise, Authoritativeness, and Trust (E-E-A-T).
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": "Person",
"@id": "https://omniseotools.com/about#amr-gharz",
"name": "Amr Gharz",
"jobTitle": "Lead Search Engine Architect",
"worksFor": {
"@type": "Organization",
"name": "OmniSEO Tools",
"url": "https://omniseotools.com"
},
"alumniOf": {
"@type": "EducationalOrganization",
"name": "University of London"
},
"knowsAbout": [
"Technical SEO",
"Next.js App Router Architecture",
"Core Web Vitals Optimization",
"Schema.org JSON-LD Infrastructure",
"Client-Side Performance Engineering"
],
"sameAs": [
"https://twitter.com/amrgharz",
"https://github.com/amrgharz",
"https://www.linkedin.com/in/amrgharz"
],
"image": "https://omniseotools.com/images/authors/amr-gharz.jpg",
"description": "Specialist in high-scale programmatic SEO, crawler budget optimization, and web performance engineering."
}Typed Properties Specification (7 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 | Full legal or professional pen name. e.g. Amr Gharz |
| jobTitle | Text | Required | Professional executive or technical role. e.g. Lead Search Engine Architect |
| worksFor | Organization | Required | Primary employer or consulting agency. e.g. { "@type": "Organization", "name": "..." } |
| knowsAbout | Array<Text> | Required | Explicit list of verified technical competencies for E-E-A-T topical authority. e.g. ["Technical SEO", "Next.js Architecture"] |
| sameAs | Array<URL> | Required | Verified social profiles, GitHub, ORCID, and personal website. e.g. ["https://twitter.com/...", ...] |
| alumniOf | EducationalOrganization | Recommended | University or academic institution. e.g. { "@type": "EducationalOrganization", "name": "..." } |
| image | URL | Recommended | Professional headshot photo. e.g. https://.../headshot.jpg |
Google Search Console Pitfalls & Critical Warnings
Avoid these 3 common validation traps, parser errors, and algorithmic policy penalties when deploying Person schema.
Generic or Missing sameAs Social Profiles
Without verified external social and academic profile links, Google cannot verify real-world author identity.
Always supply active Twitter, LinkedIn, GitHub, Google Scholar, or Wikidata links.
Vague knowsAbout Values ('Stuff', 'Tech')
Using broad or informal skill strings rather than precise industry topics.
Use specific industry taxonomy terms like 'Next.js App Router Architecture'.
Conflicting worksFor Organization Data
Mismatches between the employer listed in Person schema and the actual publisher Organization node.
Link worksFor directly to the canonical Organization @id.
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