XooCode(){

EmergencyService

EmergencyService is a direct LocalBusiness subtype for emergency-response organisations — fire departments, police departments, EMS / ambulance services, coast guard stations, mountain rescue teams, search-and-rescue organisations. It has no unique properties; the classification is the signal, and it is the parent of two civic-structure subtypes:

  • FireStation: dual-inherits CivicStructure + EmergencyService, for specific fire-station buildings.
  • PoliceStation: dual-inherits CivicStructure + EmergencyService, for specific police-station buildings.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/EmergencyService
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "EmergencyService",
  "@id": "https://dunmorefire.example/#department",
  "name": "Dunmore Fire Department",
  "url": "https://dunmorefire.example",
  "description": "Municipal fire and rescue department serving the Borough of Dunmore. Engine, ladder, and rescue companies across two stations. Emergencies: dial 911.",
  "telephone": "+1-570-555-0911",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "500 East Drinker Street",
    "addressLocality": "Dunmore",
    "addressRegion": "PA",
    "postalCode": "18512",
    "addressCountry": "US"
  },
  "openingHoursSpecification": [
    { "@type": "OpeningHoursSpecification", "name": "24/7 emergency coverage", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday", "Sunday"], "opens": "00:00", "closes": "23:59" },
    { "@type": "OpeningHoursSpecification", "name": "Administrative office", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"], "opens": "09:00", "closes": "17:00" }
  ],
  "areaServed": { "@type": "City", "name": "Dunmore" },
  "parentOrganization": { "@type": "GovernmentOrganization", "name": "Borough of Dunmore" },
  "subOrganization": [
    { "@type": "FireStation", "@id": "https://dunmorefire.example/station-1", "name": "Dunmore Fire Station 1" },
    { "@type": "FireStation", "@id": "https://dunmorefire.example/station-2", "name": "Dunmore Fire Station 2" }
  ],
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Community programmes",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Free smoke-alarm installation" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Car-seat safety checks" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Fire-safety school visits" } }
    ]
  }
}
</script>

When EmergencyService is the right type

Use EmergencyService (not a subtype) for the organisation when you are not describing a single building: a fire department with multiple stations, a county EMS, a volunteer rescue squad that operates out of multiple sites. For a specific building, use FireStation or PoliceStation.

24/7 hours pattern

Publish 24/7 coverage (opens: "00:00" / closes: "23:59", seven days) as one openingHoursSpecification block, and the administrative counter window as a second block with a distinct name. Map and local-search consumers use the 24/7 signal; walk-in visitors use the counter hours.

Emergency-number safety rule

Never put the emergency number (911, 112, 999, 000, 119) in a structured telephone slot unless the listing is specifically a 911 dispatch centre. Put the non-emergency line in telephone; explain the emergency number in prose description. Misusing the structured telephone for the emergency line can cause AI assistants and dialers to route urgent calls incorrectly.

Minimal valid version

The smallest markup that still produces a valid EmergencyService 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/EmergencyService (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "EmergencyService",
  "name": "Dunmore Fire Department",
  "address": { "@type": "PostalAddress", "streetAddress": "500 East Drinker Street", "addressLocality": "Dunmore", "addressRegion": "PA" },
  "telephone": "+1-570-555-0911",
  "areaServed": { "@type": "City", "name": "Dunmore" }
}
</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.

  • Local business / emergency-service knowledge panelprimary
    Google docs

Common EmergencyService 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

    Putting 911 in telephone

    Wrong
    "telephone": "911"
    Right
    Non-emergency line in telephone; 911 explained in description

    Structured telephone slots are displayed and sometimes auto-dialled by AI assistants. Putting the emergency line in a general-contact slot causes bad routing.

  2. 02

    EmergencyService on a single building

    Wrong
    EmergencyService for one fire station
    Right
    FireStation / PoliceStation for the building; EmergencyService for the department

    The two levels serve different queries. The department answers 'who responds in my city'; the station answers 'where is the nearest station'.

  3. 03

    Missing 24/7 openingHoursSpecification

    Wrong
    Hours reflecting only the administrative counter window
    Right
    Two openingHoursSpecification blocks (24/7 + counter) with distinct name values

    Map apps read openingHours to decide whether to route calls. Empty or counter-only hours on a 24/7 service misrepresents it.

Also mentioned in 3 other examples

EmergencyService also appears in FireStation, Hospital, and PoliceStation. See the full EmergencyService schema page for every reference.

About the example data

The Dunmore Fire Department, a fictional municipal fire and rescue service operating Stations 1 and 2 and Engine 1, Ladder 1, Rescue 1.

Comments

Loading comments...

Leave a comment