Has Schema Article

Has Schema Article checks whether a page’s visible HTML carries the legacy Schema.org Article type URI, http://schema.org/Article, returning 1 when that exact string is present and 0 when it is not. It scans the rendered body markup with scripts removed, so Article data expressed only as bare JSON-LD types or with a modern https:// URI can read as absent even when the page is, in fact, marked up.

Factor IDRG-SCH-004
FamilySchema.org
MeasurementBinary presence (0 / 1)
Measured zoneBody HTML without scripts

What it measures

This factor detects the legacy Schema.org Article type URI within a page. It is a single presence check: either the identifier for the Article type appears in the measured markup or it does not. It does not grade the completeness or correctness of the structured data — only that the classic type reference is there to be found.

How RankGear measures it

RankGear takes the page’s body HTML with script blocks stripped out and performs a case-insensitive search for the string http://schema.org/Article. A match sets the factor to 1; no match sets it to 0. Because scripts are excluded from the measured zone, the type has to surface in the rendered body markup — for example as a microdata itemtype attribute — to be counted.

What RankGear looks for

<article itemscope itemtype="http://schema.org/Article">
  <h1 itemprop="headline">…</h1>
  <span itemprop="author">…</span>
</article>
ValueMeaning
1The string http://schema.org/Article was found in the body HTML (scripts excluded).
0The string was not found — the page may use the https:// URI, a bare JSON-LD type, a more specific subtype, or no Article markup at all.

How to optimize it

Use Article structured data on genuine editorial content, and supply accurate headline, author, publication and modification dates, and images. Treat the factor as an observation about which legacy identifier a page happens to expose rather than a target to chase: matching the exact http://schema.org/Article string is not itself the goal, and a page that uses the modern https:// URI or a valid JSON-LD equivalent can be correctly marked up while still registering 0 here.

Important considerations

  • Modern https:// URIs and bare JSON-LD types can return 0 even when the page carries valid Article structured data.
  • Required properties are not checked — the factor confirms the type reference is present, not that headline, author, dates, or images are supplied.
  • Markup must match the page: structured data should describe the actual content it annotates.
  • Choose the most specific valid subtype when appropriate (for example NewsArticle or BlogPosting), which may legitimately mean this specific check reads 0.
  • This is a prioritization signal correlated with position within a measured result set — presence of the type is not a cause of ranking and does not guarantee one.

Related factors

Part of the Factors reference · how RankGear measures · glossary.