Has JSON-LD Psychiatric

RankGear’s Has JSON-LD Psychiatric factor returns a simple yes/no for whether the page’s raw HTML contains a JSON-LD @type of Psychiatric. It is a text-pattern match on source, so a value of 1 confirms the string is present — not that the surrounding structured data forms a valid, accurate graph.

What it measures

This factor reports whether RankGear finds an @type value of Psychiatric in the page’s raw source. It is a single presence check for one specific schema.org type — the type typically used to describe a psychiatric medical service or facility — and returns 1 when that type string appears and 0 when it does not.

How RankGear measures it

RankGear searches the raw HTML for the @type assignment of Psychiatric, allowing flexible whitespace around the value and an optional schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. It matches the source text directly rather than parsing and validating a JSON-LD graph.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Psychiatric"
}
</script>

// also matches (case-insensitive, flexible whitespace, optional schema: prefix):
// "@type":"psychiatric"
// "@type": "schema:Psychiatric"

How to optimize it

Use the Psychiatric type only for a genuine psychiatric medical service, with accurate practitioners, credentials, treatments, location, and contact details. Ensure every property reflects content a user can verify on the page. This is an observation about the markup present in your source, not a target to chase — only add the type where it truthfully describes the service, and let the value follow from correct markup rather than adding the string to move the number.

Important considerations

• The detector pattern-matches source text rather than validating a JSON-LD graph, so it confirms presence, not correctness.
• A matching string that sits outside valid JSON-LD — in a comment, an example, or a script that never renders — can still return 1.
• Capitalization differences do not affect detection.
• Validate the complete structured data independently with a schema testing tool; this factor does not do that for you.
• Correlation is not causation. Presence of this type relates to position within a measured result set; it is a prioritization signal, not something that makes a page rank or guarantees a ranking.

Related factors

• Has JSON-LD ProfessionalService
• Has JSON-LD PublicationIssue

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