Conversation

Conversation is a CreativeWork subtype. One or more messages between organizations or people on a particular topic. Individual messages can be linked to the conversation with isPartOf or hasPart properties.

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

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

schema.org/Conversation

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Conversation",
  "name": "Example Conversation"
}
</script>

Minimal valid version

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

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Conversation",
  "name": "Example"
}
</script>

Google rich results this unlocks

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

Common Conversation 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
Using bare CreativeWork instead of the specific Conversation subtype
Wrong
```
"@type": "CreativeWork"
```
Right
```
"@type": "Conversation"
```
Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

Conversation CreativeWork

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...