XooCode(){

WebContent

WebContent is a pending CreativeWork subtype that serves as an umbrella for WebPage, WebSite, and WebPageElement content when the distinctions do not matter. It adds no properties of its own.

In practice, prefer the more specific types: WebPage for a single page, WebSite for a site, or the inherited CreativeWork for generic content. Use WebContent only when a mixed type bag genuinely defies classification, which is rare.

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

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

schema.org/WebContent
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebContent",
  "name": "Xoo Code archive - orphaned web content collection",
  "description": "Umbrella entity for web-addressable artefacts from the Xoo Code archive (2018-2022) that do not cleanly map to WebPage, WebSite, or WebPageElement.",
  "creator": { "@type": "Organization", "name": "Xoo Code Archive Team" },
  "datePublished": "2024-12-15",
  "url": "https://xoocode.com/archive/orphaned-web-content",
  "isAccessibleForFree": true
}
</script>

Minimal valid version

The smallest markup that still produces a valid WebContent 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/WebContent (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebContent",
  "name": "Xoo Code archive - orphaned content",
  "url": "https://xoocode.com/archive/orphaned"
}
</script>

Google rich results this unlocks

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

Common WebContent 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 WebContent when WebPage fits

    Wrong
    WebContent for a single web page
    Right
    WebPage for a single page; WebSite for a whole site; WebContent only as a deliberate umbrella

    WebContent carries no semantic benefit over WebPage for single pages. Use the specific type whenever the content fits one.

Schema properties in this example

WebContentCreativeWorknamedescriptioncreatorOrganizationdatePublishedurlisAccessibleForFreeWebPageWebSiteWebPageElement

About the example data

The umbrella entity for the Xoo Code archive's collection of orphaned web content from 2018-2022 that did not cleanly fit WebPage or WebSite.

Comments

Loading comments...

Leave a comment