This factor reports whether the page’s raw HTML contains an @type of PublicationIssue in its JSON-LD — a schema.org type for a single issue of a periodical. It returns 1 when the string is present and 0 when it is not. RankGear matches the source text; it does not validate the JSON-LD graph, so a match can occur even outside well-formed structured data.
| Factor ID | RG-SCJ-214 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
RankGear reports whether it finds an @type value of PublicationIssue in the page’s raw source. PublicationIssue is the schema.org type for one issue of a periodical — a specific numbered or dated issue of a magazine, journal, or newsletter — so a value of 1 indicates that issue-level structured data is declared somewhere in the markup.
How RankGear measures it
RankGear searches the raw HTML for the @type declaration, allowing flexible whitespace around "@type": "PublicationIssue" and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences in the type name do not change the result.
What RankGear looks for
"@type": "PublicationIssue"
"@type":"schema:PublicationIssue"| Value | Meaning |
|---|---|
| 1 | A PublicationIssue @type string is present in the raw HTML. |
| 0 | No matching @type string was found in the source. |
How to optimize it
Use PublicationIssue only for a genuine issue of a periodical, and populate it with an accurate issue number, publication date, volume, publisher, articles, and identifiers. Every property should reflect content that users can verify on the page. If your page is not an issue of a periodical, adding this type is not the goal — treat a value of 1 as a description of what the markup already declares, not a target to reach for its own sake.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so structural correctness is not checked here.
- A matching string sitting outside valid JSON-LD — in a comment, script, or body copy — can still produce a 1.
- Capitalization differences in the type name do not affect detection, because matching is case-insensitive.
- Validate the complete structured data independently with a schema testing tool to confirm it parses and is eligible for its intended use.
- This is a prioritization signal that tracks with position inside a measured result set. It relates to ranking rather than causing it, and its presence does not guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.