XooCode(){

PayAction

PayAction is a TradeAction subtype for payment. Property: recipient (Person / Organization / Audience / ContactPoint).

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

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

schema.org/PayAction
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PayAction",
  "agent": { "@type": "Organization", "name": "Xoo Code" },
  "recipient": { "@type": "Organization", "name": "Dunmore Foundation" },
  "price": 2500,
  "priceCurrency": "DKK"
}
</script>

Minimal valid version

The smallest markup that still produces a valid PayAction 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/PayAction (minimal)
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PayAction",
  "recipient": { "@type": "Organization", "name": "Recipient" }
}
</script>

Google rich results this unlocks

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

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

    PayAction where DonateAction fits

    Wrong
    PayAction for a charitable gift
    Right
    DonateAction for philanthropic transfers

    DonateAction captures the no-compensation semantics; PayAction is for commercial payment.

About the example data

Paying the Dunmore Foundation the Xoo Code annual donation.

Comments

Loading comments...

Leave a comment