Has JSON-LD SelfStorage

The Has JSON-LD SelfStorage factor returns 1 when RankGear finds the @type value SelfStorage in a page’s raw HTML, and 0 when it does not. It is a text pattern match, not a validation of the underlying structured-data graph — so a matching string that sits outside valid JSON-LD still returns 1, and the result should be read as an observation, not proof of correct markup.

What it measures

This factor reports whether the page declares the SelfStorage schema type. RankGear looks for an @type value of SelfStorage in the raw source and records a simple yes/no result — 1 when the type is present, 0 when it is absent. It is one of the JSON-LD family of signals, each of which tracks the presence of a specific schema type in the markup RankGear collects.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "SelfStorage", allowing flexible whitespace around the colon and optionally a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences in the source do not change the outcome. The check runs against the raw source text rather than a parsed JSON-LD graph.

What RankGear looks for

"@type": "SelfStorage"
"@type":"schema:SelfStorage"   <!-- schema: prefix allowed -->

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SelfStorage",
  "name": "Example Self Storage"
}
</script>

How to optimize it

Use the SelfStorage type only for a genuine self-storage business, and make the markup describe the facility accurately — unit types, availability, pricing, access, location, hours, and contact details. Every property should reflect content a visitor can verify on the page. Because RankGear matches source text rather than validating the graph, treat a 1 as confirmation that the type is present, not that the structured data is complete or correct; pair it with an independent validator before relying on it.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present but not that the surrounding structured data is well-formed.
• A matching string that appears outside valid JSON-LD — in a comment, a code sample, or unrelated markup — can still produce a 1.
• Capitalization differences do not affect detection; matching is case-insensitive.
• Validate the complete structured data independently rather than relying on this single presence check.
• This is a prioritization signal that relates to position within a measured result set; presence of the type correlates with, but does not cause or guarantee, any ranking.

Related factors

• Has JSON-LD Search Action
• Has JSON-LD Service

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