Schema Markup
Schema markup is the shared schema.org vocabulary that labels what your page content means. Learn the main types, how to add it, and what it earns you.
TL;DR
Schema markup is the shared vocabulary, maintained at schema.org, that labels what the content on a page means. It supplies the agreed names: Product, Article, FAQPage, Organization and several hundred more, each with defined properties. Search engines and AI engines both read it, which makes it the closest thing the web has to a common language for describing facts to machines.
Why schema markup matters
Every engine reading your page has to decide what your content is about. Schema markup answers that question directly instead of leaving it to inference.
- Shared vocabulary: Google, Bing and AI crawlers all recognise schema.org types, so one implementation serves every consumer.
- Rich result eligibility: Star ratings, price panels and FAQ dropdowns in search results require valid markup of the right type.
- Entity anchoring: Organization markup with sameAs links ties your site to your verified profiles, which helps engines confirm who you are.
- Reduced ambiguity: A price labelled as a price cannot be misread as a model number or a date.
How to add schema markup
Identify the page type
Decide what the page fundamentally is: an article, a product, a FAQ, a how-to. One primary type per page, with supporting types nested inside it.
Start with the required properties
Each type has properties engines expect. Article needs headline, author and dates; Product needs name, offers and availability. Fill those before optional extras.
Add Organization sitewide
Name, logo, URL and sameAs links to your verified profiles, placed on every page or at least the homepage.
Nest related types
A Product containing an AggregateRating and Offer describes a page more completely than three disconnected blocks.
Validate every template
Test one instance of each page template rather than every URL. Errors are almost always template-level.
Keep it in sync
When pricing or authorship changes on the page, the markup has to change with it. Drift between the two is worse than no markup.
Schema markup vs. structured data
Schema markup: The specific vocabulary from schema.org. It gives you the type names and property names to use.
Structured data: The broader practice of making page meaning machine-readable, of which schema.org markup is by far the most common implementation.
You can add structured data without schema.org, using other vocabularies or bespoke formats, but almost nobody does, because engines document support for schema.org and little else.
Valid markup is a precondition rather than an outcome. Findrix checks structured data as part of a 31-point technical audit, then tracks how often seven AI engines actually cite you against named competitors across your market prompts. Every gap comes with the fix already written: technical, content and off-site. The audit is free, takes about a minute, and requires no signup.
Schema types worth implementing first
- Organization: Establishes your brand as an entity, with logo and sameAs profile links.
- Article: For any editorial page, carrying author and modified date, both of which feed freshness signals.
- Product: For commerce pages, with price and availability that engines quote directly.
- FAQPage: Question and answer pairs that map onto the shape of AI-generated responses.
- BreadcrumbList: Site hierarchy, which helps engines place a deep page in context.
The most common schema mistakes
Marking up content that is not on the page is the one that carries a penalty. Review markup for reviews that do not exist, or prices that differ from the visible price, violates guidelines and can cost you rich results across the whole site.
The second is choosing the wrong primary type because it looks more valuable. Tagging a blog post as a Product to chase a shopping panel produces invalid markup and confuses engines about what the page is.
The quietest failure is drift: a pricing change updates the page and not the JSON-LD, so engines now have two contradictory prices from one URL.
Frequently asked questions
Does schema markup improve rankings?
Not directly. It makes pages eligible for rich results and helps engines interpret content accurately, both of which affect clicks and citations. Google has stated repeatedly that markup is not itself a ranking signal.
Which schema types should a B2B SaaS site use?
Organization sitewide, Article on blog and guide pages, FAQPage where you genuinely answer questions, BreadcrumbList for hierarchy, and SoftwareApplication or Product on pricing pages. That covers most of what engines will use.
Do AI engines read schema markup?
They parse it when they fetch a page, and it helps them attribute facts correctly. It carries less weight than it does for search rich results, because AI answers draw on many sources at once and prose clarity often matters more than markup precision.