PostalAddress schema

Where to use it

Nested inside Organization or LocalBusiness.

A complete example

Valid as written, with every required property and the recommended ones that carry real information. Shown inside its documented parent, Organization, because that is the shape a page actually ships.

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Acme Reference",
  "address": {
    "@type": "PostalAddress",
    "addressCountry": "US",
    "streetAddress": "1 Example Street",
    "addressLocality": "Austin",
    "addressRegion": "TX",
    "postalCode": "78701"
  }
}

Generate a PostalAddress node with your own values in the schema generator, and lint what your page actually ships with the schema validator.

Properties

The three mistakes this type attracts

1. 01A country name rather than an ISO 3166 code.
2. 02Publishing a home address for a solo business without intent.
3. 03Omitting postalCode where the country uses one.

Related types

• Organization
• ContactPoint
• Event
• SearchAction
• EntryPoint
• ListItem

Where this appears in the playbook

• Structured data: what each type is for and which ones earned their place.
• The schema graph: composing types into one graph with stable identifiers.
• One JSON-LD script per page, holding one @graph
• Stable @id anchors that cross-reference rather than duplicate
• Optional fields are omitted, never emitted as empty strings
• Does schema markup work? What 42 types on one site actually did: which of these types measurably did anything in production.