This factor reports whether RankGear finds a JSON-LD @type of Newspaper in a page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — a text match on the source, not a validation of the underlying structured-data graph.
| Factor ID | RG-SCJ-174 |
|---|---|
| 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 Newspaper in the page’s raw source. It is a presence signal for the schema.org Newspaper type — the markup a genuine newspaper publication uses to declare itself to search engines and other consumers of structured data. The result is binary: the type is either detected in the source or it is not.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Newspaper", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so capitalization differences in the property or its value do not change the outcome. Any match yields 1; no match yields 0.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Newspaper",
"name": "The Example Daily",
"publisher": { "@type": "Organization", "name": "Example Media" }
}
</script>| Value | Meaning |
|---|---|
| 1 | A @type of Newspaper (optionally prefixed schema:) was found in the raw source. |
| 0 | No such @type string was found. |
How to optimize it
Declare Newspaper only for a genuine newspaper publication, and only when every property reflects content users can verify on the page. Populate the schema with an accurate publisher, edition, coverage area, identifiers, publishing schedule, and official access details. Treat this factor as a check that the markup you intend to ship is actually present in the source — not as a target to chase. Adding the type to a page that is not a newspaper misrepresents the content and offers no real benefit.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a complete JSON-LD graph.
- A matching string that sits outside valid JSON-LD — in a comment, an example block, or malformed markup — can still produce 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently; a 1 here confirms the string is present, not that the schema is correct or eligible for rich results.
- This is a prioritization signal that relates to position within a measured result set. It does not, on its own, cause a page to rank — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.