AboutPage Schema Markup: JSON-LD Examples

Google Search Features

No Google rich result uses AboutPage markup directly. It's still valid schema.org, and it helps search engines understand the page.

When to Use AboutPage

About pages Company information pages

Properties

Property	Type	Status	Description
name	Text	optional	Page title.
url	URL	recommended	Page URL.
mainEntity	Organization or Person	optional	The entity described.

JSON-LD Examples

About Page

About page for a company.

{
  "@context": "https://schema.org",
  "@type": "AboutPage",
  "name": "About Acme Corp",
  "url": "https://acme.com/about",
  "mainEntity": {
    "@type": "Organization",
    "name": "Acme Corp",
    "url": "https://acme.com"
  }
}

Common Mistakes

Not linking the mainEntity to a full Organization markup elsewhere on the site.

Complete Guide to AboutPage Schema Markup

AboutPage is the WebPage subtype for a page that describes who runs a site: the company behind a product, a publication's masthead, a freelancer's "about me". Google doesn't document a search feature for it. The type labels the page, and its mainEntity says whom the page is about, which is where its value lies.

Google's Organization documentation recommends placing Organization markup on the home page or on a single page that describes the organization, such as the about us page. An about page is often the natural home for the full description: the legal name, logo, contact details, address, founding date, and sameAs links to the organization's profiles on other sites. Put that Organization in the page's markup and make it AboutPage's mainEntity.

If the home page already describes the organization, don't write a second copy with slightly different details. Give the Organization an @id, such as https://example.com/#organization, and refer to that @id from the about page's mainEntity. Search engines then see one entity described in one place, and a new logo or address only has to change once.

For a personal site, the about page describes a Person. Google's profile page documentation lists an "About Me" page on a blog, and an employee page on a company website, as valid uses of ProfilePage, with the person as its mainEntity. ProfilePage is the type Google reads for pages about creators.

Keep the markup true to the page. If the name, logo or founding year in the JSON-LD differs from what the page shows, or from the Organization markup on the home page, search engines get conflicting descriptions of one entity. The Schema Validator reports an Organization described twice without a shared @id, and an @id reference that doesn't match any object in the markup you check.

Related Types

ContactPage WebPage Organization

AboutPage Schema Markup