Original research · 2026
Schema.org for expert-led companies.
How to wire Organization, Service, Person, hasOfferCatalog, and BreadcrumbList — without fabricated review markup.
Schema.org is the schema vocabulary that powers most structured data on the web. For expert-led companies, the right schema stack is small, well-typed, and honest.
Why schema matters
Structured data is not a ranking signal. Google has said so for years. What schema does is provide unambiguous entity signals that search engines and generative systems can use to attribute claims and decide whether to cite a page.
For expert-led companies, schema is the difference between a page that is eligible to be cited and a page that is not. A page that declares a stable Organization @id, a Person author, and a Service type is materially more citeable.
The schema stack
Five types cover most of the value for an expert-led site: Organization, WebSite, Person, Service or Article per page, and BreadcrumbList on every non-home page. FAQPage is a useful sixth on pages with visible FAQ sections.
Organization declares the canonical entity: legal name, URL, logo, contact email, areaServed, knowsLanguage, and the sameAs links. The @id is stable.
Person is the founder. Use schema.org's Person type with worksFor pointing back at the Organization.
Service is emitted on service pages, Article on case studies and research, AboutPage on the about page, ContactPage on the contact page, WebPage as a default. BreadcrumbList accompanies every non-home page.
hasOfferCatalog, without prices
Service pages benefit from hasOfferCatalog with named offers. The mistake to avoid is fabricated priceSpecification.
For an expert-led company, the right hasOfferCatalog lists engagement models with descriptions that match what the company actually offers. No prices, no review counts, no aggregate ratings unless they are real.
FAQPage and visible FAQ
FAQPage schema is useful on pages with a visible FAQ section. The schema should mirror the visible content; mismatch between schema and visible FAQ is a manual action risk.
The schema is gated: emit it only when the visible FAQ is real.
What to leave out
AggregateRating is the most overused schema on the web. If the business does not have verifiable reviews, do not emit AggregateRating.
SpecialAnnouncement, Event, and JobPosting are tempting for SEO but rarely fit expert-led businesses.
Custom schema types are powerful but risky. We do not recommend them as a default.
Operational discipline
Schema decays. New pages need new schema; updated pages need updated schema. The quarterly review cadence includes a schema audit.
Bear In Code stores schema-relevant data in src/data and emits it from Layout. New pages pick up the schema by declaring the right page key.
Public references
- Schema.org — Organization, Service, Article
- Google Search Central — Structured Data General Guidelines
- Google Search Central — AI Overviews and your website
- HTTP Archive — Web Almanac: SEO chapter
- MDN — Using hreflang for international SEO
About the author
Daniel Sánchez Otero
Daniel leads Bear In Code from Germany. His background spans senior SEO, web engineering, and product work for expert-led companies across Europe. He treats SEO, GEO, and the website itself as a single revenue system — not separate deliverables.
Talk to Bear In Code