This factor reports whether RankGear finds a JSON-LD @type of Pharmacy in a page’s raw source — a simple 1 (present) or 0 (absent). It is a text-pattern check, not a validation of the structured-data graph, so a match only means the string was found, not that the markup is valid or accurate.
| Factor ID | RG-SCJ-201 |
|---|---|
| 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 Pharmacy in the raw source of the page. It answers one question: does the page declare Pharmacy structured data at all? It records presence, not correctness — the value is 1 when the pattern appears anywhere in the source and 0 when it does not.
How RankGear measures it
RankGear searches the raw HTML for the "@type": "Pharmacy" string, allowing flexible whitespace around the colon and optionally accepting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. A match anywhere in the source sets the factor to 1.
What RankGear looks for
"@type": "Pharmacy"
// also matches, e.g.:
"@type" : "pharmacy"
"@type": "schema:Pharmacy"| Value | Meaning |
|---|---|
| 1 | The Pharmacy type string was found in the raw source. |
| 0 | No matching Pharmacy type string was found. |
How to optimize it
Use the Pharmacy type only for a genuine pharmacy, and make every declared property reflect content a user can verify on the page — accurate services, credentials, location, hours, eligibility information, and contact details. Treat this factor as an observation of whether the markup is present, not a target to chase: adding the string without real, matching page content does not help, and the correct goal is honest, complete structured data for a real pharmacy.
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 or a code sample) can still produce a 1.
- Capitalization differences do not affect detection — matching is case-insensitive.
- Validate the complete structured data independently before trusting it; a 1 here is not a guarantee the markup is valid.
- This is a prioritization signal that relates to position within a measured result set. It does not cause or guarantee a ranking — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.