This factor reports whether the page’s raw HTML contains a JSON-LD @type of PublicationVolume, returning 1 when the string is present and 0 when it is not. It is a text match on the source, not a validation of the structured-data graph, so a match alone does not prove the markup is valid or complete.
| Factor ID | RG-SCJ-215 |
|---|---|
| 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 PublicationVolume in the raw source. PublicationVolume is the schema.org type that describes a single volume of a periodical — a journal, magazine, or serial — typically carrying a volume number, publication dates, publisher, and the issues it contains. The factor is a simple present-or-absent signal: it does not score how complete or accurate that markup is.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "PublicationVolume", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-sensitive, so the exact capitalization PublicationVolume must appear. If any matching occurrence is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "PublicationVolume"
"@type":"schema:PublicationVolume"| Value | Meaning |
|---|---|
| 1 | The PublicationVolume type string was found in the raw HTML. |
| 0 | No matching PublicationVolume type string was found. |
How to optimize it
Use PublicationVolume only for a genuine publication volume, with an accurate volume number, dates, publisher, issues, and identifiers. Ensure every property reflects content a reader can verify on the page. Treat this factor as an observation of what your markup contains rather than a target to hit — adding the type string to a page that is not actually a periodical volume misrepresents the content and does nothing useful. Where the type genuinely applies, its presence within valid, complete JSON-LD is what matters, not the string on its own.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a return of 1 confirms only that the string exists, not that the markup is well-formed.
- A matching string that appears outside valid JSON-LD — in a comment, an example, or unrelated text — can still produce a 1.
- The source must use the exact capitalization
PublicationVolumeto match; a differently-cased variant will read as absent. - Validate the complete structured data independently with a schema testing tool before relying on it.
- This is a correlation-based prioritization signal within a measured result set. Its presence relates to how pages in that set are structured; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.