DEV Community

Hieu Le
Hieu Le

Posted on Originally published at sitecheckly.com

JSON-LD Structured Data: Five Types to Add First

Originally published on Sitecheckly.

Start with Organization and WebSite markup for your business and site, then add Article, FAQPage, and BreadcrumbList where the page content supports them. These types describe entities and page content, but they do not guarantee rich results or AI citations. In the Sitecheckly survey, 51% of analyzed sites had no Schema.org structured data.

What is JSON-LD structured data?

JSON-LD is a format for expressing structured data inside a script element. It gives search engines a machine-readable description of the content on a page. Google can use supported structured data to understand that content and make eligible pages available for certain search features, as explained in its introduction to structured data.

The survey figures come from the October 2026 Sitecheckly survey of the Tranco top 10,000 (Tranco list 7462X). The ranking covers 2026-10-02 to 2026-10-31. The home pages were fetched on 2026-11-01. Of those domains, 4,934 of 10,000 could be analyzed. The rest were mostly CDN, DNS and API hosts, sites that ask crawlers to stay away in robots.txt, or sites that blocked automated requests. See the survey methodology for the scope and limitations.

Treat structured data for SEO as a description, not a promise of visibility. Adding markup does not guarantee an AI answer citation either. For the broader context, read what answer engine optimization means.

The practical starting point is simple: choose a type that matches the page, replace every example value, and check the published result. Do not add all five types to every URL.

Which JSON-LD types describe your organization and website?

Organization and WebSite answer different questions: who is behind the site, and what is the site called?

Organization: identify the organization

Google says Organization structured data can help it understand and disambiguate an organization. Use details that match the organization represented on your site.

This minimal example identifies an organization by its name and URL:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Company",
  "url": "https://example.com/"
}
</script>
Enter fullscreen mode Exit fullscreen mode

Replace Example Company with your actual organization name and https://example.com/ with its real home page URL. Do not publish the placeholder values.

Start with information you can verify. If you add more properties, use the Organization documentation to check their meaning rather than guessing from their names.

WebSite: describe the site itself

Use WebSite markup on the home page. Google uses it as a signal for the site name shown in search, but it does not guarantee that your preferred name will appear. Follow Google's site name guidance.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Example Company",
  "url": "https://example.com/"
}
</script>
Enter fullscreen mode Exit fullscreen mode

These examples look similar because both include a name and URL. Their types give those values different meanings. Organization describes the organization; WebSite describes the website.

Use the actual site name for WebSite. Do not turn the name field into a list of search keywords.

When should you add Article and FAQPage markup?

Add these types only when the page contains the content they describe. The following JSON-LD examples are minimal starting points, not complete content models or guaranteed rich-result recipes.

Article: describe an actual article

Use Article for a page that is an article. Google says Article structured data can help it understand the page and display better title text, images, and date information.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Example article"
}
</script>
Enter fullscreen mode Exit fullscreen mode

Replace the headline with the article's actual headline. Then review the relevant recommended properties in Google's documentation. Add details such as author, images, and publication or modification dates when they are available and accurate.

Do not invent a publication date to fill a field. Do not use Article merely because a product page or contact page contains a few paragraphs of text.

The snippet above demonstrates the type and headline. It is not a substitute for reviewing the full Article guidance before publishing.

FAQPage: describe visible questions and answers

Use FAQPage only when the questions and answers are visible on the page. Google has deprecated FAQ rich results, so do not add FAQPage markup expecting that search feature. See Google's documentation updates for the deprecation notice.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the return policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Returns are accepted within the stated return period."
      }
    }
  ]
}
</script>
Enter fullscreen mode Exit fullscreen mode

Replace both the question and answer with the page's actual content. The example answer is deliberately generic; it is not a return policy you should copy into a live store.

Before adding FAQPage, ask whether it describes useful content already present on the page. Do not create hidden questions just to populate the markup.

How does BreadcrumbList describe a page's location?

Use BreadcrumbList when the page has a corresponding breadcrumb trail. Google uses breadcrumb structured data to categorize page information in search results.

This example represents a trail from Home to Articles:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://example.com/"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Articles",
      "item": "https://example.com/articles/"
    }
  ]
}
</script>
Enter fullscreen mode Exit fullscreen mode

Replace the names and URLs with the real navigation path. Keep the order consistent with the breadcrumb trail shown on the page.

Do not paste this unchanged onto an individual article if its visible trail includes another step. Describe the page's actual location, rather than reusing the same example everywhere.

How do you check JSON-LD after adding it?

Check syntax, content accuracy, and search-feature eligibility separately. A minimal Schema.org example is not necessarily eligible for a Google feature.

Use this workflow:

  1. Create a starting snippet. Use the free schema markup generator, then replace the example values with information from your page.
  2. Check the markup. Use the free schema markup validator to check your JSON-LD. Fix reported errors before treating the implementation as finished.
  3. Compare it with the page. Read each name, headline, question, answer, and URL against the published content. A tool cannot make placeholder text accurate for your business.
  4. Audit the changed URL. Run Sitecheckly's free SEO and AEO audit on that page. It checks one page per run and requires no sign-up.
  5. Check Google's requirements. Use Google's Rich Results Test for supported rich-result eligibility, then review the relevant feature documentation for required properties and content rules. Google's structured data introduction explains testing and why correct markup does not guarantee display.

Keep those checks distinct. Fixing a syntax error does not prove that a page meets a feature's content requirements. Meeting the requirements does not guarantee that Google will show the feature.

What to do next

  • Choose one page and the types that genuinely describe it.
  • Replace every placeholder in the relevant snippets.
  • Publish, validate, and check the exact URL you changed.

Frequently asked questions

Do I need to add all five types to every page?

No. Choose types that describe the page and its actual content. For example, an article type is not appropriate for a page that is not an article.

Can a page contain more than one JSON-LD type?

Yes. A page can describe multiple relevant entities, such as an article and its breadcrumb trail. Each description should match the page.

Does valid JSON-LD guarantee a rich result?

No. Valid syntax does not guarantee that a page meets a search feature's requirements or that the feature will appear.

Will structured data guarantee a citation in an AI answer?

No. Structured data can describe content, but adding it does not guarantee an AI answer citation.


Want to see how your own site does? Run a free audit at sitecheckly.com.

Figures in this article come from Sitecheckly's own audit data; see the methodology.

Top comments (0)