Has JSON-LD PlasticSurgery

This factor reports whether RankGear finds an @type value of PlasticSurgery in the page’s raw HTML source, returning 1 when the string is present and 0 when it is not. It is a text-presence check, not a validation of the underlying JSON-LD graph, so a match confirms the schema type is written on the page — not that the structured data is correct.

What it measures

This factor reports whether RankGear finds an @type value for PlasticSurgery in the raw source. It answers a single question: does the page declare the PlasticSurgery schema type in its markup? The signal reflects presence of the type declaration only — it does not weigh how complete or accurate the surrounding structured data is.

How RankGear measures it

RankGear searches the raw HTML for "@type": "PlasticSurgery", allowing flexible whitespace around the value and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences in the type name do not change the result. If the pattern is found anywhere in the source, the factor returns 1; otherwise it returns 0.

What RankGear looks for

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PlasticSurgery",
  "name": "Example Aesthetic Surgery Clinic",
  "medicalSpecialty": "PlasticSurgery"
}
</script>

How to optimize it

Use PlasticSurgery only for a real plastic-surgery medical service, with accurate practitioners, credentials, procedures, location, and contact information. Ensure every property reflects content users can verify on the page. Because this is a text-presence check, treat a value of 1 as confirmation that the declaration exists — not as proof that the schema is valid. Validate the full structured data with an independent tool so the markup that matches here is also correct.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so it confirms the string is present but not that the schema is well-formed.
• A matching string that sits outside valid JSON-LD — in a comment, a code sample, or malformed markup — can still produce a 1.
• Capitalization differences do not affect detection, since matching is case-insensitive.
• Validate the complete structured data independently before relying on it.
• This is a prioritization signal that relates to position within a measured result set; presence of the type does not by itself cause or guarantee a ranking.

Related factors

• Has JSON-LD Place
• Has JSON-LD Play Action

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