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
Which signal is most important for AI search citation?
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.
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.
Schema Types Explained: Person, Organization, Service, FAQPage & More — self-check
Reviewed: 0/5 (0%)
Why Using the Right Types Matters More Than Using More Types
How has AI Overview affected your or clients' organic traffic quality?
Click to vote • Results shown after voting
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 and in 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.