VisualArtwork

VisualArtwork is a CreativeWork subtype for a work of art that is primarily visual. It adds 13 properties: artist, artEdition, artform, artMedium, artworkSurface, colorist, penciler, inker, letterer, and physical dimensions (height, width, depth, weight). Its direct subtypes are CoverArt and SequentialArt.

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

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

Highlight legend:Required by GoogleRecommendedOptional

schema.org/VisualArtwork

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VisualArtwork",
  "name": "Tag Cloud: Structured Data Pantheon",
  "artist": { "@type": "Person", "name": "Lena Vasquez" },
  "artform": "Silkscreen print",
  "artMedium": "Serigraph, 5 colours, acid-free paper",
  "artworkSurface": "300 gsm acid-free paper",
  "artEdition": "37/100",
  "dateCreated": "2026-02-14",
  "width": { "@type": "QuantitativeValue", "value": 45, "unitCode": "CMT" },
  "height": { "@type": "QuantitativeValue", "value": 60, "unitCode": "CMT" },
  "weight": { "@type": "QuantitativeValue", "value": 180, "unitCode": "GRM" },
  "locationCreated": { "@type": "Place", "name": "Xoo Code Studio, Dunmore PA" }
}
</script>

Surprising: Painting, Drawing, Sculpture are NOT under VisualArtwork

Schema.org's Painting, Drawing, and Sculpture types are direct CreativeWork subtypes, not VisualArtwork subtypes. That is a quirk of the vocabulary; VisualArtwork evolved from the comics world (CoverArt, SequentialArt) and the classical-art types predate it. For a painting that needs the art-specific property set, you can still use "@type": ["Painting", "VisualArtwork"] to get both trees.

Dimensions via QuantitativeValue

Always use QuantitativeValue with a unitCode for physical dimensions. Bare numeric height/width/weight values are ambiguous (is 180 in centimetres, inches, or millimetres?). UN/CEFACT unit codes: CMT (centimetres), INH (inches), GRM (grams), KGM (kilograms).

Minimal valid version

The smallest markup that still produces a valid VisualArtwork 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/VisualArtwork (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "VisualArtwork",
  "name": "Tag Cloud: Structured Data Pantheon",
  "artist": { "@type": "Person", "name": "Lena Vasquez" },
  "artMedium": "Serigraph"
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

No dedicated rich result
Google docs

Common VisualArtwork 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.

01
Dimensions as bare numbers or strings
Wrong
```
"height": 60 or "height": "60 cm"
```
Right
```
"height": { "@type": "QuantitativeValue", "value": 60, "unitCode": "CMT" }
```
height/width/depth/weight on VisualArtwork expect Distance or QuantitativeValue. Bare numbers carry no unit; free-form strings ('60 cm') cannot be machine-parsed reliably.

Using VisualArtwork for photographs

Wrong

VisualArtwork for a photograph

Right

Photograph (a direct CreativeWork subtype) for photographs; VisualArtwork for paintings, drawings, sculptures, and prints with art-world metadata

Photograph has its own CreativeWork lineage. VisualArtwork is for art-world works where artist/artMedium/artEdition apply.

Schema properties in this example

About the example data

A limited-edition silkscreen print from a Xoo Code merch drop, signed by artist Lena Vasquez, 45 cm wide by 60 cm tall.

Comments

Loading comments...