Learn about PostalAddress schema markup for location and address data.
PostalAddress schema markup provides structured data for physical addresses and locations. It defines the components of a postal address in a machine-readable format that search engines can understand and use for local search, maps integration, and business listings.
Most websites display addresses in formatted text, but without schema markup, search engines only see "some address text." PostalAddress schema tells search engines that this is a structured postal address with specific components like street address, city, and postal code.
The key insight:
PostalAddress schema transforms your address from "formatted text" into "structured location data" that enables local search features and business listings.
Enhanced visibility in local search results and Google Maps integration.
Improved business information display in search results.
Name, Address, Phone consistency across platforms.
{
"@context": "https://schema.org",
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "City Name",
"addressRegion": "State/Province",
"postalCode": "12345",
"addressCountry": "US"
}{
"@context": "https://schema.org",
"@type": "PostalAddress",
"streetAddress": "123 Business Avenue",
"addressLocality": "San Francisco",
"addressRegion": "CA",
"postalCode": "94105",
"addressCountry": "US",
"addressRegionName": "California",
"postOfficeBoxNumber": "PO Box 123"
}{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Tech Solutions Inc",
"url": "https://techsolutions.com",
"address": {
"@type": "PostalAddress",
"streetAddress": "456 Technology Blvd, Suite 200",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+1-512-555-0123",
"contactType": "customer service"
}
}Copy the schemas above to implement PostalAddress markup on your website. The first example shows standalone usage, while the second demonstrates integration with Organization schema.
Primary use case for LocalBusiness schema. Essential for Google My Business and local search results.
LocalBusiness.addressCompany headquarters and main office locations for Organization schema.
Organization.addressPhysical locations for events, conferences, and gatherings.
Event.location.addressGeographic areas where services are provided or products are delivered.
serviceArea, areaServedHandle different address formats globally:
For businesses with multiple locations:
"address": [
{
"@type": "PostalAddress",
"streetAddress": "123 Main St",
// ... primary address
},
{
"@type": "PostalAddress",
"streetAddress": "456 Branch Ave",
// ... branch address
}
]Ensure PostalAddress data matches your Google My Business listing exactly for best local SEO results.
PostalAddress enables local business rich results and location-based features.
Important Notes
Use ISO 3166-1 alpha-2 country codes for the addressCountry property:
PostalAddress schema describes physical mailing addresses and locations in a structured format. It's essential for local business listings, Google My Business integration, and location-based search features.
Include as many components as possible for accuracy. Required for LocalBusiness: streetAddress, addressLocality, postalCode, addressCountry. Other fields like addressRegion are recommended when applicable.
Always use the appropriate ISO 3166-1 alpha-2 country code for addressCountry. Address formats vary by country, but the schema properties remain the same - just fill them appropriately for each country's address format.
While PostalAddress focuses on postal components, geographic coordinates are typically included in the separate GeoCoordinates schema, often as a property of LocalBusiness or Event schemas.
Structured address data enables better local search results, Google Maps integration, and ensures your business information matches across platforms (NAP consistency).
Use our free schema validator to test your PostalAddress markup implementation.
Postaladdress schema provides structured data for postaladdress content and information. It helps search engines understand content details and enables rich results in search listings.
Essential properties vary by schema type but commonly include name, description, url, and image. For rich results, specific properties like author, datePublished, or offers may be required.
Postaladdress schema enables rich results in Google Search, increases click-through rates with enhanced listings, improves content visibility, and provides structured data that helps search engines better understand and display your content.
Use Postaladdress schema when your content matches the schema type definition. It provides semantic meaning to your data and enables enhanced search features.
Benefits include enhanced search appearances, improved click-through rates, better content understanding by search engines, and eligibility for rich result features like carousels, panels, or enhanced listings.