Schema.org lists over 800 vocabulary types. That number exists to describe everything on the internet — Taxons, MedicalTrials, PoliceStations, SportsTeams, Volcano types, all of it. It is not a to-do list for your content operation.
Thank you for reading this post, don’t forget to subscribe!The number that matters to most content teams is closer to six. Six types that affect what Google knows about your content and what your search listing actually looks like. Everything else can wait until you have a specific reason to need it.
Here they are.
FAQPage marks up a series of question-and-answer pairs on a page and makes your listing eligible for the FAQ accordion in Google Search — the dropdown that expands directly in the SERP to show your questions and answers. The user gets an answer without clicking. Your listing takes up more visual space. CTR goes up.
The content requirement is non-negotiable: the questions and answers have to be visible on the page, readable by anyone who visits. FAQPage schema does not let you add questions that exist only in the structured data. If the Q&A isn’t there for humans to read, Google won’t display it, and depending on what you’ve done, may flag it as a violation.
This is the most commonly misimplemented schema type on content sites. People add FAQPage markup to pages that don’t have FAQ sections, then wonder why nothing changes in search.
The sequence is: write the FAQ section first, then add the schema. Not the other way around.
Use FAQPage on any post that contains question-and-answer content — a formal FAQ block at the bottom, sections structured as questions with answers, common objections addressed directly. The format is flexible. The content requirement is not.
HowTo marks up step-by-step instructional content and makes your listing eligible for the HowTo rich result — a numbered list of steps shown directly in Google Search, with images if the schema includes them. It looks like a recipe card but it works for any instructional content.
The content requirement is the same as for FAQPage: the steps have to be on the page. And the steps have to be actual steps — discrete, sequential actions with a clear outcome. “Think carefully about your content goals” is not a step. “Open Google Analytics, navigate to Acquisition > Search Console > Queries, and filter for queries with more than 100 impressions” is a step.
HowTo schema is worth implementing when your content is genuinely instructional: walkthroughs, tutorials, process guides, anything with a numbered list of discrete actions. It’s not appropriate for persuasive essays, case studies, or analysis posts that happen to have some advice in them. The schema type has to match the content type.
One honest caveat: HowTo rich results display inconsistently on mobile, and Google has shifted how it treats this type over time. Use it when the content fits. Don’t build your entire traffic strategy around it.
BreadcrumbList marks up the navigational path to a page and replaces the raw URL in your search listing with a human-readable trail: Home > Blog > Schema. It’s a small thing. It’s also something most sites with active SEO plugins already have, which means the main task here is confirming it’s present and valid rather than implementing it from scratch.
If you’re using Yoast SEO with breadcrumbs enabled on your site, you almost certainly already have BreadcrumbList schema. Run the Rich Results Test on any post URL and check the detected types. If it’s there and valid, move on.
If it’s missing, check your SEO plugin’s breadcrumb settings and your theme’s breadcrumb display — the schema generates from the displayed breadcrumbs, so the display has to be active.
Always have this. It’s low effort, it’s widely supported, and there’s no good reason for it to be missing.
Organization and Person don’t earn rich results in the traditional sense. They don’t change what your search listing looks like. They do something more foundational: they establish your business and your authors as defined entities in Google’s knowledge graph.
Organization schema lives at the site level — typically on the homepage and in a site-wide header — and tells Google who runs this site. Name, URL, logo, contact information, social profiles, and business type. Fill it in completely, including the sameAs property with links to your social profiles, Google Business Profile, LinkedIn, and anywhere else your organization is definitively identified online. This is how Google connects your content to a real, verifiable entity.
Person schema does the same thing for individual authors. Name, URL (the author page or personal site), job title, affiliation (linked to the Organization), and sameAs links to LinkedIn and other identified profiles. For bylined content operations, Person schema is how Google understands that the person named in your Author schema is a real human with a verifiable professional identity — not just a string of text in an author field.
Why this matters increasingly: AI-generated overviews, knowledge panels, and entity-based search all rely on the ability to connect content to verified entities. E-E-A-T signals are becoming more entity-driven, not less. Vague authorship — no author page, no sameAs links, no Person schema — is a gap that becomes more expensive to leave unfilled the longer you wait.
Configure both in your SEO plugin’s settings — Yoast has a dedicated Organization section; Rank Math has Author schema controls — and then confirm they’re outputting completely using View Source or the Rich Results Test.
Article (done correctly, not just present)
You probably already have Article schema. The question is whether it’s complete.
Most SEO plugin defaults generate Article schema with the minimum viable properties — headline, author name, publisher name, dates. What makes Article schema actually useful is the full set of properties:
headlineauthor(as an entity with a URL, not just a name string),datePublished&dateModifiedpublisher(linked to your Organization entity)image(required for Google Discover eligibility)mainEntityOfPage.
The @id property matters: it’s how you link the Article’s author to your defined Person entity, and the publisher to your defined Organization entity. Without @id, you have a name. With it, you have a connection to an established entity graph.
This is the difference between schema that validates and schema that does something.
The sub-type question is minor but worth knowing: Article, NewsArticle, and BlogPosting are all valid, with BlogPosting being technically most accurate for blog content. Google treats them similarly for rich result eligibility. Use whichever your plugin defaults to unless you have a specific reason to override it.
VideoObject marks up video content and makes it eligible for video rich results in search — thumbnail, title, duration, and upload date shown directly in the SERP. This matters most for video content hosted on your own site or embedded from YouTube when you want the rich result to appear on your domain rather than YouTube’s.
Use it when video is the primary content of a post, not a decorative addition. A post built around a tutorial video warrants VideoObject schema. A post with a background video header does not.
If your video content lives entirely on YouTube and you’re not publishing it on your own site, YouTube handles the structured data. VideoObject becomes relevant when you’re embedding content on your own domain and want your listing — not YouTube’s — to surface in video search.
The honest accounting
FAQPage and HowTo are where visible rich results come from for content teams. BreadcrumbList is table stakes. Organization and Person are foundational — they don’t change search listings but they build the entity graph that increasingly determines whether Google trusts your content. Complete Article schema is what makes all of it cohere.
That’s the real list. VideoObject gets added when you publish video as primary content. The other 794 types exist for specific contexts — ecommerce, healthcare, local services, events — and become relevant when those contexts apply to you.
The question to ask for any schema type isn’t “could this apply?” It’s “does my content actually warrant this, and is the required content already on the page?” If the answer to both is yes, implement it. Validate it. Move on.
If the answer to either is no, skip it until it isn’t. When you’re ready to implement: get to scheming.
I write about content strategy, fractional editorial leadership, and the professional reality of this kind of work.
For inquiries: jacob@cliftoncreative.agency · cal.com/cliftoncreative