Has JSON-LD PrimaryCare

RankGear’s Has JSON-LD PrimaryCare factor returns 1 when it finds an @type of PrimaryCare in your page’s raw HTML, and 0 when it does not. It is a pattern match on source text, not a validation of your structured-data graph — a matching string that sits outside valid JSON-LD still reads as present.

What it measures

This factor reports whether RankGear finds an @type value of PrimaryCare in your page’s raw source. PrimaryCare is the Schema.org medical-business type for a primary-care practice, so its presence signals that a page is describing a general practitioner or family-medicine service in machine-readable form. The check is binary: it records that the type appears, not whether the surrounding markup is complete or correct.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "PrimaryCare", 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. If a match 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": "PrimaryCare",
  "name": "Cedar Family Medicine",
  "address": { "@type": "PostalAddress", "streetAddress": "..." },
  "telephone": "+1-555-0100"
}
</script>

// Also matches the prefixed form:  "@type": "schema:PrimaryCare"

How to optimize it

Use PrimaryCare only for a genuine primary-care medical service, with accurate practitioners, credentials, services, location, and contact information. Every property in the markup should reflect content a visitor can verify on the page itself. Treat a returned 1 as confirmation that the type is present in your source, not as a target to hit for its own sake — adding the string without the practice it describes helps no one and can misrepresent the page.

Important considerations

• The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
• A matching string that sits outside valid JSON-LD — in a comment, an example, 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 with a dedicated schema validator; this factor confirms presence, not correctness.
• This is a correlation-based prioritization signal within a measured result set. Presence of the type relates to position; it does not by itself make a page rank or guarantee any result.

Related factors

• Has JSON-LD Podiatric
• Has JSON-LD Product

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