Has JSON-LD InsuranceAgency

Abstract illustration of an insurance-agency schema emblem inside JSON-LD braces being scanned for presence, in RankGear indigo and coral.

This factor reports whether RankGear finds an @type value of InsuranceAgency in a page’s raw source HTML. It returns 1 when the string is present and 0 when it is not. Because it pattern-matches text rather than validating a JSON-LD graph, a match is evidence the markup exists—not proof that the structured data is valid.

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

What it measures

This factor reports whether RankGear finds an @type value for InsuranceAgency in the raw source. It is a single presence check: the InsuranceAgency type is either declared in the page’s markup or it is not.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the @type declaration "@type": "InsuranceAgency", allowing flexible whitespace around the colon and quotes and optionally permitting a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. If the pattern is found anywhere in the source text, 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": "InsuranceAgency",
  "name": "...",
  "address": { "@type": "PostalAddress", "...": "..." }
}
</script>
ValueMeaning
1An @type of InsuranceAgency was matched in the raw HTML.
0No InsuranceAgency type declaration was found in the source.
Back to Top

How to optimize it

Use InsuranceAgency only for a genuine insurance agency, and only when the page’s structured data accurately describes it—policy services, service area, licensing or regulatory details, location, hours, and contact information. Ensure every property reflects content a user can verify on the page itself. Treat the value as an observation of whether the type is declared, not a target to force onto pages that are not insurance agencies.

Back to Top

Important considerations

  • The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the markup is well-formed.
  • A matching string that sits outside valid JSON-LD—for example in a comment or an example snippet—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 validator before relying on it.
  • Correlation is not causation: this signal relates to how pages are prioritized within a measured result set; declaring the type does not by itself cause a page to rank.
Back to Top

Related factors

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

Back to Top