Has MicroData Video reports whether the Microdata attribute itemprop="video" appears in a page’s rendered body after scripts are stripped. It returns 1 when the attribute is present and 0 when it is not. The check is a text match, not a validation of the underlying Microdata item graph, so a 1 confirms the string exists — not that the markup is well-formed or eligible.
| Factor ID | RG-SCM-049 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor reports whether RankGear finds the Microdata attribute itemprop="video" in the rendered body once script elements have been removed. It is a signal that the page carries item-level Microdata associating content with a video, which some result sets tend to share — it does not measure whether that markup is valid or complete.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="video". It returns 1 when at least one match exists in the rendered body and 0 otherwise. The attribute name, equals sign, double quotes, and property value must be contiguous for the search to match.
What RankGear looks for
<div itemprop="video" itemscope itemtype="https://schema.org/VideoObject">
<meta itemprop="name" content="Product demo">
</div>| Value | Meaning |
|---|---|
| 1 | The literal string itemprop="video" was found at least once in the script-stripped body. |
| 0 | The string was not found — including cases where single quotes or extra spacing break the exact match. |
How to optimize it
Use video only as part of a genuine video that is associated with, and visible from, the marked-up entity. Keep the property value aligned with the visible content and with the vocabulary expected by its parent item type. Treat this factor as an observation about your markup, not a target to chase — adding the attribute where no real video exists misrepresents the page and does not improve the underlying content.
Important considerations
- The detector pattern-matches HTML text rather than parsing or validating a Microdata item graph.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing do not match.
- Scripts are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, property value, nesting, and structured-data eligibility independently.
- Presence relates to patterns seen within a measured result set; it is a prioritization signal, not a guarantee of ranking or a cause of it.
Related factors
Part of the Factors reference · how RankGear measures · glossary.