ServerField Server operations and website growth
Technical SEO JSON-LD implementation Updated July 29, 2026

What is structured data?
SEO and JSON-LD implementation and validation

This practical guide covers what structured data means, the difference between Schema.org and Google Search requirements, choosing types by page, JSON-LD examples, validation, and error handling. It also explains changes from older guidance, including the FAQ rich result discontinued in 2026.

Published: January 8, 2025 Last updated: July 29, 2026 Written and reviewed by: Hikaru Ono
Illustration of the relationship between structured data and search engines

Google Search Central's published documentation was rechecked for this update on July 29, 2026.

This article is based on published Google Search Central and Schema.org specifications. It does not guarantee search display or rankings; validate implementations and continue monitoring after launch.

Structured data is markup that communicates the meaning of information on a page in a machine-readable form. Correct implementation can make a page eligible for search features such as articles, products, events, and breadcrumbs. It is not magic code that promises higher rankings or rich-result display.

The answer in 30 seconds

Use JSON-LD for information visible on the page, with types Google currently supports

First identify the page's main purpose, review Google's feature-specific guide, and generate JSON-LD from the template's authoritative data. Before launch, use the Rich Results Test and Schema Markup Validator; after launch, use URL Inspection and Search Console.

Recommended formatGoogle recommends JSON-LD; avoid maintaining separate copies of HTML values
SEO roleHelps communicate meaning and establish eligibility for search features; neither rankings nor display are guaranteed
2026 updateFAQ rich results have ended; do not reuse older examples without checking
What is structured data?Markup that communicates the meaning and relationships of page content to machines using defined vocabularies and formats
Main vocabularySchema.org. For Google Search eligibility, consult Google Search Central's feature-specific guides
Recommended formatJSON-LD. Microdata and RDFa are also supported, but avoid duplication and inconsistencies.
Common usesArticle, Breadcrumb, Product, Event, JobPosting, LocalBusiness, VideoObject, and others
Main validation toolsRich Results Test, Schema Markup Validator, and Search Console URL Inspection
Most important principleMatch structured data values to information users can verify on the page
CheckedJuly 29, 2026

What is structured data?

Ordinary HTML represents a page's structure, including headings, paragraphs, images, and links. It does not always uniquely convey whether a string is a person's name, a company, a product price, or an event date. Structured data supplements that meaning and the relationships between items in a standard form.

For an article, for example, rather than merely displaying a headline, you can explicitly identify headline, author, datePublished, dateModified and image. For a product, its name, price, availability, and seller can be separate properties.

Schema.orgA shared vocabulary for people, products, articles, organizations, and more: a broad dictionary of types and properties
JSON-LDA JSON format for structured data that is easy to separate from HTML and recommended by Google
Google Search requirementsImplementation requirements for each search feature, including required and recommended properties, quality, and supported regions
Rich resultsSearch results with richer appearance or interactions than an ordinary blue link; display is not guaranteed

Structured data and meta tags are different

title, meta name="description" and og:image are also important for search or sharing, but serve different roles from structured data. Rather than substituting one for another, output consistent values from the same authoritative data.

Page contentInformation users can see, including product prices, authors, dates, and locations
JSON-LDDescribes the same information with machine-readable types and properties and makes relationships explicit
Search systemsUse the information to understand content and assess eligible features; the search system decides actual display
Do not add information only to JSON-LD when it is absent from the page. Hidden reviews, nonexistent prices, past events, or fabricated authors can violate quality guidelines even when the JSON is technically valid.

SEO impact of structured data

Structured data does not automatically improve rankings. Its value is providing explicit clues about page content and enabling eligibility for supported search features.

1

Make meanings and relationships explicit

Connect articles with authors, products with offers, or events with venues as nodes to communicate more than plain strings.

2

Establish eligibility for supported search features

Meeting the requirements for currently supported features such as Article, Product, or Event can make a page a candidate for richer search display.

3

Help communicate titles, images, dates, and authors

For articles, specify the main image, publication date, modification date, and author. Keep the page, meta tags, and structured data consistent.

4

Potentially influence clicks in search results

If a rich result is actually shown, its visibility may change. Display varies by query and device, so measure results with Search Console.

What to expect

Support understanding and display opportunities

  • Explicit information for search engines
  • Eligibility for supported rich results
  • Detailed representation of articles, products, events, and more
  • Easier automated monitoring of template quality
What is not guaranteed

Automatic increases in rankings, display, or traffic

  • Higher rankings for a particular keyword
  • Continuous rich-result display
  • Improved click-through rates or sales
  • A substitute for thin or inaccurate content

Do AI Overviews or AI Mode need special structured data?

