Add structured data (JSON-LD) for blog articles

[kahboom]

Problem

Blog articles currently lack structured data (Schema.org markup), which limits:

• Rich snippet eligibility in search results
• AI crawler understanding of content structure
• Enhanced search result displays (author, date, reading time)
• Article discoverability and categorization

Proposed Solution

Add JSON-LD structured data to all blog post pages with Article schema:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article Title",
  "description": "Article description",
  "author": {
    "@type": "Organization",
    "name": "OpenThreads"
  },
  "publisher": {
    "@type": "Organization",
    "name": "OpenThreads",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.openthreads.dev/assets/logo.png"
    }
  },
  "datePublished": "2024-11-12",
  "dateModified": "2024-11-12",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://www.openthreads.dev/blog/article-slug"
  }
}

Implementation Steps

1. Create a StructuredData component that accepts article metadata
2. Add it to blog post template using react-helmet-async
3. Include Article, Organization, and BreadcrumbList schemas
4. Validate with Google's Rich Results Test
5. Test with Schema.org validator

Additional Schemas to Consider

• BreadcrumbList - Navigation breadcrumbs
• Organization - Homepage
• WebSite - Search action markup
• FAQPage - If we add FAQ sections

Benefits

• ✅ Eligible for rich snippets in search results
• ✅ Better content understanding by AI crawlers
• ✅ Enhanced search result displays
• ✅ Improved click-through rates
• ✅ Better content categorization

Resources

• Schema.org Article
• Google Article Structured Data
• JSON-LD Best Practices

Labels

enhancement, SEO, content

[JohnnyLagneau]

Good issue. If the goal is AI/search discoverability rather than just schema completeness, I’d tighten the first pass around citation-safe article pages:

1. emit Article JSON-LD server-side in the initial HTML, not only after hydration
2. make headline, description, datePublished, dateModified, canonical URL, and author/publisher match the visible page copy exactly
3. add a short answer-first summary near the top of each post so retrieval systems have a clean paragraph to quote
4. include BreadcrumbList only if the visible breadcrumbs are real and stable

Quick verification loop I’d use before broad rollout:

• curl the built page and confirm the JSON-LD is present in raw HTML
• validate 3 representative posts in Schema.org validator
• compare one older post vs one freshly updated post to ensure dateModified changes correctly

That usually ships more value faster than trying to expand every schema type at once.