This factor reports whether RankGear finds a Bakery @type declaration in a page’s raw rendered HTML. It returns 1 when the pattern is present and 0 when it is not — a presence signal only, since RankGear matches source text rather than validating a JSON-LD graph.
| Factor ID | RG-SCJ-028 |
|---|---|
| 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 Bakery in the raw source of the page. It is a simple present-or-absent check: the page either declares the Schema.org Bakery type somewhere in its markup, or it does not. RankGear records the result as a binary value and makes no judgment about whether the surrounding JSON-LD is otherwise complete or valid.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "Bakery", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result. If a match is found anywhere in the source, the factor is set to 1; otherwise it is 0.
What RankGear looks for
"@type": "Bakery"
"@type": "schema:Bakery"
"@TYPE": "bakery"| Value | Meaning |
|---|---|
| 1 | A Bakery @type string was found in the raw HTML. |
| 0 | No Bakery @type string was found. |
How to optimize it
Use the Bakery type for a genuine bakery, and make the structured data describe the business accurately: correct address, opening hours, contact details, menu, and ordering information. Treat the returned 1 as confirmation that the declaration exists, not as a target to chase for its own sake — the value only tells you the type string is present, not that the markup is valid or that the content behind it is trustworthy.
Important considerations
- RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph, so a present result does not confirm the structured data is well-formed.
- A matching string that sits outside a valid JSON-LD
scriptblock — for example, inside a comment or plain text — can still produce a 1. - Capitalization differences do not affect detection, since matching is case-insensitive.
- All structured data must match visible, truthful content on the page.
- Presence of this type correlates with, but does not cause, position within a measured result set; it is a prioritization signal, not a guarantee of ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.