Has JSON-LD JewelryStore

Abstract illustration of a gemstone inside code braces representing JSON-LD JewelryStore schema detection, in RankGear indigo and coral.

This factor reports whether a page’s raw HTML contains a JSON-LD @type of JewelryStore. 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 does not by itself prove the structured data is valid.

Factor IDRG-SCJ-128
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 JewelryStore in the page’s raw source. JewelryStore is a schema.org local-business subtype used to describe a jewelry retailer. The check is a simple presence test: the type is either declared in the source or it is not.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the @type declaration, allowing flexible whitespace around "@type": "JewelryStore" and optionally permitting a schema: prefix. Matching is case-insensitive, so differences in capitalization do not affect the result. If the pattern is found, the factor returns 1; otherwise it returns 0.

Back to Top

What RankGear looks for

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

How to optimize it

Use JewelryStore only for a genuine jewelry retailer, and only when the markup reflects what visitors can actually verify on the page — accurate products, offers, location, hours, service details, and contact information. Every property should describe real, on-page content. Treat this factor as an observation about whether the type is declared, not a target to game: declaring the type without the substance behind it invites the mismatch problems below rather than any benefit.

Back to Top

Important considerations

  • The detector pattern-matches source text; it does not validate a JSON-LD graph, so a returned 1 is not proof of well-formed structured data.
  • A matching string that sits outside valid JSON-LD — for example in a comment or a code sample — can still produce a 1.
  • Capitalization differences do not affect detection, since matching is case-insensitive.
  • Validate the complete structured data independently with a dedicated schema validator before relying on it.
  • Presence of this type correlates with, and does not cause, ranking position; it is a prioritization signal measured within a result set, never a guarantee of where a page ranks.
Back to Top

Related factors

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

Back to Top