Report

Report is an Article subtype for formal reports: corporate annual reports, transparency reports, government reports, research reports, audit reports. It adds 1 property: reportNumber. All Article properties apply: headline, author, publisher, datePublished, articleBody.

The type hierarchy is Thing → CreativeWork → Article → Report. Use Report when the document is a formal report with a defined scope, methodology, and (often) a reference number. For general articles and blog posts, use Article or BlogPosting instead.

Full example of schema.org/Report json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional

schema.org/Report

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Report",
  "headline": "Xoo Code Inc. Annual Transparency Report 2025",
  "reportNumber": "XCI-TR-2025",
  "author": { "@id": "https://xoocode.com#organization" },
  "publisher": { "@id": "https://xoocode.com#organization" },
  "datePublished": "2026-02-15",
  "url": "https://xoocode.com/transparency/2025",
  "image": "https://xoocode.com/transparency/2025/cover-16x9.jpg",
  "description": "Annual disclosure of data handling practices, government data requests, structured data adoption metrics, and search visibility outcomes across customer sites.",
  "inLanguage": "en"
}
</script>

reportNumber

reportNumber is the report's reference identifier: a government report number, an internal tracking number, an ISO standard number for industry reports. It takes a Text string. Include it whenever the report has a formal identifier; readers and search engines can use it to cite the document.

Minimal valid version

The smallest markup that still produces a valid Report entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/Report (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Report",
  "headline": "Xoo Code Inc. Annual Transparency Report 2025",
  "reportNumber": "XCI-TR-2025",
  "author": { "@type": "Organization", "name": "Xoo Code Inc." },
  "datePublished": "2026-02-15"
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

Article rich resultprimary
Google docs

Common Report mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

01
Using Article for a formal report
Wrong
```
"@type": "Article" for a transparency report or annual report
```
Right
```
"@type": "Report"
```
Report signals to search engines that this is a formal document with a specific scope and methodology. Article is generic. Government, corporate, and research search features may treat Reports differently.

Schema properties in this example

Report Article CreativeWork headline reportNumber author publisher datePublished url image description inLanguage

About the example data

The Xoo Code Inc. annual transparency report, published yearly to disclose data handling practices and structured data adoption metrics across customer sites.

Comments

Loading comments...