AI AI Tools Guidebook
Indie Dev & Website Building

Structured Data for Content Sites — Start With These Three Types

A no-jargon intro to JSON-LD structured data — the three schema types every content site should ship, and the ones to ignore until you scale.

Published: Author: AI Productivity Guide Team 🌐 查看中文版本

Structured data is the markup that tells Google “this thing on the page is an article / a person / a FAQ”. Done right, it earns you rich results — those star ratings, FAQs in the SERP, and author bylines that double click-through. Done wrong, it does nothing or gets you a manual action. Here is the version every content site can ship in one afternoon.

Background

Structured data is encoded as JSON-LD blocks inside a <script type="application/ld+json"> in your <head>. Google reads it to better understand page content and, for certain types, to display “rich results”. You do not need to add structured data for every entity on every page — start with three high-leverage types: Article, BreadcrumbList, and WebSite/Organization. Skip the rest until you have a reason.

How to tell

  • You have a content site (blog, docs, guides) with 10+ articles.
  • Your articles have an author, publish date, and a single canonical URL.
  • You want author / published-date metadata to appear in Google snippets.
  • You read about “FAQ rich results” and want to know if they are still worth doing in 2026.

Quick verdict

Ship Article, BreadcrumbList, and WebSite JSON-LD on every relevant page. Add FAQPage only if your article has a real FAQ section — and know that Google reduced FAQ rich-result eligibility in 2023, so visibility is lower than it used to be. Skip Product, Recipe, HowTo, Event unless they literally describe your content.

Step by step

  1. Audit one article. View source and search for application/ld+json. If you find nothing, you need to add structured data. If you find something, validate it.
  2. Add Article schema to every article page. Required fields: headline (matches <title> and <h1>), author (Person object with name), datePublished (ISO 8601), dateModified, image (full URL to the article hero). Optional but recommended: publisher, mainEntityOfPage.
  3. Add BreadcrumbList if you have a breadcrumb trail (Home -> Category -> Article). Mark up each step with position number and URL. Google may show breadcrumbs in the SERP instead of the URL.
  4. Add WebSite schema once, on the homepage. Include name, url, and optionally a SearchAction if you have a working site-search endpoint — that can unlock the sitelinks search box.
  5. Validate with Google’s Rich Results Test (/test/rich-results). Paste a URL or the JSON-LD itself. Read the warnings — they tell you exactly which optional fields would unlock more rich-result types.
  6. Deploy, wait 1-2 weeks, then check Search Console -> “Enhancements” panel for each schema type. It tells you how many pages Google recognized and any errors. Errors here are usually missing required fields.

Common pitfalls

  • Structured data that contradicts what is visible on the page. If your headline in JSON-LD differs from the <h1> text, Google may ignore the markup and treat it as spammy.
  • Marking up content as FAQPage when the page is not actually a FAQ. Google has rolled back FAQ rich results significantly; do not stretch the schema to get them.
  • Using HowTo for any article that mentions steps. HowTo is for actual step-by-step instructions for completing a single task (recipe, repair guide). A best-practices article with numbered tips is not a HowTo.
  • Including image URLs that 404 or that are smaller than 1200x630. Image rich-result eligibility has minimum size requirements; under-sized images get silently skipped.
  • Adding 5 different schema types per page “to maximize coverage”. The more you stuff, the more likely Google ignores some. Pick the schemas that genuinely describe the content.

Who this is for

Indie content sites that want author bylines, published dates, and breadcrumb-rich SERPs. Anyone preparing for AdSense (rich snippets often correlate with stronger content signals).

When to skip this

Pure marketing landing pages with no content body. Or sites whose framework already injects schema (most modern starters do); double-check first before adding more.

FAQ

  • Does JSON-LD affect rankings directly?: No — it does not boost rankings. It affects how Google displays your result (rich snippets, breadcrumbs, sitelinks search). Better display = higher CTR = more clicks at the same rank.
  • Are FAQ rich results still worth doing in 2026?: They show up much less often than they used to since Google’s 2023 rollback. Still worth adding to genuine FAQ sections — they are easy and you might get the rich result occasionally — but do not invent FAQs just to chase the snippet.
  • Should I use JSON-LD or Microdata?: JSON-LD. Google has preferred it for years and it is easier to maintain because it lives in <head> instead of being mixed into your HTML.
  • What is the difference between Article, BlogPosting, and NewsArticle?: BlogPosting extends Article and is more specific for blog posts. NewsArticle is for news (with stricter eligibility for Top Stories carousel). For typical indie blogs, Article is the safest, most portable choice.

Tags: #Indie dev #SEO #Technical SEO #Structured data

Related Articles