XooCode(){

Museum

Museum is a direct CivicStructure subtype. It adds no properties of its own. Use inherited Place properties and CivicStructure's openingHours.

For museum collections, pair Museum with Collection (for curated holdings) and ArchiveComponent (for individual items). Museum itself is the institution; Collection is what it holds.

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

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

schema.org/Museum
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Museum",
  "name": "Museum of Early JSON-LD",
  "description": "One-room archive-museum curating printouts, whiteboards, and screenshots from the first decade of JSON-LD practice. Open to the public Saturdays.",
  "address": { "@type": "PostalAddress", "streetAddress": "14 Riverfront Pl, Suite G1", "addressLocality": "Dunmore", "addressRegion": "PA", "postalCode": "18512", "addressCountry": "US" },
  "telephone": "+1-570-555-0266",
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4270, "longitude": -75.6318 },
  "openingHours": "Sa 11:00-16:00",
  "isAccessibleForFree": true,
  "url": "https://xoocode.com/museum"
}
</script>

Minimal valid version

The smallest markup that still produces a valid Museum 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/Museum (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Museum",
  "name": "Museum of Early JSON-LD",
  "address": { "@type": "PostalAddress", "streetAddress": "14 Riverfront Pl", "addressLocality": "Dunmore", "addressRegion": "PA", "postalCode": "18512", "addressCountry": "US" }
}
</script>

Google rich results this unlocks

Museum is a structural type. It does not produce a rich result on its own.

Its value comes from combining it with a primary type whose markup earns a rich result (Article, Product, Event, and so on). Museum becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

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

    Cramming exhibit info into Museum.description

    Wrong
    Describing current and upcoming exhibits in a single Museum.description blob
    Right
    Use ExhibitionEvent entries linked via Museum.event (or a separate events page) for each exhibit

    Exhibits are time-bounded events with their own start/end, organizer, and audience. ExhibitionEvent is the correct entity; Museum is the institution.

Schema properties in this example

MuseumCivicStructurePlacenamedescriptionaddressPostalAddressstreetAddressaddressLocalityaddressRegionpostalCodeaddressCountrytelephonegeoGeoCoordinateslatitudelongitudeopeningHoursisAccessibleForFreeurlCollectionArchiveComponent

About the example data

The "Museum of Early JSON-LD", a fictional one-room Xoo Code archive-museum open to the public on Saturdays.

Comments

Loading comments...

Leave a comment