This factor is a yes/no check for whether a ScholarlyArticle type appears in a page’s JSON-LD structured data. It returns 1 when RankGear finds the @type value ScholarlyArticle in the raw source and 0 when it does not. Because the check pattern-matches source text rather than validating a JSON-LD graph, a matching string sitting outside valid structured data can still register as 1.
| Factor ID | RG-SCJ-233 |
|---|---|
| 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 ScholarlyArticle in the page’s raw source. It is a single presence signal, not a quality score: it tells you the type declaration is there, not whether the surrounding structured data is complete or accurate.
How RankGear measures it
RankGear searches the raw HTML for the token "@type": "ScholarlyArticle", allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. A match returns 1; no match returns 0.
What RankGear looks for
"@type": "ScholarlyArticle"
"@type": "schema:ScholarlyArticle" (schema: prefix allowed)
"@type":"scholarlyarticle" (whitespace flexible, case-insensitive)| Value | Meaning |
|---|---|
| 1 | A ScholarlyArticle @type string was found in the raw source. |
| 0 | No ScholarlyArticle @type string was found. |
How to optimize it
Use ScholarlyArticle only for a genuine scholarly article, and only when the page can back it up with accurate authors, affiliations, publication, dates, an abstract, citations, and identifiers. Make sure every property reflects content a reader can verify on the page. If the content is not actually a scholarly article, forcing this type to satisfy the check misrepresents the page rather than helping it — treat a 1 here as a signal that the type is declared, not as a target to hit for its own sake.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph, so a 1 is not proof of well-formed structured data.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently rather than relying on this presence check alone.
- This is a correlation-based prioritization signal within a measured result set. Declaring
ScholarlyArticledoes not make a page rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.