Has JSON-LD BroadcastService reports whether a page’s raw HTML contains a BroadcastService @type declaration: it returns 1 when RankGear matches the expected string and 0 when it does not. It is a text-pattern presence check only — a 1 does not mean the JSON-LD is valid, complete, or that a real broadcast service is described.
| Factor ID | RG-SCJ-041 |
|---|---|
| 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 BroadcastService in the raw source of the page. A value of 1 means the expected string was present; a value of 0 means it was not. The factor measures the presence of that one text marker only. It does not parse the JSON-LD graph, confirm that the surrounding structured data is valid, check that the service’s provider, broadcast area, channel, or delivery properties are present, or judge whether the markup describes a genuine broadcast service.
How RankGear measures it
RankGear performs a case-insensitive raw-HTML search for "@type": "BroadcastService", allowing flexible whitespace around the pattern and permitting an optional schema: prefix on the type value. When a matching string is found the factor returns 1; otherwise it returns 0. Because the match is against text rather than a parsed graph, differences in capitalization do not affect detection, and the string can be matched wherever it appears in the source.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BroadcastService",
"name": "Example Radio",
"broadcastDisplayName": "EXR",
"provider": { "@type": "Organization", "name": "Example Media" }
}
</script>| Value | Meaning |
|---|---|
| 1 | The BroadcastService @type string (optionally schema:-prefixed) was found in the raw HTML. |
| 0 | No matching BroadcastService type string was found in the raw HTML. |
How to optimize it
Use BroadcastService only for a real broadcast service, and supply accurate provider, broadcast-area, channel, and delivery details. Make sure the properties you declare match the content visible on the page. Because RankGear matches text rather than validating the graph, treat this factor as an observation that the marker is present, not a target to reach by inserting the string alone — adding the type without the real, accurate service data around it produces a 1 that does not reflect a well-formed entity.
Important considerations
- RankGear pattern-matches text rather than parsing or validating the JSON-LD graph.
- A matching string that appears outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently — this factor tracks a signal that relates to how pages are prioritized within a measured result set, not a guarantee of a rich result or a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.