Organization

The official, legally recognized name of the organization. This is the primary identifier used by search engines and knowledge graphs to disambiguate your entity from others.

• Must match the exact name used on your homepage, legal filings, and authoritative profiles
• Avoid appending taglines or location modifiers unless they are part of the legal name
• Inconsistent naming across pages creates entity fragmentation, weakening your knowledge graph presence

Example: "name": "Acme Corporation" not "Acme Corp - Best Widgets"

The canonical homepage URL of the organization. This property establishes the primary digital anchor for the entity.

• Must be an absolute URL including the protocol (https://)
• Should match the canonical URL declared in your homepage's <link rel="canonical"> tag
• Used by Google's Knowledge Graph to link structured data to the verified website

Example: "url": "https://www.acmecorp.com"

An array of URLs pointing to the organization's official profiles on authoritative external platforms. This property is critical for entity reconciliation.

• Include Wikipedia/Wikidata entries, verified social media profiles, Crunchbase, and Bloomberg profiles
• Each URL must be an exact match for the canonical profile page
• Google uses sameAs to merge entity signals across the web, strengthening your entity authority score

Example platforms:

• https://www.wikidata.org/wiki/Q12345
• https://www.linkedin.com/company/acmecorp
• https://twitter.com/acmecorp

A URL pointing to the organization's official logo image. Google uses this in knowledge panels and search result branding.

• Image must be in a supported format: JPEG, PNG, WebP, or SVG
• Minimum resolution: 112x112px; recommended: 512x512px or larger
• The logo should be clearly recognizable, not an icon or favicon
• Use an ImageObject type for richer metadata including width, height, and caption

Example:

jsonCopy
"logo": {
  "@type": "ImageObject",
  "url": "https://www.acmecorp.com/logo.png",
  "width": 512,
  "height": 512
}

Defines the organization's customer service contact information using the ContactPoint type. Essential for local SEO and trust signals.

• Specify contactType such as "customer service", "sales", or "technical support"
• Include telephone in international format: "+1-555-123-4567"
• Optionally add email, availableLanguage, and areaServed
• Multiple ContactPoint entries can be used for different departments

Example:

jsonCopy
"contactPoint": {
  "@type": "ContactPoint",
  "contactType": "customer service",
  "telephone": "+1-800-555-0199",
  "availableLanguage": ["English", "Spanish"]
}

The organization's physical or mailing address using the PostalAddress type. Required for LocalBusiness subtypes and strongly recommended for all organizations.

• Include streetAddress, addressLocality, addressRegion, postalCode, and addressCountry
• Use ISO 3166-1 alpha-2 country codes (e.g., "US", "GB", "DE")
• Consistency with Google Business Profile and other citations is critical for local entity authority

Example:

jsonCopy
"address": {
  "@type": "PostalAddress",
  "streetAddress": "123 Main Street",
  "addressLocality": "San Francisco",
  "addressRegion": "CA",
  "postalCode": "94105",
  "addressCountry": "US"
}