Skip to content
Learn Measure Blog Case studies About
On this page
  • How to mark up your content
  • Resources

Structured data is valid

May 2, 2019 — Updated Aug 21, 2019
Appears in: SEO audits
On this page
  • How to mark up your content
  • Resources

Search engines use structured data to understand what kind of content is on your page. For example, you can tell search engines that your page is an article, a job posting, or an FAQ.

Marking up your content with structured data makes it more likely that it will be included in rich search results. For example, content marked up as an article might appear in a list of top stories relevant to something the user searched for.

The Lighthouse structured data audit is manual, so it does not affect your Lighthouse SEO score.

How to mark up your content #

  1. Identify the content type that represents your content.
  2. Create the structured data markup using the reference docs for that content type.
  3. Insert the markup into each page you wish to make eligible to search engines.
  4. Run the Structured Data Linter to validate your structured data.
  5. Test how the markup works in Google Search using the Structured Data Testing Tool.

See Google's Mark Up Your Content Items page for more information.

Resources #

  • Source code for Structured data is valid audit
  • Mark Up Your Content Items
  • Structured Data Testing Tool
  • Structured Data Linter
  • Google search gallery
Last updated: Aug 21, 2019 — Improve article
Return to all articles
Share
subscribe

Contribute

  • File a bug
  • View source

Related content

  • developer.chrome.com
  • Chrome updates
  • Web Fundamentals
  • Case studies
  • Podcasts
  • Shows

Connect

  • Twitter
  • YouTube
  • Google Developers
  • Chrome
  • Firebase
  • Google Cloud Platform
  • All products
  • Terms & Privacy
  • Community Guidelines

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies.