Has JSON-LD MedicalBusiness

Abstract illustration of a medical business emblem inside a JSON-LD code bracket, in RankGear indigo and coral.

Has JSON-LD MedicalBusiness reports whether RankGear finds a MedicalBusiness schema type declared in a page’s raw HTML, returning 1 when the string is present and 0 when it is not. It is a pattern match on source text, not a validation of the structured-data graph — so a match can register even where the surrounding JSON-LD is malformed.

Factor IDRG-SCJ-142
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 MedicalBusiness in the page’s raw source. It answers a single yes/no question: does the delivered HTML declare the MedicalBusiness schema type anywhere in its text?

Back to Top

How RankGear measures it

RankGear searches the raw HTML for the token "@type": "MedicalBusiness", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result. When the pattern is found the factor is 1; otherwise it is 0.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "MedicalBusiness",
  "name": "Riverside Family Practice",
  "medicalSpecialty": "PrimaryCare"
}
</script>
ValueMeaning
1A MedicalBusiness @type string was found in the raw HTML.
0No matching string was found in the raw HTML.
Back to Top

How to optimize it

Declare MedicalBusiness only for a genuine medical business, and make every property accurate: services, specialties, credentials, location, hours, and contact details. Ensure each value reflects content a user can verify on the page itself. Treat this factor as an observation about what your markup currently declares, not a target to chase — adding the type to a page that is not a medical business, or that cannot back the claim with visible content, does not help and can misrepresent the entity.

Back to Top

Important considerations

  • The detector pattern-matches source text rather than parsing and validating a JSON-LD graph, so a 1 confirms the string is present, not that the structured data is well-formed.
  • A matching string that sits outside valid JSON-LD — in a comment, an example, or broken markup — can still produce a 1.
  • Capitalization differences do not affect detection, because matching is case-insensitive.
  • Validate the complete structured data independently with a schema validator; this factor is not a substitute for that check.
  • Presence relates to how an entity is described within a measured result set; it is a prioritization signal, not a guarantee of ranking or a cause of it.
Back to Top

Related factors

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

Back to Top