XooCode(){

Landform

Landform is a Place subtype for natural physical features of the earth: Mountain, Volcano, Continent, and the BodyOfWater family (Canal, LakeBodyOfWater, OceanBodyOfWater, Pond, Reservoir, RiverBodyOfWater, SeaBodyOfWater, Waterfall). It adds no properties of its own; use inherited Place properties (geo, name, description, image) plus the standard geospatial relations (geoContains, geoWithin, etc.).

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

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

schema.org/Landform
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Landform",
  "name": "Dunmore Ridge",
  "description": "A small ridge running roughly north-south along the eastern edge of Dunmore Borough, peaking at 488 metres.",
  "geo": { "@type": "GeoCoordinates", "latitude": 41.4301, "longitude": -75.6004 },
  "containedInPlace": { "@type": "AdministrativeArea", "name": "Lackawanna County, Pennsylvania" },
  "image": "https://xoocode.com/dunmore/ridge.jpg"
}
</script>

Landform vs AdministrativeArea

Landform is for natural features (the Rocky Mountains, the Great Lakes). AdministrativeArea is for political jurisdictions (Colorado, the Great Lakes Region of US Fisheries). A feature can be both: use dual typing when the natural feature has a legal/administrative identity.

Minimal valid version

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

Google rich results this unlocks

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

Common Landform 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 Landform for a park or reserve

    Wrong
    Landform for a named park
    Right
    Park (CivicStructure subtype) for parks; Landform for the underlying natural feature

    A Park is a managed human institution; the landform is the natural feature. Yosemite National Park is a Park; the Sierra Nevada is a Landform.

Schema properties in this example

LandformPlacenamedescriptiongeoGeoCoordinateslatitudelongitudecontainedInPlaceAdministrativeAreaimageMountainVolcanoContinentBodyOfWater

About the example data

Fictional "Dunmore Ridge", a small landform just outside Dunmore, PA, used as a hiking reference point and the namesake of the Dunmore Ridge Trail.

Comments

Loading comments...

Leave a comment