What Schema.org Actually Is
Schema.org is a shared vocabulary of types and properties for describing things on the web. For example, its vocabulary includes a Recipe type and properties such as cookTime. The vocabulary defines terms; it does not determine how a particular search engine uses them (sourceRef: https://schema.org/docs/gs.html).
Schema.org was launched in 2011 by Google, Microsoft, Yahoo, and Yandex as a shared initiative (sourceRef: https://schema.org/docs/gs.html). The distinction between the vocabulary and an individual search engine’s features is important: Schema.org defines the terms, while Google documents which structured data it supports for Search and what conditions apply (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
Why Schema.org Matters for SEO
Structured data provides explicit, machine-readable information about page content. Google says it uses structured data to understand the content of a page and to make pages eligible for certain search features; it does not say that adding structured data guarantees a feature or improves rankings (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
Presentation is conditional. Google’s documentation says a page must meet the relevant feature’s technical and content guidelines to be eligible, and that eligibility does not guarantee the feature will appear. Google may show a different result based on the search, device, location, or other factors (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data). A rich result’s display is also not a promise of more clicks; Google does not guarantee a particular click-through outcome in its structured-data guidance.
Schema markup should not be treated as a ranking lever. Google explicitly says structured data does not affect rankings in web search; it can make a page eligible for supported search features, subject to the relevant guidelines and Google’s decision to show them (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
Rich Results Aren’t a Schema-Only Club
Structured data is not required for Google to generate ordinary search results or snippets. Google says its systems use page content to generate snippets, and may choose a different source for a snippet if that better helps users (sourceRef: https://developers.google.com/search/docs/appearance/snippet). Structured data has a separate role: it can help Google understand page information and may qualify a page for specific rich-result features (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
That is not a guarantee that a search engine will interpret every page correctly, or that markup is irrelevant. It means schema is not a prerequisite for Google to parse page content or create a standard snippet, and that feature eligibility depends on the feature’s own requirements.
Types Worth Knowing
Schema.org defines many types. Choose types that accurately describe the content, rather than adding markup merely because a type exists. Google’s supported-feature documentation lists the structured data types that can make pages eligible for Google Search features; Schema.org’s broader vocabulary and Google’s feature list are not the same thing (sourceRefs: https://schema.org/docs/full.html, https://developers.google.com/search/docs/appearance/structured-data/search-gallery).
Organization, WebSite, BreadcrumbList, Article, Product, VideoObject, Event, and Recipe are examples of types with definitions in Schema.org. Whether a type supports a particular Google Search feature, and what requirements apply, should be checked in Google’s current Search Gallery rather than inferred from the vocabulary alone (sourceRefs: https://schema.org/docs/full.html, https://developers.google.com/search/docs/appearance/structured-data/search-gallery).
FAQ and HowTo require particular care. Google announced in August 2023 that FAQ rich results would generally be shown only for well-known, authoritative government- and health-focused websites. The change was intended to reduce their visibility in Search; it did not remove the FAQPage type from Schema.org. Google’s current FAQ documentation retains the limited eligibility criteria and cautions that eligible pages are not guaranteed to receive FAQ rich results (sourceRefs: https://developers.google.com/search/blog/2023/08/howto-faq-changes, https://developers.google.com/search/docs/appearance/structured-data/faqpage).
Google also announced that HowTo rich results would be removed from Search on September 13, 2023, and its Search documentation no longer lists HowTo as a supported Search feature. HowTo remains a Schema.org type, but adding HowTo markup should not be presented as a way to obtain a Google HowTo rich result (sourceRefs: https://developers.google.com/search/blog/2023/08/howto-faq-changes, https://developers.google.com/search/docs/appearance/structured-data/search-gallery).
These changes concern Google Search feature availability, not whether FAQPage or HowTo terms exist in the Schema.org vocabulary. Use markup only when it accurately describes visible page content, and check current Google documentation before making claims about eligibility or display (sourceRefs: https://schema.org/FAQPage, https://schema.org/HowTo, https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
Formats: JSON-LD, Microdata, RDFa
Schema.org terms can be expressed in different formats, including JSON-LD, Microdata, and RDFa. Google supports all three formats for its structured-data features and recommends JSON-LD when possible (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
JSON-LD is commonly added in a <script type="application/ld+json"> block. Microdata and RDFa use attributes in the HTML. Whichever format you use, Google’s guidance requires that the structured data represent the page’s visible content and comply with the applicable feature policies (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
What Schema Won’t Do for You
Structured data does not guarantee higher rankings, eligibility for every rich result, display of a rich result, or additional clicks. Google says it does not affect web-search rankings, and its feature documentation makes clear that eligibility does not guarantee display (sourceRef: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
It is also not a substitute for page content. Google can generate ordinary snippets from page content without structured data, and structured data is relevant to the particular search features Google supports—not a requirement for a page to appear in Search (sourceRefs: https://developers.google.com/search/docs/appearance/snippet, https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data).
Getting Started Without Overpromising
Choose markup that accurately describes the page and use a format supported by the search engine feature you are targeting. Ensure the structured data reflects visible content and follows Google’s general and feature-specific guidelines. Google recommends testing structured data and monitoring relevant Search Console reports, while noting that passing a test does not guarantee a rich result will appear (sourceRefs: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data, https://developers.google.com/search/docs/appearance/structured-data/sd-policies).
Treat markup as a way to provide structured information and, where a supported feature applies, seek eligibility—not as a promise of rankings, a particular search appearance, or more clicks.