PeopleAudience

PeopleAudience refines Audience when the target is defined by demographic or physical attributes: a children's toy (requiredMinAge / requiredMaxAge), an adult-only product (requiredMinAge), clothing sized for a specific range (suggestedMeasurement), a menstrual-health app (suggestedGender), a diabetes-education resource (healthCondition).

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

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

Highlight legend:Required by GoogleRecommendedOptional

schema.org/PeopleAudience

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "XooTee Junior Classic",
  "audience": {
    "@type": "PeopleAudience",
    "suggestedMinAge": 4,
    "suggestedMaxAge": 10,
    "suggestedGender": "unisex",
    "suggestedMeasurement": [
      {
        "@type": "QuantitativeValue",
        "name": "Chest",
        "minValue": 54,
        "maxValue": 74,
        "unitCode": "CMT"
      },
      {
        "@type": "QuantitativeValue",
        "name": "Height",
        "minValue": 104,
        "maxValue": 142,
        "unitCode": "CMT"
      }
    ]
  }
}
</script>

Direct properties (9)

requiredMinAge / requiredMaxAge: Integer ages that must be met (legal / safety gate).
suggestedMinAge / suggestedMaxAge: Number ages the publisher recommends (marketing signal).
suggestedAge: QuantitativeValue when the range wants minValue, maxValue, and unitCode together.
requiredGender: Text gender gate (rare; usually suggestedGender is enough).
suggestedGender: Text or GenderType (Male, Female, or free text like "unisex").
suggestedMeasurement: QuantitativeValue for body measurements (inseam, chest, shoe size).
healthCondition: MedicalCondition for content targeting a medical population.

Required vs suggested

The required / suggested split matters. A children's carseat uses requiredMaxAge (a legal gate). A "teens 13-17" novel uses suggestedMinAge / suggestedMaxAge (editorial guidance, not enforcement).

Minimal valid version

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

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "PeopleAudience",
  "suggestedMinAge": 4,
  "suggestedMaxAge": 10,
  "suggestedGender": "unisex"
}
</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 (feeds Product / SizeSpecification matching + AI targeting)
Google docs

Common PeopleAudience 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
required vs suggested age mixed up
Wrong
```
requiredMinAge for a marketing-recommended age
```
Right
```
suggestedMinAge unless there's a legal / safety gate
```
required* signals a hard gate; marketing signals belong on suggested*.
02
suggestedGender as an enum URL that doesn't fit
Wrong
```
"suggestedGender": "https://schema.org/Unisex"
```
Right
```
"suggestedGender": "unisex"
```
GenderType only has Male / Female; anything else is free text.
03
suggestedMeasurement without unitCode
Wrong
```
{ value: 160 }
```
Right
```
{ minValue: 54, maxValue: 74, unitCode: "CMT" }
```
Body measurements without unit can't be matched to buyer size filters.

Schema properties in this example

PeopleAudience Audience Product audience suggestedMinAge suggestedMaxAge suggestedGender suggestedMeasurement QuantitativeValue minValue maxValue unitCode requiredMinAge requiredMaxAge requiredGender suggestedAge healthCondition MedicalCondition

Also mentioned in 9 other examples

PeopleAudience also appears in AdultEntertainment, Casino, ChildCare, MedicalAudience, NightClub, ParentAudience, Product, Recipe, and 1 more. See the full PeopleAudience schema page for every reference.

About the example data

The XooTee Junior tee collection audience: children ages 4–10, any gender, chest 54–74 cm.

Comments

Loading comments...