XooCode(){

BowlingAlley

BowlingAlley is a direct SportsActivityLocation subtype for bowling centres: ten-pin, candlepin, duckpin, and boutique bowling. It adds no properties of its own.

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

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

schema.org/BowlingAlley
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BowlingAlley",
  "name": "Lackawanna Lanes",
  "description": "Twenty-four-lane bowling centre with glow bowling Friday/Saturday nights, league bowling weeknights.",
  "address": { "@type": "PostalAddress", "streetAddress": "380 Scranton Rd", "addressLocality": "Dunmore", "addressRegion": "PA", "postalCode": "18512", "addressCountry": "US" },
  "telephone": "+1-570-555-1601",
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4249, "longitude": -75.6297 },
  "openingHours": "Mo-Th 11:00-23:00, Fr-Sa 10:00-01:00, Su 11:00-22:00",
  "priceRange": "$$",
  "url": "https://xoocode.com/entertainment/lackawanna-lanes"
}
</script>

Minimal valid version

The smallest markup that still produces a valid BowlingAlley 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/BowlingAlley (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BowlingAlley",
  "name": "Lackawanna Lanes",
  "address": { "@type": "PostalAddress", "streetAddress": "380 Scranton Rd", "addressLocality": "Dunmore", "addressRegion": "PA", "postalCode": "18512", "addressCountry": "US" }
}
</script>

Google rich results this unlocks

BowlingAlley 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). BowlingAlley becomes the trunk that the primary type branches off viamainEntityorbreadcrumb. Include it on every page as the backbone of your markup.

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

    Using EntertainmentBusiness for a bowling alley

    Wrong
    EntertainmentBusiness on a bowling centre
    Right
    BowlingAlley (a SportsActivityLocation) so sport and fitness searches can find it

    Schema.org places BowlingAlley under SportsActivityLocation, not EntertainmentBusiness. The specific subtype wins both sport and entertainment query surfaces.

Schema properties in this example

BowlingAlleySportsActivityLocationLocalBusinessPlacenamedescriptionaddressPostalAddressstreetAddressaddressLocalityaddressRegionpostalCodeaddressCountrytelephonegeoGeoCoordinateslatitudelongitudeopeningHourspriceRangeurl

About the example data

"Lackawanna Lanes", a fictional 24-lane bowling centre.

Comments

Loading comments...

Leave a comment