This factor reports whether RankGear finds an AudioObject @type declaration in a page’s raw HTML — a 1 when the schema string is present, a 0 when it is not. It is a string match on source text, not a validation that the JSON-LD graph is well-formed.
| Factor ID | RG-SCJ-019 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
The factor reports whether RankGear finds an @type value of AudioObject in the page’s raw source. AudioObject is the Schema.org type used to describe an audio file — a podcast episode, a recording, or an embedded clip — with properties such as its URL, encoding format, and duration. The result is a simple present-or-absent reading of that type declaration in the delivered HTML.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "AudioObject", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-sensitive, so the capitalization must be exact. This is a source-text pattern match rather than a parse of the JSON-LD graph, so it looks only for the declaration string and does not evaluate the surrounding object.
What RankGear looks for
"@type": "AudioObject"
"@type":"schema:AudioObject" (schema: prefix allowed)| Value | Meaning |
|---|---|
| 1 | The AudioObject type string was found in the raw HTML. |
| 0 | No matching AudioObject type string was found. |
How to optimize it
Where a page genuinely hosts audio, describe it with an AudioObject whose properties are accurate: a correct file URL, encoding format, duration, and descriptive fields that reflect the actual recording. This supports accessible, well-described audio. Add the markup because the page has real audio to describe — not to move this reading. Because the check is a case-sensitive string match, confirm the exact spelling and capitalization of "@type": "AudioObject" in the delivered source.
Important considerations
- RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph, so a well-formed graph is not required for a match.
- A matching string that sits outside a valid JSON-LD
<script>block can still produce a 1. - Capitalization must match exactly — the match is case-sensitive.
- All structured data should match visible, truthful content on the page.
- This is a prioritization signal that relates to position within a measured result set; presence of the markup correlates with, and does not cause or guarantee, any ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.