# Schema Types Explained: Person, Organization, Service, FAQPage & More

_2026-09-16 (updated 2026-10-06) · 6 min · by Ilias Sami · ~920 words_

> Every schema type describes a different kind of "thing," and using the right one, connected to the others correctly, is what turns a page from isolated markup into part of a coherent entity graph. The core types I use on nearly every engagement are Organization, Person, Service, FAQPage, BreadcrumbList, and Article, each doing a distinct, specific job, not interchangeable labels for the same generic content.

**Direct answer:** Every schema type describes a different kind of "thing," and using the right one, connected to the others correctly, is what turns a page from isolated markup into part of a coherent entity graph. The core types I use on nearly every engagement are Organization, Person, Service, FAQPage, BreadcrumbList, and Article, each doing a distinct, specific job, not interchangeable labels for the same generic content.

I get asked "which schema types do I actually need" often enough that a clear, practical reference is worth having, rather than pointing to schema.org's full, sprawling documentation every time.

# Organization

Describes the business or entity itself, name, logo, contact information, and critically, the sameAs array linking to verified external profiles. This is typically the anchor entity everything else on the site connects back to through @id references, the parent node the rest of the schema graph hangs off of.

# Person

Describes a named individual, a founder, an expert, an author, with their own credentials, professional history, and their own sameAs array. This matters especially for E-E-A-T signals, content attributed to a clearly-established Person entity, rather than an anonymous "admin" byline, carries meaningfully more credibility weight with both search engines and AI systems evaluating expertise.

# Service

Describes a specific offering, distinct from the general Organization schema, with its own name, description, and ideally a reference back to the Organization's @id. This is the type most commonly implemented incorrectly, in isolation, without that Organization cross-reference, exactly the disconnected-block problem covered in [schema agency vs. DIY plugins](/compare/schema-agency-vs-diy-plugins).

# FAQPage

Marks up genuine question-and-answer content directly, and it's one of the highest-leverage types for AI citation specifically, since it's already structured in the exact question-and-direct-answer format retrieval systems are built to extract cleanly. Worth using for genuine FAQ content, not stretched to cover content that isn't actually structured as real questions and answers.

# BreadcrumbList

Describes a page's position within a site's hierarchy, less directly tied to entity clarity than the types above, but useful for helping both traditional search results and AI systems understand site structure and content relationships.

# Article / BlogPosting

Describes long-form content itself, typically including an author reference back to a Person entity and a publisher reference back to the Organization, connecting a piece of content to the entities responsible for it, rather than leaving it as an anonymous, disconnected page.

{{BLOCK:0}}

# Why Using the Right Types Matters More Than Using More Types

I think there's a common instinct to add as many schema types as possible, assuming more markup is automatically better. It isn't, using the wrong type for a given piece of content, or adding types without proper @id cross-referencing back to the core Organization and Person entities, can create noise rather than clarity. The goal isn't maximum schema coverage, it's accurate, correctly-connected coverage, each type used for genuinely matching content, properly linked into the broader entity graph rather than floating as isolated, disconnected markup.

# How This Connects to the Broader @graph Architecture

Every type covered here is meant to function as one node inside a larger, connected @graph, not as standalone, isolated markup, the specific technical pattern covered in more depth in [what sameAs actually does](/seo-glossary/sameas-property) and in [entity SEO](/services/entity-seo) more broadly. Getting individual types right is necessary but not sufficient, the cross-referencing between them is what actually builds a coherent, machine-readable picture of the business.

# Frequently Asked Questions

**Do I need every schema type covered here on every page?**
**Direct answer:** No, each type applies to specific content, use Organization site-wide, Person for named individuals, Service for specific offerings, FAQPage only for genuine FAQ content, applying types accurately matters more than applying every type everywhere.

**Is there a schema type I'm likely missing that would help most?**
**Direct answer:** For most sites I audit, the most commonly missing high-value addition is a properly connected Person schema for named experts or founders, often the Organization schema exists but individual credibility signals don't.

**Can I use multiple schema types on the same page?**
**Direct answer:** Yes, this is common and often correct, a blog post page might combine Article, Person (author), and Organization (publisher) schema together, properly cross-referenced, rather than using just one type in isolation.

**Does adding more schema types directly improve rankings?**
**Direct answer:** Not directly or automatically, schema helps search engines and AI systems understand content accurately, which supports other ranking and citation factors, it's not itself a direct ranking boost independent of the content and entity signals it's describing.

**How often should schema types be reviewed and updated?**
**Direct answer:** Periodically, particularly when a business adds new services, team members, or content types that existing schema doesn't yet reflect accurately, stale schema describing an outdated version of the business can introduce the same inconsistency problems covered elsewhere on this site.

**Do I need every schema type this covers, or just a few relevant ones?**
**Direct answer:** Just the types that actually match your content, Organization and Person for identity, plus whichever content-specific types apply, Article, Service, FAQPage, forcing an irrelevant type onto a page adds noise rather than signal.

**What happens if I use the wrong schema type for my content?**
**Direct answer:** It can confuse rather than help, a mismatched type signals the wrong thing about what the content actually is, which is worse than having no schema on that element at all.

---

*Getting the right types, correctly connected, is core to every entity SEO engagement I run. [See what your own current schema setup actually covers](/chat).*

---
_Canonical page: [https://iliassami.com/blog/schema-types-explained](https://iliassami.com/blog/schema-types-explained) · Markdown generated on request from the live site content._