All JSON-LD Schema.org types match page content with critical properties present

A JSON-LD block with the wrong @type or missing critical properties like name, description, and url is worse than no schema at all — it tells search engines you have content structure, then fails to describe it. Google's schema-org BlogPosting and Product parsers skip incomplete records for Rich Results eligibility. A product page with a generic Thing type instead of Product receives zero structured-data SERP benefit. Incomplete schema is technical debt that accumulates silently until a Rich Results Test exposes it.

Audit each JSON-LD block against the Schema.org type specification. Update incomplete blocks in the relevant page component — app/blog/[slug]/page.tsx for articles, app/products/[slug]/page.tsx for products. At minimum, every object needs name, description, and url:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Widget Pro",
  "description": "High-performance widget for professional use",
  "url": "https://yoursite.com/products/widget-pro",
  "offers": {
    "@type": "Offer",
    "price": "29.00",
    "priceCurrency": "USD"
  }
}

Never use Thing where a specific type applies. The Google Rich Results Test will flag type mismatches; fix them before they compound across pages.