This factor reports whether RankGear finds a VeterinaryCare value declared as a JSON-LD @type in a page’s raw HTML. It returns a simple present/absent signal (1 or 0) — it flags that the string appears in source, not that a valid VeterinaryCare entity has been correctly modeled.
| Factor ID | RG-SCJ-263 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of VeterinaryCare in the page’s raw source. VeterinaryCare is the schema.org type used to describe a veterinary practice as a local business — its services, practitioners, hours, and contact details. The factor answers a single yes/no question: does that type declaration appear in the markup at all?
How RankGear measures it
RankGear searches the raw HTML for the @type declaration of VeterinaryCare, allowing flexible whitespace around the key and value and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so differences in capitalization do not change the result. If the pattern is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "VeterinaryCare"
// the schema-prefixed form also matches:
"@type": "schema:VeterinaryCare"| Value | Meaning |
|---|---|
| 1 | A VeterinaryCare @type string was found in the raw HTML. |
| 0 | No VeterinaryCare @type string was found in the raw HTML. |
How to optimize it
Use VeterinaryCare only for a genuine veterinary practice, and only when the markup reflects content users can verify on the page: accurate services, practitioners, credentials, species served, location, hours, and contact details. Every property should match what the page actually says. Because this factor detects a source string rather than a validated graph, treat a returned 1 as evidence the markup is present — not as confirmation that the structured data is complete or correct. Validate the full JSON-LD graph separately.
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 — for example in a comment, script, or body copy — 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 correlation-based prioritization signal within a measured result set. Presence of the type is associated with a pattern; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.