intermediate

Structured data

Use JSON-LD or microdata to expose product, article, breadcrumb, FAQ, and organization facts.

Structured data exposes on-page facts in a machine-readable vocabulary. JSON-LD is common because it lives in a script block and is easier to maintain than scattered microdata attributes. Article, product, organization, breadcrumb, and FAQ schemas can improve rich-result eligibility when content is truthful.

					<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Launch notes v2.4",
  "author": { "@type": "Person", "name": "Ada Lovelace" }
}
</script>
				

On interviews: structured data is not a ranking shortcut and must match visible content.

Common pitfalls: markup for hidden or false claims; hand-maintained JSON that drifts from the UI.

The trade-off is manual schema snippets versus generated JSON-LD — generation costs setup but prevents drift and penalties.

Checklist:

  • Prefer JSON-LD.
  • Mirror visible content only.
  • Validate with Rich Results Test.
  • Generate from shared page data.