Has JSON-LD ArtGallery

Has JSON-LD ArtGallery is a binary presence check: RankGear reports 1 when it finds an @type value of ArtGallery in a page’s raw rendered HTML, and 0 when it does not. It confirms the string is present, not that the markup forms a valid, verified JSON-LD graph.

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

What it measures

This factor reports whether RankGear finds an @type value of ArtGallery in the raw source of the page. It is one of the Schema.org local-business subtypes, used to describe a physical art gallery. The result is a simple yes/no signal about whether that type declaration appears in the served markup.

How RankGear measures it

RankGear searches the raw HTML for the token "@type": "ArtGallery", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the value. Matching is case-insensitive, so capitalization differences do not change the result. It is a text pattern match against the source, not a parse or validation of the JSON-LD graph.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ArtGallery",
  "name": "Riverside Contemporary",
  "address": { "@type": "PostalAddress", "streetAddress": "..." },
  "openingHours": "Tu-Su 10:00-18:00",
  "telephone": "+1-555-0100"
}
</script>
ValueMeaning
1An @type of ArtGallery was found in the raw HTML.
0No ArtGallery type declaration was found.

How to optimize it

Use the ArtGallery type only for a real gallery, and populate it with accurate location, hours, contact, and exhibition information. Treat this factor as an observation of whether that markup is present rather than a target to chase: adding the type to a page that is not a gallery, or that lacks matching visible content, is not the goal. Where the type genuinely applies, correct and complete detail is what makes the markup useful.

Important considerations

  • RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph.
  • A matching string that sits outside a valid JSON-LD script can still produce a 1.
  • Capitalization differences do not affect detection.
  • All structured data must match visible, truthful content on the page.
  • Correlation is not causation: this signal relates to how pages are described within a measured result set and is a prioritization signal, not something that makes a page rank or guarantees a position.

Related factors

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