The approach is not to add a special Schema.org type solely for Google's AI features. As with ordinary SEO, publish original content, make it crawlable, and match structured data to visible content when using it. Structured data is a machine-readable way to share information; it cannot replace the value of the content itself.

Practical priority: Before looking for special AI tags, improve content that answers search intent, primary information, clear author and operator details, internal links, images and video, correct canonical URLs, and structured-data consistency.

Structured data developments in 2026

Old articles and plugin descriptions may recommend features that Google Search has already retired. Check separately whether a type exists in Schema.org and whether Google currently uses it for rich results.

2026.07.24

Guidance added on review transparency

Warnings about fake reviews and undisclosed incentives have been clarified. Review how ratings are collected and displayed before marking them up.

2026.07.07

Product categories and sale periods clarified for e-commerce

For merchant listings, the handling of Product.category and the use of validFrom, validThrough and priceValidUntil for sale-price periods were clarified.

2026.06.15

FAQ rich-result documentation removed

FAQ rich results stopped appearing in Google Search on May 7, 2026. FAQ content can still answer readers' questions, but reconsider adding FAQPage markup solely for Google FAQ display.

2026.03.02

Both structured data and og:image help indicate preferred images

Google clarified that it can use both Schema.org image and og:image as sources when choosing image candidates for Search and Discover.

2026.01.06

Practice problem search-feature documentation removed

In 2025, Google Search also retired features including Course info, Estimated salary, Learning video, Special announcement, and Vehicle listing. Use the current search gallery to choose features.

You do not need to remove FAQ content. What ended was Google's FAQ rich result. FAQs remain useful for answering readers, site search, and support. This page includes a visible FAQ but does not output FAQPage JSON-LD.

Choosing structured data by page

Instead of adding every available type, start with the one that best fits the page's main purpose. Check both Google's search gallery and its feature-specific guide, not only Schema.org definitions.

PageMain candidatesInformation conveyedImplementation considerations
Blog or explanatory articleArticle / BlogPosting
BreadcrumbList
Headline, author, image, published date, modified dateChange dateModified only after a substantive update
Product detail or e-commerceProduct
Offer
Product, price, currency, availability, sales termsKeep price, availability, and sale periods in sync with the page
Store or business locationLocalBusiness typesName, address, phone, opening hours, locationUse an actual location page and display current hours
EventEventDates, venue, performers, sales statusPromptly reflect cancellations, postponements, or a switch to online
Job postingJobPostingRole, employment type, location, salary, expiryManage removal, expiry, and status when recruitment ends
Video-focused pageVideoObjectName, description, thumbnail, publication date, durationThe video must be viewable as the page's main content
Q&A or forumQAPage
DiscussionForumPosting
Questions, answers, comments, votes, and similar informationDifferent from an ordinary FAQ authored by the site operator

Separate site-wide and page-specific information

Organization and WebSite can be shared as site-wide information, while articles, products, events, and similar items are generated as page-specific nodes.@id lets the graph reference the same organization, author, or webpage without treating them as separate duplicates.

Good design

Generate once from authoritative data

Use shared CMS or template data for title, URL, author, image, and dates, and output it to HTML, OGP, and JSON-LD.

Design to avoid

Plugins and theme output separately

When multiple Article or Organization nodes disagree about author, image, or canonical, interpretation can be unstable even if validation passes.

How to write JSON-LD: an example

JSON-LD is usually placed inside <script type="application/ld+json">. This example connects Article, BreadcrumbList and Organization using @graph.

Article + BreadcrumbList + Organization
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Company",
      "url": "https://example.com/",
      "logo": {
        "@type": "ImageObject",
        "url": "https://example.com/logo.png"
      }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://example.com/blog/structured-data/#breadcrumb",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://example.com/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "SEO",
          "item": "https://example.com/blog/seo/"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "Structured data",
          "item": "https://example.com/blog/structured-data/"
        }
      ]
    },
    {
      "@type": "Article",
      "@id": "https://example.com/blog/structured-data/#article",
      "mainEntityOfPage": "https://example.com/blog/structured-data/",
      "headline": "What Is Structured Data? SEO, JSON-LD, and Validation (2026)",
      "description": "A practical 2026 guide to structured data, its SEO role, JSON-LD examples, Schema.org and Google requirements, and rich-result validation and troubleshooting.",
      "image": [
        "https://example.com/images/structured-data.jpg"
      ],
      "datePublished": "2026-07-01T09:00:00+09:00",
      "dateModified": "2026-07-29T12:00:00+09:00",
      "inLanguage": "en-US",
      "author": {
        "@type": "Person",
        "name": "Hikaru Ono",
        "url": "https://example.com/authors/example-author/"
      },
      "publisher": {
        "@id": "https://example.com/#organization"
      },
      "breadcrumb": {
        "@id": "https://example.com/blog/structured-data/#breadcrumb"
      }
    }
  ]
}
</script>

