This factor reports whether RankGear finds a JSON-LD @type of ReportageNewsArticle in the page’s raw HTML. It returns a simple present-or-absent flag (1 or 0) — and because it pattern-matches the source text rather than validating a structured-data graph, a match is a strong hint of intent, not proof of a valid schema.
| Factor ID | RG-SCJ-226 |
|---|---|
| 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 ReportageNewsArticle in the raw source of the page. ReportageNewsArticle is the schema.org type reserved for original, on-the-ground reported journalism — a first-hand news account rather than an opinion piece or generic article. The factor is a binary observation: the type string is either present in the markup or it is not.
How RankGear measures it
RankGear searches the raw HTML for the token "@type": "ReportageNewsArticle", allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. It is a text pattern match against the source, not a parse or validation of the JSON-LD graph.
What RankGear looks for
"@type": "ReportageNewsArticle"
"@type" : "schema:ReportageNewsArticle" (whitespace flexible, schema: prefix optional, case-insensitive)| Value | Meaning |
|---|---|
| 1 | The ReportageNewsArticle type string was found in the raw HTML. |
| 0 | No matching type string was found in the raw HTML. |
How to optimize it
Use ReportageNewsArticle only for a genuine reported news article — one with an accurate headline, a named reporter, a publisher, valid publish and modified dates, cited sources, images, and a real article body. Every property should reflect content a reader can verify on the page itself. Do not apply this type to opinion, marketing, or evergreen content just to trigger the flag; treat the factor as a truthful description of what the page is, not a target to game.
Important considerations
- The detector pattern-matches source text instead of validating a full JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid or complete.
- A matching string that sits outside a valid JSON-LD block — in a comment, a script example, or escaped text — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently (for example with a schema validator) rather than relying on this flag alone.
- Correlation is not causation: a present type string tracks with pages in a measured result set but does not by itself make a page rank or guarantee a position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.