XooCode(){

Waterfall

Waterfall is a direct BodyOfWater subtype for waterfalls: natural cascades, tiered falls, plunge pools. It adds no properties of its own.

Many waterfalls are tourist attractions; dual-type with TouristAttraction for the tourism layer.

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

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

schema.org/Waterfall
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": ["Waterfall", "TouristAttraction"],
  "name": "Dunmore Falls",
  "description": "A 12-metre plunge waterfall on an upper tributary of the Lackawanna River, accessible via a half-kilometre hiking trail.",
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4401, "longitude": -75.5904 },
  "containedInPlace": { "@type": "AdministrativeArea", "name": "Lackawanna County, Pennsylvania" },
  "isAccessibleForFree": true,
  "image": "https://xoocode.com/places/dunmore-falls.jpg"
}
</script>

Minimal valid version

The smallest markup that still produces a valid Waterfall 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/Waterfall (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Waterfall",
  "name": "Dunmore Falls",
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4401, "longitude": -75.5904 }
}
</script>

Google rich results this unlocks

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

Common Waterfall 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 RiverBodyOfWater for a waterfall

    Wrong
    RiverBodyOfWater for a named waterfall
    Right
    Waterfall for the falls; RiverBodyOfWater for the river it sits on

    The waterfall is a feature distinct from the river; both can coexist via containedInPlace.

Also mentioned in 1 other example

Waterfall also appears in BodyOfWater. See the full Waterfall schema page for every reference.

About the example data

Fictional "Dunmore Falls", a small plunge waterfall on a tributary of the Lackawanna River.

Comments

Loading comments...

Leave a comment