Schema Markup Types: choosing structured data that actually fits

Quick Definition

Schema Markup Types are structured data types that describe page content in a standardized vocabulary. They help search engines understand whether a page is an article, product, course, video, local business, breadcrumb trail, person profile, or another entity. The most common vocabulary is Schema.org; for Google Search, JSON-LD is usually the preferred implementation format because it is easier to maintain than Microdata or RDFa.

The most important idea is simple: Schema Markup does not invent truth. It describes the truth that is visible on the page. If a page does not sell a product, Product markup is wrong. If no real reviews are visible, Review markup is risky. If a FAQ is hidden only for search engines, FAQPage is not clean implementation. Good markup is therefore less a trick than an editorial discipline.

Terms Covered Here

• Article Schema
• FAQPage Schema
• HowTo Schema
• Product Schema
• Review and AggregateRating
• Organization, LocalBusiness and Person
• BreadcrumbList, WebSite and ItemList
• VideoObject and SpeakableSpecification
• Course and SoftwareApplication
• MedicalWebPage
• JSON-LD, rich results and validation

Simple Explanation

Think of Schema Markup as labels in a well-organized warehouse. One box does not just say "content"; it says "product", "price", "availability", "rating" and "image". Another says "article", "author", "date" and "main image". These labels do not make the goods better, but they make their meaning clearer.

For SEO, that is valuable because search engines need to classify content, not merely render it. Structured data can make rich results possible, sharpen entity understanding and expose template problems. It does not guarantee display. Google is explicit that valid markup does not guarantee a rich result. The algorithm decides whether a feature fits the search experience.

JSON-LD: The Practical Default

Google supports JSON-LD, Microdata and RDFa, but recommends JSON-LD when the site setup allows it. The reason is practical: JSON-LD sits separately from visible HTML in a script block with type application/ld+json. It is easier to generate, test and version. For modern CMS, ecommerce and framework projects, it is usually more robust than maintaining attributes across the HTML tree.

Still, JSON-LD is only the format. The real quality comes from mapping. What is the main thing on the page? Which entities are visible? Which properties are provable? Which fields change often and need automated updates? Markup can be technically valid and still poor if it describes stale prices, old ratings or content users cannot see.

Content Schemas: Article, FAQPage and HowTo

Article Schema fits editorial articles, news, blog posts and similar content pages. Useful fields include headline, author, date, image and publisher. It helps Google understand the page as published content. For glossary entries, Article or a more specific CreativeWork or DefinedTerm-style model may fit depending on the system, but for Google rich-result purposes Article is mainly relevant to real article pages.

FAQPage and HowTo require special care in 2026. FAQPage is still a valid Schema.org type: a page that presents questions and answers can describe them this way. However, Google documented in May and June 2026 that FAQ rich results no longer appear in Google Search. HowTo is also still valid as a Schema.org type, but Google previously removed HowTo rich-result documentation because that rich result is no longer shown. The practical conclusion: FAQPage and HowTo can still help semantic clarity, internal search or other consumers, but they should not be sold as primary Google visibility levers.

Commercial Schemas: Product, Review, SoftwareApplication and Course

Product Schema is powerful when a page truly describes a product: name, images, offers, price, availability, variants, reviews and merchant information. It is also one of the areas where bad data becomes obvious quickly. Price, availability and ratings must be current and visible to users.

Review Snippet markup describes Review and AggregateRating data. It must not be used for invented, hidden or self-serving stars. Google has specific rules for review snippets; violations can remove rich-result eligibility. SoftwareApplication fits app and software pages when operating system, category, rating and offer data are present. Course markup is especially relevant to course lists; a generic sales block without actual course data is not a strong candidate.

Organization, LocalBusiness and Person

Organization markup helps Google understand administrative and identity details: name, URL, logo, contact details, address, social profiles and other identifiers. It often belongs on the homepage or a central About page, not blindly on every URL with conflicting data.

LocalBusiness is more specific. It fits physical locations or branches with address, opening hours, phone number and local attributes. A SaaS company without a visitor-facing local location should not force LocalBusiness markup. Person markup fits authors, expert profiles, founders or medically reviewed content when the person is visible and relevant. The more a page depends on trust, the more important clean entity clarity becomes.

