This factor reports whether the raw HTML of a page contains a JSON-LD @type of Thing, returning 1 when the pattern is present and 0 when it is not. Because RankGear matches source text rather than validating a structured-data graph, a match confirms only that the string exists — not that your JSON-LD is well-formed or valid.
| Factor ID | RG-SCJ-252 |
|---|---|
| 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 Thing in the raw source. Thing is the most generic type in the schema.org vocabulary — the root every other type descends from — so its presence tells you a page declares an entity at the broadest possible level rather than a specific one such as Product, Article, or Organization.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Thing", allowing flexible whitespace around the value and optionally permitting a schema: prefix. Matching is case-insensitive. The result is 1 when a match is found and 0 when it is not.
What RankGear looks for
"@type": "Thing"
"@type":"Thing" (whitespace is flexible)
"@type": "schema:Thing" (schema: prefix allowed)
Matching is case-insensitive, so "thing" also matches.| Value | Meaning |
|---|---|
| 1 | RankGear matched a @type of Thing in the raw HTML. |
| 0 | No matching Thing type string was found in the source. |
How to optimize it
Use Thing only for a genuine entity that cannot be represented more specifically, and give it an accurate name, description, image, identifier, and url. Ensure every property reflects content users can verify on the page. Where a more precise schema.org type applies, prefer it — treat a Thing match as an observation about how your markup is typed, not a target to chase for its own sake.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 is not proof of valid structured data.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or plain text — can still produce 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema validator.
- This is a prioritization signal that relates to position within a measured result set. It does not make a page rank or guarantee any ranking — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.