Ten things to check in the example

1

@context uses Schema.org

Usually specify https://schema.org to define the vocabulary for types and properties.

2

@type should match the page's main purpose

For example, choose an Article type for an explanatory article, Product for a product, and Event for an event.

3

Use absolute URLs consistently

Use public absolute URLs for pages, images, authors, logos, and breadcrumbs, consistent with the published URL and canonical.

4

@id identifies the same entity

Assign stable identifiers to organizations and articles and reference the same entity from other nodes.

5

Use ISO 8601 dates and time zones

2026-07-29T12:00:00+09:00 illustrates a date and time with a time zone.

6

Provide an identifiable author URL

Use an author profile or similar page to help distinguish people with the same name.

7

Match the representative image to the page

Specify a high-quality image representing the article, not only a logo or unrelated decorative image.

8

Avoid unnecessary differences between headline and H1

An exact match is not an absolute requirement, but avoid differences that make them look like different articles.

9

Change dateModified only for substantive updates

Do not automatically update only the date; tie it to recorded changes in content, tables, prices, specifications, or similar information.

10

Do not invent values absent from the page

Make reviews, availability, prices, dates, and locations verifiable to users on the page.

WordPress implementation considerations

SEO plugins, themes, product plugins, and review features may each output JSON-LD. First search the generated HTML for application/ld+json and check whether the same type is output more than once.

  • Do both the theme and an SEO plugin output Article?
  • Does WooCommerce's displayed price conflict with another plugin's Offer?
  • Does the markup provide an author URL that does not exist because author archives are disabled?
  • Does cached HTML include current prices, dates, and availability?
  • Are Japanese URLs mixed with English headlines on multilingual pages?
Validate the output, not the plugin name. Even when settings appear correct, theme hooks, caching, translation, or JavaScript can change the production HTML.

How to validate structured data

Valid JSON alone is not enough. Check in stages whether it is eligible for Google's search features, valid Schema.org, accessible to Googlebot, and consistent with page content.

1

Inspect generated HTML

Read JSON-LD counts, types, URLs, dates, images, authors, and prices in production-equivalent HTML, not just source data in the template or CMS.

2

Run the Rich Results Test

Check supported search features, critical errors, warnings, and detected items. Types for retired features may no longer be detected.

3

Validate vocabulary with Schema Markup Validator

Check Schema.org types and properties generally, beyond Google's specific search features.

4

Use Search Console URL Inspection

Check whether the published URL is crawlable, the fetched HTML contains JSON-LD, and canonical, noindex, authentication, or JavaScript causes problems.

5

Review reports and search performance after launch

Track enhancement reports, indexing, search display, clicks, and queries, comparing the same periods and page groups before and after implementation.

6

Retest when templates change

Themes, plugins, product feeds, translations, and design changes can break markup, so include representative pages in CI or periodic audits.

Google-specific

Rich Results Test

Review eligibility for Google's supported rich results and feature-specific errors and warnings.

All Schema.org

Schema Markup Validator

Generally validate embedded Schema.org markup beyond Google's display features.

Common errors and fixes

SymptomLikely causeFix
Required-property errorA feature-specific required price, image, or date is missingAdd a real value to the page and markup; do not force the type when the value does not exist
Warning remainsA recommended property is missingAdd it if the information exists on the page; do not invent a value just to clear a warning
Value differs from page contentHTML and JSON-LD are manually maintained separatelyGenerate both from the same authoritative data and refresh caches
The same type appears more than onceTheme, SEO plugin, and dedicated plugin output overlapping markupAssign one owner and disable unnecessary output; explicitly connect nodes with @id when appropriate
Image cannot be fetchedRelative URL, robots restrictions, authentication, low resolution, or 404Use an accessible absolute URL and check HTTP status and image size
Outdated prices, availability, or eventsCaching, batch delays, or expired data left in placeUpdate visible content and JSON-LD together and manage expiry and status operationally
Passes testing but does not appearDisplay is not guaranteed; quality, query fit, or feature retirement may matterRecheck guidelines, the current search gallery, URL Inspection, and page quality

What not to do with structured data

Hidden information

Add content users cannot see

Do not put prices, availability, reviews, authors, or dates only in JSON-LD when they are absent from the page.

Fabricated ratings

Mark up self-created stars or fake reviews

Do not present figures as independent reviews or display incentivized reviews without appropriate disclosure.

Expired content

Leave ended events or jobs in place

