XooCode(){

BroadcastFrequencySpecification

BroadcastFrequencySpecification describes the over-the-air coordinates of a broadcast: the MHz frequency, the modulation format (FM / AM / ATSC / DVB-T), and any digital subchannel (PBS 10.1, 10.2, 10.3). It attaches to BroadcastChannel via broadcastFrequency.

Full example of schema.org/BroadcastFrequencySpecification json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional
schema.org/BroadcastFrequencySpecification
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "RadioChannel",
  "name": "WXOO 89.5",
  "alternateName": "Dunmore Community Radio",
  "broadcastFrequency": {
    "@type": "BroadcastFrequencySpecification",
    "broadcastFrequencyValue": {
      "@type": "QuantitativeValue",
      "value": 89.5,
      "unitCode": "MHZ"
    },
    "broadcastSignalModulation": "FM"
  },
  "broadcastServiceTier": "Local",
  "inBroadcastLineup": {
    "@type": "CableOrSatelliteService",
    "name": "Lackawanna Community Broadcasting"
  }
}
</script>

Direct properties (3)

  • broadcastFrequencyValue: the center frequency as a QuantitativeValue or a bare Number in MHz.
  • broadcastSignalModulation: FM, AM, ATSC, DVB-T, ISDB-T, as QualitativeValue or Text.
  • broadcastSubChannel: digital TV subchannel identifier (10.1, 10.2).

Minimal valid version

The smallest markup that still produces a valid BroadcastFrequencySpecification entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/BroadcastFrequencySpecification (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BroadcastFrequencySpecification",
  "broadcastFrequencyValue": 89.5,
  "broadcastSignalModulation": "FM"
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

  • No dedicated rich result (feeds broadcast-lineup / station lookup)
    Google docs

Common BroadcastFrequencySpecification mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

  1. 01

    Frequency without unit

    Wrong
    "broadcastFrequencyValue": 89.5 with no MHz context
    Right
    QuantitativeValue with unitCode: "MHZ"

    The bare number could be Hz, kHz, or MHz — the unit is load-bearing.

  2. 02

    broadcastSignalModulation as lowercase

    Wrong
    "broadcastSignalModulation": "fm"
    Right
    "broadcastSignalModulation": "FM"

    Standard-compliant modulation strings are uppercase (FM / AM / ATSC).

  3. 03

    Subchannel as a range

    Wrong
    "broadcastSubChannel": "10.1-10.3"
    Right
    Separate BroadcastFrequencySpecification per subchannel

    Each subchannel is its own logical channel; collapsing them loses guide data.

Schema properties in this example

BroadcastFrequencySpecificationIntangibleRadioChannelBroadcastChannelnamealternateNamebroadcastFrequencybroadcastFrequencyValueQuantitativeValuevalueunitCodebroadcastSignalModulationbroadcastSubChannelbroadcastServiceTierinBroadcastLineupCableOrSatelliteService

About the example data

WXOO 89.5 FM — the Dunmore community radio station broadcasting at 89.5 MHz FM, with no subchannels.

Comments

Loading comments...

Leave a comment