JSON-LD for a technical blog post: Article markup that is accurate

Add a single JSON-LD block to each post using the Article or BlogPosting type, fill in headline, dates, author and image, and make every value match what readers can see on the page. Google documents no required properties for Article, so accuracy matters more than volume.

Why JSON-LD

Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD because it is easier to implement and maintain at scale and sits apart from the visible text. Google adds that structured data can enable enhanced results but does not guarantee them.

The properties Google recommends

For Article, NewsArticle and BlogPosting, Google lists these:

• headline: the title. Concise is better because long titles may be truncated.
• datePublished: when the article first went live, in ISO 8601, with a timezone.
• dateModified: when it last changed, same format.
• author: a Person or Organization, with a name and a url or sameAs.
• image: representative images, not logos.

An example

{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Reading a dependency scan report",
  "datePublished": "2026-10-19T09:00:00+00:00",
  "dateModified": "2026-10-19T09:00:00+00:00",
  "author": [
    {
      "@type": "Person",
      "name": "Jane Doe",
      "url": "https://example.com/authors/jane-doe"
    }
  ],
  "image": ["https://example.com/img/scan-report-16x9.png"]
}

Place it in a script tag with type application/ld+json. Names and URLs here are placeholders.

Author rules worth following

Google's guidance is specific. Include every author shown on the page. Give each author a separate entry rather than joining names in one field. Use Person for people and Organization for organizations. Keep the name field to the name alone, with no job titles or phrases like "posted by". Add a url or sameAs to help identify the author.

Do not invent an author to look credible. Google's people-first content guidance warns against fabricated creators.

Technical articles

Schema.org also defines TechArticle, a subtype of Article for how-to topics, step by step procedures and troubleshooting. It adds dependencies and proficiencyLevel properties. Google's documented Article types are Article, NewsArticle and BlogPosting, so I would use one of those for Search and treat TechArticle as optional vocabulary. Check the current Google documentation before relying on any other type.

Test and monitor

1. Validate with the Rich Results Test while building.
2. After release, watch the rich result reports in Search Console. Template changes can silently break markup.
3. Use URL Inspection to confirm Google found the data on a given page.

Quick check

Sources

• Introduction to structured data, Google Search Central
• Article structured data, Google Search Central
• TechArticle, schema.org
• Creating helpful content, Google Search Central

Last reviewed: 19 October 2026.