Has JSON-LD Florist reports whether RankGear finds an @type value of Florist in a page’s raw source. It returns 1 when the string is present and 0 when it is not — but because it pattern-matches source text rather than validating a JSON-LD graph, a match is a signal that the markup exists, not proof that it is valid.
| Factor ID | RG-SCJ-089 |
|---|---|
| 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 for Florist in the page’s raw source. It is a binary presence check: the page either carries a Florist type declaration in its markup, or it does not. The factor describes the presence of that declaration — it does not assess whether the surrounding structured data is complete or well-formed.
How RankGear measures it
RankGear searches the raw HTML for a "@type": "Florist" declaration, allowing flexible whitespace around the colon and optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. If the pattern is found anywhere in the source text the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "Florist"
"@type" : "schema:Florist" // optional schema: prefix, flexible whitespace, case-insensitive| Value | Meaning |
|---|---|
| 1 | A Florist @type string was found in the raw HTML. |
| 0 | No matching Florist @type string was found. |
How to optimize it
Use the Florist type only for a genuine florist, and back it with accurate structured data: real products, delivery area, location, hours, and ordering information, with properties that match the content a visitor can see on the page. Treat this factor as an observation of whether that markup is present, not as a target to game — emitting the string on a page that is not a florist, or where the properties contradict visible content, adds no value and risks misrepresenting the page.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is valid.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a dedicated tool before relying on it.
- Presence of this markup correlates with pages in a measured result set; it is a prioritization signal, not a guarantee of ranking or a cause of it.
Related factors
Part of the Factors reference · how RankGear measures · glossary.