This factor reports whether RankGear finds a MedicalScholarlyArticle @type declaration in a page’s raw HTML. It returns 1 when the schema type string is present and 0 when it is not — but it pattern-matches source text rather than validating the JSON-LD graph, so a match is not proof of valid structured data.
| Factor ID | RG-SCJ-144 |
|---|---|
| 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 MedicalScholarlyArticle in a page’s raw source. It is a simple presence check: the schema type is either declared in the markup or it is not. MedicalScholarlyArticle is the schema.org type used to describe peer-reviewed medical research — a scholarly article whose subject is medicine, health, or clinical study — so its presence signals that a page has been marked up as formal medical literature rather than general health content.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "MedicalScholarlyArticle", allowing flexible whitespace around the colon and quotes and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result. If a match is found the factor is 1; otherwise it is 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "MedicalScholarlyArticle",
"headline": "...",
"author": { "@type": "Person", "name": "..." },
"citation": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A MedicalScholarlyArticle @type string was found in the raw HTML (with or without a schema: prefix, in any capitalization). |
| 0 | No MedicalScholarlyArticle @type string was found in the raw HTML. |
How to optimize it
Use MedicalScholarlyArticle only for a genuine medical scholarly article — one with accurate authorship, publication, citation, study, and evidence details. Ensure every property in the markup reflects content users can actually verify on the page. Because this factor is a presence check, treat it as an observation about how a page is described rather than a target to force: adding the type to a page that is not truly a medical scholarly article misrepresents the content and offers no genuine benefit.
Important considerations
- The detector pattern-matches source text instead of validating a complete JSON-LD graph.
- A matching string that sits outside valid JSON-LD — for example in a comment, a code sample, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a schema testing tool; this factor does not confirm the markup is well-formed.
- Presence of this type correlates with pages RankGear observes in a result set; it does not, on its own, cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.