ReplyAction

ReplyAction is a CommunicateAction subtype. Property: resultComment (Comment).

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

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

schema.org/ReplyAction

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ReplyAction",
  "agent": { "@type": "Person", "name": "Sam Xoo" },
  "resultComment": { "@type": "Comment", "text": "The FAQPage rich result is restricted post-2023..." }
}
</script>

Minimal valid version

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

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ReplyAction",
  "resultComment": { "@type": "Comment", "text": "Reply text" }
}
</script>

Google rich results this unlocks

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

Common ReplyAction 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
ReplyAction without resultComment
Wrong
```
ReplyAction with only agent
```
Right
```
Include resultComment — it holds the reply content
```
The reply itself lives on resultComment.

ReplyAction

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

Minimal valid version

Google rich results this unlocks

Common ReplyAction mistakes

ReplyAction without resultComment

Schema properties in this example

Comments

Leave a comment