About Us Page Schema Reference

Scenario 1: “About Us” Page Focused on the Organization/Business

This is the most common structure for an “About Us” page. The page describes the company, its history, mission, values, and possibly features key team members.

• WebPage: Describes the “About Us” page itself.
  • @type: WebPage
  • @id: [About Us Page URL]#webpage (e.g., https://www.example.com/about/#webpage)
  • url: [About Us Page URL] (e.g., https://www.example.com/about/)
  • name: “About [Your Company Name]” (e.g., “About Example Company”)
  • description: A meta description summarizing the “About Us” page content.
  • isPartOf: { "@type": "WebSite", "@id": "[Homepage URL]#website" } (Links to the WebSite schema)
  • publisher: { "@type": "Organization", "@id": "[Homepage URL]#organization" } (Links to the Organization schema)
  • mainEntity: { "@type": "Organization", "@id": "[Homepage URL]#organization" } (Crucially Important: This tells Google the page is primarily about the organization.)
  • Breadcrumb: Correct breadcrumb for navigation.
• Organization: Describes the business/organization. This is the primary schema type for this scenario.
  • @type: Organization (or LocalBusiness if it’s a single-location business and this page includes the location details – see notes below)
  • @id: [Homepage URL]#organization (This should be the same @id used for the Organization schema on your homepage. Consistency is key.)
  • url: [Homepage URL] (It’s generally best to use the homepage URL for the main Organization schema, even on the “About Us” page. This reinforces the connection.)
  • name: [Your Company Name] (The official business name)
  • description: A concise description of your organization. This can be the same as, or different from, the description in your homepage’s Organization schema.
  • logo: (With nested ImageObject, including URL, width, height)
  • image: (With nested ImageObject, including URL, width, height)
  • address: (If applicable – using PostalAddress schema)
  • telephone: (Your business phone number)
  • email: (Your business email address)
  • sameAs: (URLs of your business’s social media profiles, Google Business Profile, etc.)
  • aggregateRating: (Optional, only if based on verifiable aggregate reviews)
  • foundingDate: (Optional) The date the organization was founded (YYYY-MM-DD format).
  • founder: (Optional) If you want to highlight the founder(s), use the founder property to link to Person schema(s) for each founder.
  • employee: (Optional) If you feature key team members on the “About Us” page, use the employee property to link to their Person schemas (see below).
  • contactPoint: (Optional) If you have specific contact information for different departments.
• Person (Optional, but Recommended if Featuring Individuals):
  • If your “About Us” page includes detailed information about specific people (founders, team members, etc.), include a separate Person schema for each person.
  • @type: Person
  • @id: [About Us Page URL]#person-[person's name] (e.g., https://www.example.com/about/#person-jane-doe – create a unique ID for each person)
  • name: [Person's Full Name]
  • jobTitle: [Person's Job Title]
  • description: A brief bio of the person.
  • image: (URL of the person’s photo)
  • sameAs: (URLs of the person’s personal professional profiles)
  • worksFor: { "@type": "Organization", "@id": "[Homepage URL]#organization" } (Links the Person to the Organization)
  • … other relevant Person properties …
  • Linking Person to Organization: Within the Organization schema, use the employee property (or founder, member, etc., as appropriate) to link to the @id values of the individual Person schemas. This creates the connection.
• Website: Referencing the website.
• Breadcrumb Correct breadcrumb for the page.

Scenario 2: “About Us” Page Focused on a Single Person (Personal Website/Solo Professional):

This is for websites where the “About Us” page is essentially a personal profile.

• WebPage: Describes the page.
  • mainEntity: Should point to the Person schema. This indicates the page is primarily about the individual.
  • isPartOf: Should point to the WebSite schema.
  • publisher: Should point to the Person schema.
  • Breadcrumb: Add accurate breadcrumb schema.
• Person: Describes the individual. This is the primary schema type.
  • Include all relevant properties: name, jobTitle, description, image, sameAs, worksFor (if applicable), knowsAbout, etc.
• Organization (Optional):
  • If the person is affiliated with an organization, you can also include an Organization schema.
  • Use the worksFor property within the Person schema to link to the Organization.
• Website included.
• Breadcrumb included.

Key Differences Between the Scenarios:

• mainEntity: In Scenario 1 (organization focus), mainEntity of WebPage points to Organization. In Scenario 2 (person focus), mainEntity points to Person.
• Primary Schema Type: In Scenario 1, Organization is the primary focus. In Scenario 2, Person is the primary focus.
• Person Role: In Scenario 1, Person is optional and used to describe featured individuals within the organization. In Scenario 2, Person is essential and describes the primary subject of the page.

Conceptual JSON-LD Example (Scenario 2 – Person Focus):

HTML

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "[About Me Page URL]#webpage",
      "url": "[About Me Page URL]",
      "name": "About [Your Name]",
      "description": "Learn more about [Your Name], [Your Profession/Title].",
       "isPartOf": {
        "@type": "WebSite",
        "@id": "[Homepage URL]#website"
      },
     "publisher": {
        "@type": "Person",
        "@id": "[About Me Page URL]#person"
      },
      "breadcrumb": {
          "@type": "BreadcrumbList",
          "@id": "[About Us Page URL]#breadcrumb",
          "itemListElement": [
            {
              "@type": "ListItem",
              "position": 1,
              "name": "Home",
              "item": "[Homepage URL]"
            },
            {
              "@type": "ListItem",
              "position": 2,
              "name": "About Us",
              "item": "[About Us Page URL]"
            }
          ]
        },
      "mainEntity": { // <-- Points to Person
        "@type": "Person",
        "@id": "[About Me Page URL]#person"
      }
    },
     {
        "@type": "WebSite",
        "@id": "[Homepage URL]#website",
        "url": "[Homepage URL]",
        "name": "[Website Name]",
          "potentialAction": {
          "@type": "SearchAction",
          "target": {
            "@type": "EntryPoint",
            "urlTemplate": "[Homepage URL]/?s={search_term_string}"
          },
          "query-input": "required name=search_term_string"
        }
    },
    {
      "@type": "Person",
      "@id": "[About Me Page URL]#person",
      "name": "[Your Full Name]",
      "url": "[About Me Page URL]",
      "givenName": "[Your First Name]",
      "familyName": "[Your Last Name]",
      "jobTitle": "[Your Profession/Title]",
      "description": "[Your Biographical Description]",
      "image": {
        "@type": "ImageObject",
        "url": "[Your Photo URL]",
        "width": [Image Width],
        "height": [Image Height],
        "caption": "Photo of [Your Name]"
      },
      "sameAs": [
        "[Your LinkedIn URL]",
        "[Your Twitter URL]",
        // ... other *personal* professional profiles ...
      ],
      "worksFor": { // Optional: If you work for/own a company
        "@type": "Organization",
        "@id": "[Organization Homepage URL]#organization"
      },
       "knowsAbout": [
        "[Area of Expertise 1]",
        "[Area of Expertise 2]",
        "[Area of Expertise 3]"
        ]
    },
    {
      "@type": "Organization", // Optional: If applicable
      "@id": "[Organization Homepage URL]#organization",
       // ... organization details
    }
  ]
}
</script>

