On this page:
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
Created
updated
DigitalDocument Schema for Webflow Websites
DigitalDocument schema describes digital files such as PDFs, spreadsheets, presentations, whitepapers, and other downloadable documents. It signals to search engines that a page hosts or links to a document resource rather than a standard web page. DigitalDocument is a subtype of CreativeWork.
Google does not maintain dedicated structured data documentation for DigitalDocument.
Fields in This Glossary
Not mentioned by Google
- encodingFormat — MIME type of the document (e.g., application/pdf)
Common fields (shared across types)
These fields are documented under their primary types but apply to DigitalDocument:
- name — Document title
- description — Document summary
- author — Document creator
- datePublished — Publication date
- url — Page URL where the document is hosted
Additional DigitalDocument properties (not in glossary)
hasDigitalDocumentPermission— Access permissions (read, write, comment)contentUrl— Direct download URL for the file
JSON-LD Example
{
"@context": "https://schema.org",
"@type": "DigitalDocument",
"name": "Q1 2026 Financial Report",
"description": "Quarterly financial results for Example Corp, covering revenue, operating income, and forward guidance.",
"url": "https://example.com/reports/q1-2026",
"encodingFormat": "application/pdf",
"author": {
"@type": "Organization",
"name": "Example Corp"
},
"datePublished": "2026-04-01"
}
When to Use DigitalDocument Schema
Use DigitalDocument on pages that host downloadable files: whitepapers, reports, templates, legal documents, and resource libraries. For datasets, use Dataset with DataDownload instead. For software, use SoftwareApplication.
Ask AI about this property
I just read https://www.karpi.studio/schema-glossary-types/digital-document about DigitalDocument schema for Webflow websites. Help me apply this to my own resource library:
- Minimum vs nice-to-have: `encodingFormat` (the MIME type, e.g. application/pdf) is the type-specific field; shared `name`, `description`, `author`, `datePublished`, `url` round it out
- A complete JSON-LD example using the @graph format for a DigitalDocument with `name`, `description`, `url`, `encodingFormat`, an Organization `author`, and `datePublished`
- How to implement it in a Webflow CMS template for a downloads/whitepaper collection, mapping each document's title, summary, and host URL
- How to validate it with the Schema.org Validator; there is no dedicated Google rich result for DigitalDocument, since Google maintains no structured data documentation for it
- Why `encodingFormat` is the highest-leverage field: it signals the page hosts a document resource (DigitalDocument is a subtype of CreativeWork), not a standard web page
- The most common mistake: using it for the wrong resource — use Dataset for datasets and SoftwareApplication for software