Has JSON-LD HowTo

Has JSON-LD HowTo reports whether a page’s raw HTML contains an @type value of HowTo: it returns 1 when RankGear finds the matching string and 0 when it does not. It is a text-pattern presence check only — a 1 confirms the string is on the page, not that a valid HowTo structured-data graph is present.

Factor IDRG-SCJ-113
FamilyStructured data — JSON-LD
MeasurementBoolean (0 / 1)
Measured zoneRaw rendered HTML

What it measures

Has JSON-LD HowTo reports whether RankGear finds an @type value of HowTo in the raw source. A value of 1 means the matching string was present in the HTML; a value of 0 means it was not. The factor measures the presence of that string only. It does not parse or validate the surrounding JSON-LD graph, confirm the HowTo is well-formed, or judge whether the markup reflects the page’s visible content.

How RankGear measures it

RankGear searches the raw HTML for the token "@type": "HowTo", allowing flexible whitespace around the colon and an optional schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. Finding at least one match returns 1; otherwise the value is 0. Because the check pattern-matches source text rather than validating a JSON-LD graph, a matching string that sits outside valid structured data can still produce a 1.

What RankGear looks for

<script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "HowTo",
    "name": "...",
    "step": [ ... ]
  }
</script>
ValueMeaning
1An @type of HowTo (with optional schema: prefix) was found in the raw HTML.
0No matching HowTo type string was found (the page may still carry other structured-data types, which this factor does not count).

How to optimize it

Use HowTo only for a genuine step-by-step instructional process — one with an accurate name, ordered steps, and, where relevant, supplies, tools, timing, and supporting media. Make sure every property reflects content users can verify on the page. Because the detector matches source text rather than validating structure, treat this factor as an observation of presence, not a target to chase: adding the string without a real, well-formed HowTo graph satisfies the pattern but not the intent, and can create quality problems.

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph.
  • A matching string that sits outside valid JSON-LD can still produce a 1.
  • Capitalization differences do not affect detection; the match is case-insensitive.
  • Validate the complete structured data independently with an appropriate structured-data testing tool.
  • Presence is a signal that relates to how pages are prioritized within a measured result set — it is not a guarantee of a rich result or a ranking.

Related factors

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