This factor reports whether the page’s raw source contains a JSON-LD @type of DigitalDocument — returning 1 when the string is present and 0 when it is not. It is a text pattern match, not a validation of the surrounding schema, so a match can be reported even when the JSON-LD graph itself is malformed.
| Factor ID | RG-SCJ-073 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of DigitalDocument in the page’s raw source. DigitalDocument is the schema.org type for a genuine digital document — something a reader can open, read, or download — described with a name, author, format, URL, and access information. The factor answers a single yes/no question: does that type appear in the markup at all?
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "DigitalDocument", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the value. Matching is case-insensitive, so capitalization differences in the type name do not change the result. A match anywhere in the source returns 1; no match returns 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "DigitalDocument",
"name": "Q3 Pricing Guide",
"author": { "@type": "Organization", "name": "RankGear" },
"encodingFormat": "application/pdf",
"url": "https://example.com/guides/q3-pricing.pdf"
}
</script>| Value | Meaning |
|---|---|
| 1 | A DigitalDocument @type string was found in the raw source (case-insensitive, schema: prefix allowed). |
| 0 | No DigitalDocument @type string was found. |
How to optimize it
Use DigitalDocument only for a genuine digital document, and describe it accurately: give it a real name, author, format, URL, and access information, and keep those properties matched to the content a visitor actually sees. Treat the score as an observation about your markup rather than a target to chase — adding the type to a page that is not a document invites a mismatch between your structured data and your visible content, which is the opposite of what accurate schema is for.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD — in a comment, an example block, or broken markup — can still produce 1.
- Capitalization differences in the type name do not affect detection.
- Validate the complete structured data independently; this factor confirms only that the string is present.
- Presence relates to, and does not cause, ranking position. It is a prioritization signal measured within a result set, not a guarantee that a page will rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.