How to Add Organization & Person Schema for E-E-A-T

E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) is Google's framework for evaluating content quality. Organization and Person schema are the machine-readable signals that declare who you are and what credentials you have. Without them, Google and AI engines have to guess your identity from on-page content. With them, your entity is explicitly defined, linked to authoritative profiles, and verifiable across the knowledge graph. This guide walks through implementing both.

Step 1: Add Organization schema to your homepage

Create a JSON-LD block on your homepage with @type Organization:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "@id": "https://example.com/#organization",
  "name": "Izajul Haque",
  "url": "https://example.com",
  "description": "Independent digital marketing consultant specializing in SEO, AEO, and GEO consulting.",
  "logo": {
    "@type": "ImageObject",
    "url": "https://example.com/logo.png",
    "width": 512,
    "height": 512
  },
  "sameAs": [
    "https://www.linkedin.com/in/izajulhaque",
    "https://twitter.com/izajulhaque",
    "https://www.youtube.com/@izajulhaque",
    "https://www.crunchbase.com/person/izajul-haque"
  ]
}

The @id property creates a persistent identifier that other schema (like Article publisher) can reference. Use the pattern https://yourdomain.com/#organization.

Step 2: Include sameAs links to authoritative profiles

The sameAs array is the most important E-E-A-T property. It tells search engines and AI models: "The entity described here is the same entity as the one on these other platforms." Add links to:

• LinkedIn — professional identity and work history
• Wikipedia — if you have a page (only if it exists; do not create one just for schema)
• Crunchbase — company and funding data
• Twitter/X — social presence
• YouTube — video content presence
• Google Scholar — for academic authors
• GitHub — for technical authors

Only include profiles that actually exist and are authoritative. Do not link to empty or placeholder profiles. See what is GEO for why entity clarity matters for AI visibility.

Step 3: Add a logo with correct ImageObject structure

Google requires the logo to be an ImageObject with url, width, and height:

"logo": {
  "@type": "ImageObject",
  "url": "https://example.com/logo.png",
  "width": 512,
  "height": 512
}

Requirements:

• Square image, at least 112x112 pixels (Google recommends 512x512)
• Must be a valid, accessible image URL
• Must be the official brand logo, not a generic icon
• PNG or JPG format

Google uses this logo in Knowledge Panel displays and in Article rich results (as the publisher logo).

Step 4: Create Person schema for each author

On each author bio page, add Person schema:

{
  "@context": "https://schema.org",
  "@type": "Person",
  "@id": "https://example.com/about/#person",
  "name": "Izajul Haque",
  "jobTitle": "Digital Marketing Consultant",
  "description": "Independent digital marketing consultant specializing in SEO, AEO, and GEO. I help brands get found in search results and cited in AI-generated answers.",
  "url": "https://example.com/about",
  "image": {
    "@type": "ImageObject",
    "url": "https://example.com/images/izajul-haque.jpg",
    "width": 400,
    "height": 400
  },
  "sameAs": [
    "https://www.linkedin.com/in/izajulhaque",
    "https://twitter.com/izajulhaque",
    "https://www.youtube.com/@izajulhaque"
  ],
  "worksFor": {
    "@id": "https://example.com/#organization"
  }
}

The @id creates a persistent identifier. The worksFor property links the Person to the Organization. The sameAs links reinforce the author's identity across platforms.

Step 5: Reference Person schema in Article author properties

In your Article or BlogPosting schema, reference the same Person entity:

"author": {
  "@id": "https://example.com/about/#person"
}

Or, if you are not using @id references, use matching name and url:

"author": {
  "@type": "Person",
  "name": "Izajul Haque",
  "url": "https://example.com/about"
}

Using @id is preferred because it creates an explicit link between the Article and the Person entity defined on the bio page. This is how Google and AI engines verify that the article author is a real, credentialed person — a core E-E-A-T signal. See SEO vs AEO vs GEO for how entity schema supports all three disciplines.

Step 6: Validate both Organization and Person schema

• Organization schema: Validate with Google Rich Results Test — Organization logo is a supported rich result type.
• Person schema: Validate with Schema.org Validator — Person is not a Google rich result type, but the validator confirms structural validity.

Fix all errors. Common errors include missing @context, broken sameAs links (404 pages), incorrect logo dimensions, and missing @id references. See schema markup for AI visibility and use the free SEO tools for related checks.

Common mistakes

• Listing fake or non-existent sameAs profiles — Only link to profiles that actually exist and are active. Broken sameAs links reduce trust signals and can cause Google to ignore the schema entirely.
• Missing the @id property — Without @id, you cannot reference your Organization or Person entities from other schema (like Article publisher and author). This breaks the entity graph on your site.
• Using a generic logo instead of the real brand logo — Google uses the logo in Knowledge Panels. A generic icon or placeholder weakens brand identity signals.
• Not updating Person schema when authors change roles — If an author's jobTitle or affiliation changes, update the Person schema. Stale credentials reduce E-E-A-T trust. See GEO consulting and the glossary for more on entity optimization.
• Placing Organization schema on every page instead of just the homepage — Organization schema belongs on the homepage. Other pages should reference it via @id, not duplicate it. Duplication creates conflicting entity definitions. See what is GEO for the broader entity strategy.