Navigation and Site Structure: BreadcrumbList, WebSite and ItemList

BreadcrumbList is one of the most practical schema types because it describes where a page sits in the site hierarchy. It is useful for large sites, shops, glossaries and content hubs. Strong breadcrumbs are visible in the interface, not only hidden in JSON-LD.

WebSite markup can describe the website as a whole. It was often associated with the Sitelinks Search Box, but Google has removed that documentation. WebSite can still be semantically useful when it accurately represents the domain. ItemList describes ordered or curated lists: categories, top lists, course lists, collections or comparison pages. The mistake is inflating every random block of links into an ItemList.

Media, Special Cases and Sensitive Content

VideoObject is appropriate when a video is visible and important on the page. Title, description, thumbnail, upload date, duration and embed information need to match. Without a visible video, VideoObject is misleading. SpeakableSpecification exists in Schema.org and appears in Google's feature landscape, but it is not a generic SEO standard for every page. Use it only where the specific requirements are truly met.

MedicalWebPage is a good example of a sensitive special type. Medical content needs extra care: factual accuracy, review, clear authorship and no misleading claims. Schema can structure those signals, but it cannot replace medical quality. On YMYL topics, wrong markup is worse than no markup.

Which Schema Types Create the Most Value?

The most valuable schema type is the one that correctly describes the main content and is supported for the search surface you care about. For an ecommerce product page, Product is often central. For a local clinic, LocalBusiness. For a content hub, BreadcrumbList, Article and clean Organization or Person entities. For a video page, VideoObject. For a course directory, Course and ItemList.

A practical rollout order is: inspect required visible data, check Google support, generate JSON-LD, test with the Rich Results Test and URL Inspection, then monitor Search Console. Schema is not a one-time checkbox. Prices, reviews, availability, author details and URLs drift.

Common Mistakes

• Markup describes content users cannot see.
• Every page receives the same Organization block without page context.
• Review stars are invented or self-serving.
• FAQPage is still sold in 2026 as a Google FAQ-rich-result growth lever.
• Product is used on category pages or lead pages that do not sell one product.
• Breadcrumb markup does not match visible navigation.
• JSON-LD is forgotten, duplicated or shipped with old URLs during relaunches.
• Passing validation is confused with guaranteed rich-result display.

Contextter Angle

Contextter treats Schema Markup as a content-structure problem, not only a technical afterthought. Useful structured data comes from useful structure: clear entities, coherent sections, real authorship, accurate product data, visible questions, real media and consistent internal links. When the brief already clarifies which entity a page explains and which facts are visible, JSON-LD becomes easier, cleaner and more honest.

Sources for Review

• Intro to structured data: https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data
• General structured data guidelines: https://developers.google.com/search/docs/appearance/structured-data/sd-policies
• Search Gallery: https://developers.google.com/search/docs/appearance/structured-data/search-gallery
• Article structured data: https://developers.google.com/search/docs/appearance/structured-data/article
• Breadcrumb structured data: https://developers.google.com/search/docs/appearance/structured-data/breadcrumb
• Product structured data: https://developers.google.com/search/docs/appearance/structured-data/product
• Review snippet structured data: https://developers.google.com/search/docs/appearance/structured-data/review-snippet
• Organization structured data: https://developers.google.com/search/docs/appearance/structured-data/organization
• Local business structured data: https://developers.google.com/search/docs/appearance/structured-data/local-business
• Video structured data: https://developers.google.com/search/docs/appearance/structured-data/video
• Software app structured data: https://developers.google.com/search/docs/appearance/structured-data/software-app
• Course list structured data: https://developers.google.com/search/docs/appearance/structured-data/course
• FAQ rich result removal: https://developers.google.com/search/updates#removing-faq-rich-result
• FAQPage type: https://schema.org/FAQPage
• HowTo type: https://schema.org/HowTo
• MedicalWebPage type: https://schema.org/MedicalWebPage
• SpeakableSpecification type: https://schema.org/SpeakableSpecification
• ItemList type: https://schema.org/ItemList