Has JSON-LD ServiceChannel checks whether a page’s raw HTML source contains a Schema.org ServiceChannel type declaration — a "@type": "ServiceChannel" string — returning 1 when that string is present and 0 when it is not. It pattern-matches the source text rather than parsing a JSON-LD graph, so a matching string that sits outside valid structured data can still register 1.
| Factor ID | RG-SCJ-237 |
|---|---|
| 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 ServiceChannel in a page’s raw source. It is a single presence check: either the ServiceChannel type reference appears in the measured HTML or it does not. It does not grade whether the surrounding structured data is complete, valid, or correctly nested — only that the type string is there to be found.
How RankGear measures it
RankGear searches the raw HTML for the ServiceChannel type declaration, allowing flexible whitespace around "@type": "ServiceChannel" and optionally permitting a schema: prefix on the type name. Matching is case-insensitive. A match sets the factor to 1; no match sets it to 0. Because the check runs against raw source text, the string is counted wherever it appears — inside a JSON-LD script block or anywhere else in the markup.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ServiceChannel",
"serviceType": "...",
"servicePhone": "...",
"serviceUrl": "..."
}
</script>| Value | Meaning |
|---|---|
| 1 | A "@type": "ServiceChannel" string (optionally schema:-prefixed, any capitalization) was found in the raw HTML. |
| 0 | The string was not found — the page declares no ServiceChannel type in its source. |
How to optimize it
Use ServiceChannel only for a genuine way to access a service, with an accurate channel type, phone, URL, location, language, and availability. Ensure every property reflects content users can verify on the page. Treat this factor as an observation about whether the type string happens to appear in your source rather than a target to chase: the string alone is not the goal, and adding ServiceChannel markup where no real service channel exists misrepresents the page.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so it confirms the type string is present, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or unrelated text — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- Validate the complete structured data independently with a dedicated schema testing tool.
- This is a prioritization signal correlated with position within a measured result set — presence of the type is not a cause of ranking and does not guarantee one.
Related factors
Part of the Factors reference · how RankGear measures · glossary.