XooCode(){

WPFooter

WPFooter is a direct WebPageElement subtype for a page's footer region. No unique properties.

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

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

schema.org/WPFooter
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WPFooter",
  "name": "Xoo Code site footer",
  "cssSelector": "footer.site-footer"
}
</script>

Minimal valid version

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

Google rich results this unlocks

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

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

    Article footer vs page footer

    Wrong
    WPFooter on an article's byline/author block
    Right
    WPFooter is the page footer; article footers belong on Article structured data

    Keep region-level and content-level separate.

Schema properties in this example

About the example data

The xoocode.com site footer.

Comments

Loading comments...

Leave a comment