XooCode(){

WPAdBlock

WPAdBlock is a direct WebPageElement subtype for a region of the page used for advertising. No unique properties; use cssSelector to identify the slot.

Explicit WPAdBlock markup helps search crawlers and AI assistants distinguish editorial content from paid placement, improving E-E-A-T / quality signalling for the surrounding article.

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

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

schema.org/WPAdBlock
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WPAdBlock",
  "name": "Inline sponsored slot",
  "cssSelector": ".ad-inline"
}
</script>

Minimal valid version

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

Google rich results this unlocks

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

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

    Sponsored content as plain article

    Wrong
    Sponsored article with no WPAdBlock or Article type distinction
    Right
    Use AdvertiserContentArticle for sponsored articles; WPAdBlock for inline ad slots

    The two surface different signals — content-level vs placement-level.

About the example data

An inline ad slot on Xoo Code Engineering posts.

Comments

Loading comments...

Leave a comment