Schema Markup
Schema markup is structured data using Schema.org types, typically JSON-LD, that describes page content for search engines and answer systems.
Also known as: schema-org-markup · json-ld-markup
Why it matters
Clear machine-readable labels improve eligibility for rich results, disambiguate entities, and help AI systems cite the right passage with correct attribution. Invalid or spammy markup wastes trust.
How it works
You add JSON-LD scripts describing visible entities: Organization, Article, FAQPage, Product, etc. Validators check syntax and required fields. Search systems compare markup to rendered HTML; mismatches can be ignored or penalized.
Common mistakes
- Marking up reviews or FAQs that are not visible to users.
- Duplicating conflicting schema blocks on one URL.
- Using wrong `@type` for the actual page format.
- Copy-pasting competitor schema without matching your content.
Best practices
- One primary type per page aligned with visible content.
- Use JSON-LD in head; keep properties synchronized with copy.
- Validate after CMS or template deploys.
- Include `url`, `headline`, `dateModified` on articles when shown.
Learn Domains perspective
When someone searches your brand plus "pricing," rich results only help if schema matches what is visible on the page. Content Operations drafts include structured data for articles and FAQs you actually publish, so you are not hand-coding JSON-LD in every template.
FAQ
- Does schema guarantee rich results?
- No. It enables eligibility; relevance and quality still decide outcomes.
- JSON-LD or microdata?
- JSON-LD is preferred, easier to maintain and validate separately from HTML.
- Should glossary pages use DefinedTerm schema?
- Yes when the page visibly defines a term, Learn Domains glossary routes follow this pattern.
Next steps
- 1Validate homepage Organization JSON-LD.
- 2Audit FAQ schema on top articles for visibility match.
- 3Fix template regressions after next deploy.
Knowledge graph
Parent terms
Child terms
Related concepts
entity-seo · on-page-seo · llms-txt