TextDigitalDocument

TextDigitalDocument is a direct DigitalDocument subtype for long-form text documents — .docx, .pages, .odt, Google Docs. No unique properties.

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

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

schema.org/TextDigitalDocument

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TextDigitalDocument",
  "name": "Xoo Code Shop — Employee Handbook 2026",
  "author": { "@type": "Organization", "name": "Xoo Code Shop HR" },
  "encodingFormat": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
  "contentUrl": "https://xoocode.com/internal/handbook-2026.docx",
  "dateModified": "2026-01-15",
  "version": "2026.1"
}
</script>

Minimal valid version

The smallest markup that still produces a valid TextDigitalDocument 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/TextDigitalDocument (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TextDigitalDocument",
  "name": "Employee Handbook 2026"
}
</script>

Google rich results this unlocks

TextDigitalDocument is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). TextDigitalDocument becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

Common TextDigitalDocument 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.