Has JSON-LD Article reports whether the rendered HTML contains a JSON-LD @type declaration set to Article. It returns 1 when that pattern is found and 0 when it is not — a string-level detection, not proof that the markup is valid, complete, or eligible for any search feature.
| Factor ID | RG-SCJ-015 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Boolean (0 / 1) |
| Measured zone | Complete rendered HTML |
What it measures
Has JSON-LD Article reports whether the rendered HTML contains a JSON-LD type declaration whose value is Article. A value of 1 means RankGear found the recognized type pattern; a value of 0 means it did not. The factor detects a string pattern only. It does not validate the JSON-LD, confirm that the page is genuinely an article, inspect required or recommended properties, or guarantee a search feature.
How RankGear measures it
RankGear scans the complete rendered HTML, case-insensitively, for an @type key followed by an Article value. Optional whitespace around the separator is accepted, and RankGear also recognizes the supported schema-prefixed form. The value must match Article under this pattern. More specific types such as NewsArticle or BlogPosting have their own RankGear factors and do not automatically satisfy this exact detector.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | An @type of Article (or the schema-prefixed form) was found in the rendered HTML. |
| 0 | No Article type declaration was found. More specific subtypes like NewsArticle do not count here. |
How to optimize it
Use Article structured data when the visible page is genuinely an article and that type accurately represents it. Include appropriate properties such as headline, author, publication and modification dates, image, publisher, and canonical page identity when they are supported by the content. Keep structured data consistent with what users can see, and update it when the article changes. Choose a more specific subtype when it is a better semantic fit — and read this factor as an observation of what is present, not as a target to chase on pages where Article is not the right type.
Important considerations
- Presence does not guarantee valid or complete structured data.
- More specific article subtypes are measured separately by their own factors.
- Product, service, category, and other non-article pages should not be mislabeled as Article.
- Search engines decide eligibility and display behavior.
- Validate the deployed markup and ensure represented facts match visible content.
- This factor relates to position within a measured result set — it is a prioritization signal, not a cause of ranking, and adding it does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.