Schema field: primaryImageOfPage

What this field is: primaryImageOfPage names the single lead image that best represents a WebPage, the hero or featured image a person would point to as “the picture for this page.” It sits on the WebPage node.

Why it matters

When an engine (or a knowledge panel, or a chat answer with a thumbnail) needs one image to represent your page, primaryImageOfPage tells it which one, instead of leaving it to guess between your logo, a stock icon, and an ad. It disambiguates the visual the same way a headline disambiguates the text. On article and product pages especially, a clearly declared primary image improves how your content is presented when it is surfaced.

How to fill it

Point it at your page’s real lead image. Two accepted forms:

Simplest, a URL:

{
  "@type": "WebPage",
  "url": "https://example.com/guide",
  "primaryImageOfPage": "https://example.com/img/guide-hero.jpg"
}

Better, an ImageObject with dimensions (gives engines width and height up front):

"primaryImageOfPage": {
  "@type": "ImageObject",
  "url": "https://example.com/img/guide-hero.jpg",
  "width": 1200,
  "height": 630
}

• Choose the actual hero or featured image of the content, not the site logo and not a decorative background.
• Use an absolute URL to the full-size image, one that returns 200 to anyone (not gated behind auth).
• Prefer the ImageObject form with width and height, ideally a large, high-resolution image (1200px wide or more works well).
• It is a WebPage property, so it belongs on your WebPage/Article node, not on the Organization node (the Organization’s image is its logo).

If you already set og:image for social sharing, the same asset is usually the right value here.