XooCode(){

Crematorium

Crematorium is a direct CivicStructure subtype for cremation facilities. It has no unique properties, and as a Place it cannot carry organization properties such as parentOrganization or hasOfferCatalog. Dual-type it with LocalBusiness to use them:

  • openingHoursSpecification: appointment-based and service-hour windows, often narrower than operational hours.
  • hasOfferCatalog: cremation packages, witness cremation options, memorial services.
  • parentOrganization: the administering funeral home or municipal authority.
  • amenityFeature: witness viewing room, memorial chapel, urn selection, scattering garden.

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

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

Highlight legend:Required by GoogleRecommendedOptional
schema.org/Crematorium
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": ["Crematorium", "LocalBusiness"],
  "@id": "https://dunmorememorial.example/crematorium",
  "name": "Dunmore Memorial Crematorium",
  "url": "https://dunmorememorial.example/crematorium",
  "description": "On-site cremation facility operated by Dunmore Funeral Home. Witness cremation available by appointment. Scattering garden and memorial chapel on grounds.",
  "telephone": "+1-570-555-0260",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "620 Chestnut Street",
    "addressLocality": "Dunmore",
    "addressRegion": "PA",
    "postalCode": "18512",
    "addressCountry": "US"
  },
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4274, "longitude": -75.6360 },
  "publicAccess": true,
  "openingHoursSpecification": [
    { "@type": "OpeningHoursSpecification", "name": "Service and viewing hours (by appointment)", "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"], "opens": "09:00", "closes": "17:00" }
  ],
  "amenityFeature": [
    { "@type": "LocationFeatureSpecification", "name": "Witness cremation available", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Memorial chapel (seats 40)", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Scattering garden", "value": true },
    { "@type": "LocationFeatureSpecification", "name": "Wheelchair accessible", "value": true }
  ],
  "parentOrganization": { "@type": "LocalBusiness", "name": "Dunmore Funeral Home" },
  "hasOfferCatalog": {
    "@type": "OfferCatalog",
    "name": "Cremation packages",
    "itemListElement": [
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Direct cremation" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Cremation with witness" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Memorial service + cremation" } },
      { "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Scattering in the garden" } }
    ]
  }
}
</script>

Why dual-type with LocalBusiness

A crematorium that sells services is both a place and a business. ["Crematorium", "LocalBusiness"] keeps the CivicStructure meaning and adds the Organization properties. schema.org has no FuneralParlor type, so the funeral home that runs the facility goes in parentOrganization as a plain LocalBusiness.

Minimal valid version

The smallest markup that still produces a valid Crematorium 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/Crematorium (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Crematorium",
  "name": "Dunmore Memorial Crematorium",
  "address": { "@type": "PostalAddress", "streetAddress": "620 Chestnut Street", "addressLocality": "Dunmore", "addressRegion": "PA" },
  "telephone": "+1-570-555-0260"
}
</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 / civic structure knowledge panelprimary
    Google docs

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

    Cemetery instead of Crematorium

    Wrong
    Cemetery on a cremation-only facility
    Right
    Crematorium for the cremation operation; Cemetery only if there are burial plots

    The two serve different consumer intents. Mislabelling leads to wrong-service enquiries.

  2. 02

    Missing witness-cremation amenity

    Wrong
    Prose-only description of witness options
    Right
    Structured amenityFeature for witness availability

    Witness cremation is a high-sensitivity search intent; make it filterable.

  3. 03

    Inventing a FuneralParlor type

    Wrong
    "@type": "FuneralParlor"
    Right
    "@type": "LocalBusiness" for the funeral home

    schema.org has no FuneralParlor type. Validators flag unknown types and consumers drop the entity.

  4. 04

    Organization properties on a plain Crematorium

    Wrong
    "@type": "Crematorium" with parentOrganization or hasOfferCatalog
    Right
    "@type": ["Crematorium", "LocalBusiness"]

    Crematorium is a Place, not an Organization, so parentOrganization and hasOfferCatalog are not valid on it alone. Dual-typing adds them.

Schema properties in this example

CrematoriumCivicStructurePlacenameurldescriptiontelephoneaddressPostalAddressgeoGeoCoordinatespublicAccessopeningHoursSpecificationamenityFeatureLocationFeatureSpecificationparentOrganizationLocalBusinesshasOfferCatalogOfferCatalogitemListElementOfferitemOfferedService

About the example data

Dunmore Memorial Crematorium, a fictional facility attached to the Dunmore Funeral Home with a witness-cremation option.

Comments

Loading comments...

Leave a comment