Has JSON-LD Distillery

Abstract illustration of a distillery pot still and location pin fused with a JSON-LD code bracket, in RankGear indigo and coral.

Has JSON-LD Distillery reports whether RankGear finds a "@type": "Distillery" value in a page’s raw HTML — a binary presence check that returns 1 when the string is matched and 0 when it is not. It pattern-matches source text rather than validating the structured-data graph, so a match sitting outside valid JSON-LD can still register a 1.

Factor IDRG-SCJ-076
FamilyStructured Data – JSON-LD
MeasurementBinary presence (0 / 1)
Measured zoneRaw rendered HTML

What it measures

This factor reports whether an @type value of Distillery is present in the page’s raw source. It is a schema.org type used to describe a real distillery as a local business or place — the entity that produces spirits and often runs a tasting room, tours, and retail. The factor answers a single yes/no question: does the markup for this type appear on the page?

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "Distillery", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not affect the result. A match sets the factor to 1; no match sets it to 0.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Distillery",
  "name": "Example Distillery",
  "address": { "@type": "PostalAddress", "...": "..." }
}
</script>
ValueMeaning
1A "@type": "Distillery" string was found in the raw HTML.
0No matching string was found.
Back to Top

How to optimize it

Use the Distillery type only for a genuine distillery, and only when its structured-data properties match what the page actually shows — accurate location, hours, products, tours, and contact information. Because this is a presence signal on a specific business type, treat it as an observation about whether the page describes itself as a distillery, not as a target to chase on pages that are not one. Applying the type to an unrelated page would misrepresent the entity and adds no value.

Back to Top

Important considerations

  • The detector pattern-matches source text; it does not validate a JSON-LD graph, so it cannot confirm the structured data is well-formed or complete.
  • 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, since matching is case-insensitive.
  • Validate the complete structured data independently with a schema testing tool; a 1 here is not proof of valid, eligible markup.
  • This is a prioritization signal that relates to pages in a measured result set — presence of the type correlates with, but does not by itself cause, ranking position.
Back to Top

Related factors

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

Back to Top