XooCode(){

Church

Church is a PlaceOfWorship subtype. A church.

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

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

schema.org/Church
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Church",
  "name": "Example Church"
}
</script>

Minimal valid version

The smallest markup that still produces a valid Church 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/Church (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Church",
  "name": "Example"
}
</script>

Google rich results this unlocks

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

Common Church 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 bare PlaceOfWorship instead of the specific Church subtype

    Wrong
    "@type": "PlaceOfWorship"
    Right
    "@type": "Church"

    Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

Also mentioned in 2 other examples

Church also appears in CatholicChurch, and PlaceOfWorship. See the full Church schema page for every reference.

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...

Leave a comment