Placeholders to Replace (Generic):

Adapt the placeholders according to whichever scenario above applies.

• [About Us Page URL] / [About Me Page URL]: The full URL of your “About Us” or “About Me” page.
• [Homepage URL]: The full URL of your website’s homepage.
• [Website Name]: The name of your website.
• [Your Company Name]: The official name of your business/organization.
• [Your Name]: Your full name (if the page is about you).
• [Your Profession/Title]: Your professional title.
• [Your Photo URL]: The URL of your photo.
• [Image Width] and [Image Height]: The dimensions (in pixels) of your photo.
• [Your LinkedIn URL], etc.: URLs of your personal professional social media profiles (for Person schema).
• [Organization Homepage URL]: The homepage URL of the organization the person works for (if applicable).
• Area of Expertise: Use relevant terms for skills.

Implementation Steps:

1. Choose Scenario: Decide whether your “About Us” page is primarily about the organization (Scenario 1) or a specific person (Scenario 2).
2. Link Entities: Use mainEntity, worksFor, publisher, and isPartOf to create the correct relationships between the schema entities.
3. Validate: Use the Google Rich Results Test.

This comprehensive, generic guide covers both common “About Us” page scenarios, providing clear schema structures and implementation guidance. Remember to tailor the placeholders and URLs to your specific website and content. The key is to choose the structure that best reflects the primary focus of your “About Us” page.