Has JSON-LD Service is a yes/no check for whether a page’s rendered HTML contains a JSON-LD Service type. It returns 1 when the type string is present and 0 when it is not — but RankGear only text-matches that string; it does not parse the JSON, validate properties, or confirm the service is described correctly.
| Factor ID | RG-SCJ-236 |
|---|---|
| Family | Structured data — JSON-LD |
| Measurement | Boolean presence (0 / 1) |
| Measured zone | Complete rendered HTML |
What it measures
This factor indicates whether the rendered HTML includes a JSON-LD @type of Service or schema:Service. It is useful for comparing how pages in a result set describe an offered service as a structured entity — a page that models its service in schema versus one that only describes it in prose.
How RankGear measures it
RankGear applies a case-insensitive text pattern to the complete rendered HTML. It returns 1 when the exact quoted type is found and 0 otherwise. The detector does not parse the JSON, validate properties, or infer Service from a related or more specific type — the literal type string has to be present in the markup.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Service",
"serviceType": "Emergency plumbing",
"provider": { "@type": "LocalBusiness", "name": "..." },
"areaServed": "..."
}
</script>The match is case-insensitive and keys on the type token itself — both "@type": "Service" and the prefixed form schema:Service satisfy it.
| Value | Meaning |
|---|---|
| 1 | A JSON-LD Service (or schema:Service) type string is present in the rendered HTML. |
| 0 | No such type string was found — the page may still describe a service in prose or in a different schema type. |
How to optimize it
Use Service markup only when the page genuinely describes a real service. Connect it to the provider and add accurate properties such as service type, area served, audience, offers, or available channels when appropriate. Ensure those claims agree with the visible page and the organization’s actual operations. Treat this factor as an observation about how a page is structured, not a target to force onto pages that do not offer a service.
Important considerations
- Service markup does not itself promise a rich result.
- Do not invent service areas, pricing, or availability — keep the markup honest to the page.
- A business type and a service type can play different roles in one schema graph.
- Validate syntax and entity relationships after implementation; RankGear checks only for the type string, not correctness.
- This is a correlational signal that tracks how pages in a measured result set are structured. Its presence relates to position within that set — it does not on its own cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.