This factor is a binary presence check: RankGear returns 1 when it finds an @type value of HowToSupply in a page’s raw HTML, and 0 when it does not. It confirms the string appears in source — it does not validate the surrounding JSON-LD graph.
| Factor ID | RG-SCJ-117 |
|---|---|
| Family | Structured Data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of HowToSupply in a page’s raw source. HowToSupply is the schema.org type that describes a consumable supply a reader needs to complete a documented how-to process — the materials that get used up, as distinct from the reusable tools. The check answers a single question: is that type declared anywhere in the page’s HTML?
How RankGear measures it
RankGear searches the raw HTML for the literal "@type": "HowToSupply" string, allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not change the result. A single match anywhere in source sets the factor to 1.
What RankGear looks for
"@type": "HowToSupply"
"@type":"schema:HowToSupply" ← prefix and tight spacing also match| Value | Meaning |
|---|---|
| 1 | A HowToSupply @type string was found in the raw HTML. |
| 0 | No HowToSupply @type string was found. |
How to optimize it
Use HowToSupply only for a real consumable supply that the documented process actually requires, giving it a clear name and details that are supported by the visible content on the page. Every property you declare should reflect something a reader can verify on the page itself. Because the detector matches source text rather than a validated graph, treat a score of 1 as confirmation that the string is present, not as proof that your structured data is correct — validate the complete JSON-LD independently.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to patterns within a measured result set. Presence of
HowToSupplydoes not make a page rank or guarantee a position; correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.