XooCode(){

CreditCard

CreditCard is a PaymentCard subtype. A card payment method of a particular brand or name. Used to mark up a particular payment method and/or the financial product/service that supplies the card account. Commonly used values: * http://purl.org/goodrelations/v1#AmericanExpress * http://purl.

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

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

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

Minimal valid version

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

Google rich results this unlocks

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

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

    Using bare PaymentCard instead of the specific CreditCard subtype

    Wrong
    "@type": "PaymentCard"
    Right
    "@type": "CreditCard"

    Specific subtypes carry domain context consumers use; reach for the narrowest applicable type.

Schema properties in this example

About the example data

Reference entry in the Xoo Code schema.org catalogue.

Comments

Loading comments...

Leave a comment