Do not send search users to stale pages by failing to update end dates, availability, job deadlines, or cancellation status.

Type misuse

Use an unrelated type to target search display

Avoid markup that conflicts with the page's main purpose, such as marking an article as Product or an ordinary FAQ as QAPage.

Date-only updates

Update dateModified daily without changing content

Keep modification dates trustworthy by linking them to substantive changes and the update shown on the page.

Reliance on old requirements

Assume a retired rich result still exists

Some features, such as FAQ rich results in 2026, have ended in Google Search even though their Schema.org types still exist.

Prelaunch checklist

  • Choose a type matching the page's main purpose and review Google's current feature-specific guide
  • Match JSON-LD values to what users can verify on the page
  • Avoid material contradictions among title, H1, headline, description, canonical, and OGP
  • Use accessible absolute URLs for the page, images, logo, author, and breadcrumbs
  • Output datePublished and dateModified in ISO 8601 with time zones
  • Check for duplicate or conflicting output from themes and plugins
  • Run both Rich Results Test and Schema Markup Validator
  • Use URL Inspection to check fetched HTML, canonical, and indexability
  • Assign owners for time-sensitive values such as price, availability, hours, events, and jobs
  • Plan to revalidate representative URLs after template changes

Frequently asked questions about structured data

Will structured data improve search rankings?

Neither rankings nor rich-result display are guaranteed. Structured data helps search engines understand content and establish eligibility for supported features. Content quality, search intent, crawling, indexing, and internal links also need attention.

Should I use JSON-LD or Microdata?

For a new implementation, JSON-LD is generally practical because it is easy to separate from HTML and manage in templates. Google also recommends it. Existing Microdata or RDFa need not be removed immediately, but avoid duplicating or contradicting the same information.

Is FAQPage structured data no longer useful?

Google Search FAQ rich results ended on May 7, 2026, and related documentation was removed on June 15. Adding markup to target Google's FAQ display is therefore no longer useful. This does not remove the Schema.org vocabulary; assess separately whether another system has a clear use for it.

Can a page contain multiple structured-data items?

Yes. An article page can include Article, BreadcrumbList, Organization, and Person nodes related with @id. Do not add entities absent from the page or output multiple conflicting Article nodes.

Can I publish with warnings?

Assess critical errors and warnings separately. Adding real recommended information can improve quality, but inventing values just to clear warnings is counterproductive. Check the impact in the feature-specific guide.

Can JavaScript generate JSON-LD?

Google can render JavaScript, but you must verify the resulting DOM, HTTP status, noindex, canonical, and loading failures. Where possible, output it reliably in initial HTML; if JavaScript is needed, use URL Inspection to check what Google fetched.

Does structured data alone make AI search more likely to cite my page?

Structured data alone does not determine this. Google says its existing fundamentals continue to apply to AI search: useful original content, good page experience, crawlability, and structured data matching visible content remain important.

Does passing the Rich Results Test guarantee display?

No. Passing checks technical eligibility; actual results depend on query, device, region, quality, and feature availability. Monitor outcomes in Search Console after launch.

This FAQ is visible content for readers. Since Google Search FAQ rich results ended in 2026, this page does not output FAQPage JSON-LD.

Conclusion: accurate information architecture and ongoing operations matter

Consistency matters more than the amount of markup. Define the page's main purpose, generate JSON-LD, meta tags, and OGP from the authoritative data displayed on the page, and align with Google's currently supported features.

  • Schema.org: Shared vocabulary of types and properties
  • Google's feature-specific guides: Implementation and quality conditions for search features
  • JSON-LD: A recommended format convenient for new implementations
  • Validation: Rich Results Test, Schema Markup Validator, and URL Inspection
  • Operations: Keep prices, availability, dates, opening hours, and feature retirements current

Changes in 2026 included the end of FAQ rich results. Review Google Search Central's update history and search gallery periodically instead of freezing templates from years ago.

Author Hikaru Ono

Written and reviewed by: Hikaru Ono I work on website production and improvement using HTML, CSS, Go, WordPress, and more. This article helps implementers make decisions about template output, validation, and maintenance as well as specifications.

Official sources consulted

Website Production

Work with Finite Field
on your website

Discuss more than adding structured data: page design aligned with search intent, WordPress or Go implementation, performance, mobile support, and post-launch improvement.

Free consultation Starting with requirements WordPress and Go
  • Improve SEO, structured data, and information architecture together
  • Diagnose layout issues, duplicate markup, and performance on an existing site
  • Design templates and operating procedures that are easy to update after launch
Contact

Let's start with the challenges facing your website

It is fine if you want more search traffic but do not yet know what to fix.

We can help clarify your current challenges. Start with the 30-second assessment.