XooCode(){

Bridge

Bridge is a direct CivicStructure subtype for road, rail, and pedestrian bridges. It adds no properties of its own; use inherited Place properties (geo, name) plus CivicStructure's openingHours for toll hours or drawbridge schedules.

For bridges with unique architectural or historical significance, consider dual-typing with TouristAttraction to unlock tourism-specific properties.

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

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

schema.org/Bridge
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Bridge",
  "name": "Xoo Code Footbridge",
  "description": "Pedestrian suspension bridge crossing the Lackawanna River between downtown Dunmore and the Riverfront Residences. Opened 2025, illuminated at night, always accessible.",
  "address": { "@type": "PostalAddress", "addressLocality": "Dunmore", "addressRegion": "PA", "addressCountry": "US" },
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4273, "longitude": -75.6311 },
  "openingHours": "Mo-Su 00:00-23:59",
  "isAccessibleForFree": true
}
</script>

Minimal valid version

The smallest markup that still produces a valid Bridge 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/Bridge (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Bridge",
  "name": "Xoo Code Footbridge",
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4273, "longitude": -75.6311 }
}
</script>

Google rich results this unlocks

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

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

    Bridge without geo coordinates

    Wrong
    Bridge as a bare entity with only name
    Right
    Always populate geo so mappers and routing services can place the bridge

    A bridge's whole identity is spatial. Without geo, consumers cannot place it on a map or route across it.

Schema properties in this example

BridgeCivicStructurePlacenamedescriptionaddressPostalAddressaddressLocalityaddressRegionaddressCountrygeoGeoCoordinateslatitudelongitudeopeningHoursisAccessibleForFreeTouristAttraction

About the example data

The fictional "Xoo Code Footbridge", a pedestrian bridge crossing the Lackawanna River between downtown Dunmore and the Riverfront Residences.

Comments

Loading comments...

Leave a comment