Has JSON-LD Midwifery

Abstract illustration of a JSON-LD Midwifery schema type detected as present or absent, in RankGear indigo and coral.

Has JSON-LD Midwifery reports whether RankGear can find an @type of Midwifery in a page’s raw HTML source — a simple 1 (present) or 0 (absent). It is a text match against the source, not a validation that the surrounding JSON-LD graph is well formed.

Factor IDRG-SCJ-150
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 Midwifery in the page’s raw source. It is a presence signal for one specific structured-data type: either the string is there (1) or it is not (0). It says nothing about how much other markup the page carries, only whether this particular type appears.

Back to Top

How RankGear measures it

RankGear searches the raw HTML for "@type": "Midwifery", allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so differences in capitalization do not change the result. Because the check runs against source text rather than a parsed JSON-LD graph, any matching string in the HTML can satisfy it.

Back to Top

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Midwifery"
}
</script>
ValueMeaning
1A @type of Midwifery (optionally schema:Midwifery) was found in the raw HTML, in any capitalization.
0No matching Midwifery type string was found in the source.
Back to Top

How to optimize it

Use the Midwifery type only for a genuine midwifery service, and make every property honest: accurate services, practitioners, credentials, service area, location, and contact details. Ensure each field reflects content a visitor can verify on the page. Treat this factor as an observation of what your markup declares, not as a target to chase — adding the string without a real, matching service behind it earns you nothing and risks misrepresentation.

Back to Top

Important considerations

  • The detector pattern-matches source text; it does not validate a complete JSON-LD graph.
  • A matching string that sits outside valid JSON-LD can still produce a 1.
  • Capitalization differences do not affect detection.
  • Validate the complete structured data independently — a 1 here is not proof the markup is valid or eligible for rich results.
  • Presence of this type correlates with certain result sets; it does not by itself cause or guarantee any ranking.
Back to Top

Related factors

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

Back to Top