Is Article Page reports whether RankGear finds at least one HTML or metadata pattern commonly associated with an article page. It returns 1 when a recognized pattern is present and 0 when none is found — a detector of implementation signals, not a judgment that the content is genuinely an article, well written, or right for the query.
| Factor ID | RG-STR-001 |
|---|---|
| Family | Page structure |
| Measurement | Boolean (0 / 1) |
| Measured zone | Rendered HTML |
What it measures
Is Article Page reports whether RankGear finds at least one of several HTML or metadata patterns commonly associated with an article page. A value of 1 means a recognized pattern was present; a value of 0 means none was found. The factor identifies implementation signals only. It does not determine whether the content is genuinely an article, well written, original, current, or appropriate for the query.
How RankGear measures it
RankGear scans the rendered HTML without regard to letter case. It returns 1 when it finds any one of the following: an article element, an article-author metadata marker, a recognized NewsArticle JSON-LD type pattern, or an Open Graph type whose content is article in one of the supported attribute orders. The checks are pattern based, so any single supported pattern is enough to produce 1. Unusual spacing or serialization can affect recognition for some metadata forms.
What RankGear looks for
<article> ... </article>
<meta property="article:author" content="...">
<script type="application/ld+json">{ "@type": "NewsArticle", ... }</script>
<meta property="og:type" content="article">| Value | Meaning |
|---|---|
| 1 | At least one recognized article pattern — an article element, an article-author marker, a NewsArticle JSON-LD type, or an og:type of article — was present in the rendered HTML. |
| 0 | No supported pattern was found. This can also happen when equivalent metadata is serialized in a form RankGear does not recognize. |
How to optimize it
For genuine editorial or informational articles, use semantic article structure and accurate metadata. Apply an article-related schema type only when the page and publisher satisfy its meaning, and ensure the structured information agrees with the visible content. For product, service, category, tool, or other non-article pages, do not change the page type merely to match a competitor value — read this factor as an observation of what a page is, not a target to chase. The correct structure should reflect what the page actually is and what users expect from it.
Important considerations
- This factor is a detector, not a recommendation that every page should be an article.
- A value of 1 does not validate structured data or guarantee search-result enhancements.
- A value of 0 can occur when equivalent metadata is serialized in an unsupported form.
- Page type should follow content purpose and search intent.
- Review schema, Open Graph, authorship, date, and content-quality factors separately.
- This factor relates to position within a measured result set — it is a prioritization signal, not a cause of ranking, and adding an article pattern does not by itself make a page rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.