Semantyra
Blog

Which schema types actually matter for SEO

2026-09-07

Schema markup is structured data, usually JSON-LD in the page head, that states what a page represents: this is a product with this price, this is an article by this author, this is an FAQ with these questions. It does not change what a reader sees. It gives machines an unambiguous statement they can act on. A small number of types do most of the work.

Organisation and Person

Organisation markup on your home page or about page, with a logo, a description and sameAs links to your official profiles, is the foundation of your entity. Person markup for named authors, with credentials and sameAs links, does the same for the people behind the content.

These are the types that help a search engine resolve who you are and connect you to the rest of the knowledge graph. They are also the ones most sites skip.

Article and BreadcrumbList

Article markup on editorial pages states the headline, the author, the published and modified dates, and the publisher. It reinforces authorship and freshness, both of which feed quality signals.

BreadcrumbList markup states where a page sits in the site hierarchy. It can produce a breadcrumb in the search result and it reinforces your internal structure for machines.

FAQPage, Product and the ones that enable rich results

FAQPage markup can produce an expandable FAQ directly in the search result for pages that genuinely answer common questions. Product markup with price, availability and reviews can produce rich product results. HowTo, Recipe and Event have their own display treatments.

Only mark up content that is actually on the page and visible to a reader. Marking up content that is not there is a policy violation and can cause the markup to be ignored or the site penalised.

Keeping schema honest

The common failure is drift. Someone edits the visible content and the JSON-LD is left describing the old version. A price changes on the page but not in the markup. An author byline is updated but the Person markup still names the previous writer.

Validate schema after any content edit, keep it generated from the same data that renders the page where possible, and check it during audits. Semantyra reads the structured data on every crawled page and factors its presence and validity into the technical-health and entity signals.

The takeaway

Focus on Organisation, Person, Article and BreadcrumbList as the structural base, add FAQPage or Product where the content supports a rich result, only mark up what is visible on the page, and validate after every content change so the markup does not drift.

Related

See this measured on your own site.

Start free scan