About / Team Stack
About/team pages linking organization and key people with FAQs and breadcrumb context.
When to use this stack
- About or leadership pages highlighting key people
- Company pages where FAQs clarify mission, locations, and contact
- Team hubs needing navigation and entity clarity
What is included
Declares the about/team page.
Company identity tied to the page.
Represents a featured team member.
Answers mission, location, and contact FAQs.
Provides navigation context.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- itemListElement[].name
- jobTitle
- logo
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- url
- worksFor.@id
Recommended properties
- description
- image
- itemListElement[].item
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- sameAs[]
- url
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "AboutPage",
"@id": "https://www.example.com/about#page",
"name": "About Northwind",
"url": "https://www.example.com/about",
"description": "Learn about Northwind Analytics and our leadership team."
},
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.example.com/#org",
"name": "Northwind Analytics",
"url": "https://www.example.com",
"logo": "https://www.example.com/images/logo-120x60.png"
},
{
"@context": "https://schema.org",
"@type": "Person",
"@id": "https://www.example.com/about#person",
"name": "Alex Doe",
"jobTitle": "CEO",
"url": "https://www.example.com/about#alex",
"worksFor": { "@id": "https://www.example.com/#org" }
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{ "@type": "Question", "name": "Where is the team based?", "acceptedAnswer": { "@type": "Answer", "text": "HQ in SF with remote team members across the US." } },
{ "@type": "Question", "name": "How do I contact the team?", "acceptedAnswer": { "@type": "Answer", "text": "Use the contact form or email press@example.com for media inquiries." } }
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "About", "item": "https://www.example.com/about" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Do I need Person for every leader?
Include Person objects for leaders you feature on the page. Keep worksFor pointing to the Organization.
Can I reuse the Organization object elsewhere?
Yes. Keep @id consistent across your site for the same entity.