This factor reports whether a page’s raw source contains an @type of AskPublicNewsArticle in its JSON-LD — a 1 if the string is present, a 0 if it is not. It is a text-pattern check, not a validation of the JSON-LD graph, so a match only tells you the markup string appears, not that it is well-formed.
| Factor ID | RG-SCJ-016 |
|---|---|
| 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 AskPublicNewsArticle in the page’s raw source. AskPublicNewsArticle is a schema.org type for news coverage of a public question, so this factor tells you, at a glance, whether that specific markup is declared on the page.
How RankGear measures it
RankGear searches the raw HTML for "@type": "AskPublicNewsArticle", allowing flexible whitespace around the punctuation and optionally a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not change the result. The check returns 1 when the pattern is found anywhere in the source and 0 when it is not.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AskPublicNewsArticle",
"headline": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | The AskPublicNewsArticle type string was found in the raw source. |
| 0 | No matching type string was found. |
How to optimize it
Use AskPublicNewsArticle only for genuine public-question news coverage that carries accurate editorial metadata. Do not add the markup to force a 1 on pages that are not this content type — treat the value as an observation about what the page declares, not a target to chase. If the page truly is public-question news coverage, declaring the type in valid JSON-LD is the correct way to earn the 1.
Important considerations
- RankGear pattern-matches the source text rather than parsing or validating a JSON-LD graph, so a 1 confirms the string is present, not that the markup is valid.
- A matching string that sits outside a valid JSON-LD script — for example in a comment or a code sample — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- All structured data must match visible, truthful content on the page.
- This is a prioritization signal that relates to position within a measured result set. Correlation is not causation — the presence of this markup does not by itself cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.