Esc
  • Jump to
  • The board
  • All launchesSort and filter by week or category
  • Open statsEvery number, in public
  • Maker storiesApps that stopped hiding
  • Submit a launch
  • AICategory
  • AnalyticsCategory
  • API & BackendCategory
  • Audio & VoiceCategory
  • AutomationCategory
  • CommunityCategory
↑↓ to move↵ to openPress / anywhere
Sign in

What is Structured Data (JSON-LD)?

Standardized machine-readable metadata, typically written in JSON-LD using the Schema.org vocabulary, that explicitly describes a page's entities and attributes to search engines and AI parsers.

Updated · SEO & AI Search

Plain definition

Definition of Structured Data (JSON-LD)

Standardized machine-readable metadata, typically written in JSON-LD using the Schema.org vocabulary, that explicitly describes a page's entities and attributes to search engines and AI parsers.

Formula / syntaxscript type="application/ld+json" -> "@context": "https://schema.org", "@type": "SoftwareApplication"

Worked example

Google Search supports three structured data formats: JSON-LD, Microdata, and RDFa, and explicitly recommends JSON-LD because it lives cleanly inside a standalone script block rather than tangling with your visual HTML markup. Most search structured data uses the shared vocabulary published at Schema.org, while Google's own documentation defines which specific types and required properties qualify for rich results.

Say a made-up habit tracker called StreakKite launches a web and iOS app. On its homepage, it embeds a JSON-LD block describing an Organization entity and a SoftwareApplication entity with its product name, applicationCategory, operatingSystem, and starting price inside an Offer object. On its help guides, it emits Article and BreadcrumbList blocks. Before shipping, the founder runs the rendered HTML through Google's Rich Results Test and the Schema Markup Validator to catch missing fields or stray commas.

Why it matters when you launch

A new SaaS has to teach search engines and answer engines basic facts quickly: what the product is called, what category it belongs to, what it costs, who built it, and how its pages fit together. Plain prose leaves room for ambiguity, especially when your brand name is also an everyday English word. Clean JSON-LD removes that guesswork by stating entity types, prices, authors, and breadcrumb hierarchy explicitly.

Keep expectations grounded: Google Search Central makes clear that valid structured data makes a page eligible for rich results, not guaranteed to show them. Even without a special snippet, accurate schema strengthens entity recognition across both traditional search and AI retrieval systems.

Common mistakes

  • Marking up facts in JSON-LD that do not appear visibly to human visitors on the page, such as hidden star ratings or fake review counts, which violates Google's structured data policies.
  • Shipping malformed JSON with trailing commas, unescaped quotes, or invalid date formats without checking the live URL in Google's Rich Results Test.
  • Adding irrelevant schema types like FAQPage or Product onto every route just to chase rich snippets instead of matching the actual page type.
  • Forgetting to update Offer prices or software descriptions inside your JSON-LD template after changing your pricing page, leaving search engines with stale numbers.

Tools and guides that use it

Official sources

Pritam Ghosh runs Hauntboard and maintains this glossary.

Published · Updated

Building something real? Launch it in public.

A person reviews every launch on Hauntboard, and every view and visit it sends your site is published on your launch page. Free to submit.

Launch free →

On the board

All →

Still hiding your app?

Put it on the board. Reviewed by a person, free to launch.

Launch free
Submit a launch