XooCode(){

Painting

Painting is a direct CreativeWork subtype. Counterintuitively, it is not under VisualArtwork; it predates that branch. It adds no properties of its own. Use creator, dateCreated, locationCreated, and material from CreativeWork.

If you want the full art-world property set (artEdition, artform, artMedium, height/width/depth/weight), use a dual type: "@type": ["Painting", "VisualArtwork"].

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

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

schema.org/Painting
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": ["Painting", "VisualArtwork"],
  "name": "The Scraper's Return",
  "creator": { "@type": "Person", "name": "Marcus Okwuosa" },
  "dateCreated": "1978",
  "artMedium": "Oil on canvas",
  "width": { "@type": "QuantitativeValue", "value": 120, "unitCode": "CMT" },
  "height": { "@type": "QuantitativeValue", "value": 90, "unitCode": "CMT" },
  "locationCreated": { "@type": "Place", "name": "Dunmore, PA" },
  "isAccessibleForFree": true,
  "image": "https://xoocode.com/archive/paintings/scrapers-return.jpg"
}
</script>

Minimal valid version

The smallest markup that still produces a valid Painting 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/Painting (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Painting",
  "name": "The Scraper's Return",
  "creator": { "@type": "Person", "name": "Marcus Okwuosa" },
  "dateCreated": "1978"
}
</script>

Google rich results this unlocks

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

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

    Assuming Painting inherits from VisualArtwork

    Wrong
    Using only @type Painting and expecting artEdition/artform to be valid
    Right
    Use dual @type [Painting, VisualArtwork] when you need the art-specific property set

    Painting in schema.org is a direct CreativeWork subtype, so the VisualArtwork property set (artEdition, artform, artMedium) is technically not on its schema. Dual typing is the clean fix.

Schema properties in this example

PaintingVisualArtworkCreativeWorknamecreatorPersondateCreatedartMediumwidthheightQuantitativeValuevalueunitCodelocationCreatedPlaceisAccessibleForFreeimage

About the example data

A fictional Xoo Code archive painting, "The Scraper's Return", oil on canvas by Dunmore-based artist Marcus Okwuosa, 1978.

Comments

Loading comments...

Leave a comment