Semantec SEO

Person Schema for SEO Profile Pages

Person schema is used to describe a real person in structured data.

On its own, Person is a Schema.org type. In Google Search, the cleaner pattern for a profile page is often ProfilePage + mainEntity + Person, not a loose Person object dropped onto a page with no clear profile focus. Google’s supported Search features include Profile page and Organization, and the profile page documentation says the main entity can be a Person or an Organization. JSON LD is Google’s recommended format for rich result eligible structured data.

If you want the wider cluster first, start with Schema for SEO. If you need the syntax basics, read JSON LD Basics. If your focus is entity relationships across the site, go next to Entity Markup.

What Person schema is for

Use Person schema when a page is about one identifiable person and the page gives readers enough visible detail to support that markup.

That makes it a good fit for pages such as:

  • founder pages
  • author profile pages
  • team member pages
  • speaker or contributor pages

On Semantec SEO, the clearest fit is a page like Kevin Maguire, where the page centers on one person rather than a product, a concept, or a company. Schema.org’s Person type includes properties such as name, image, jobTitle, worksFor, and knowsAbout, which makes it useful for identity, expertise, and role data.

When to use it

Use Person schema when the page has a clear person as the main focus and the visible content backs up that choice.

That means the page should show things like the person’s name, role, image, short bio, and a clean description of who they are in relation to the site. If the page is mostly about the company, the product, or a category, a different type is often the better fit. Google’s profile page documentation requires mainEntity on ProfilePage, and that main entity can be a Person or Organization. For the entity itself, name is required in Google’s profile page documentation.

When not to use it

Do not use Person schema just because a name appears on a page.

Skip it when:

  • the page is really about the business
  • the page is a product page
  • the page is a broad article with only a byline
  • the person is mentioned but not the page focus
  • the page does not give enough visible detail to support a person profile

For those cases, a cleaner move may be Organization Schema for company identity or article level markup where the person sits in an author field rather than as the full page focus. Google’s general structured data rules also say the markup should represent the main content on the page and not describe hidden or misleading content.

The core properties to think about

For most profile pages, you do not need every possible Person property. You need the fields that help identify the person cleanly and match the visible page.

The strongest starting set is:

  • name
  • image
  • description
  • sameAs
  • url

Then add role and expertise fields where they fit the page, such as:

  • jobTitle
  • worksFor
  • knowsAbout

Schema.org includes those properties on Person, and Google’s profile page documentation also calls out fields such as description, image, and sameAs for profile pages. Google says image URLs should be crawlable and indexable, should match the person, and should not use placeholder images.

Example 1: profile page markup for a founder page

This is the cleanest pattern for a page like a founder bio on Semantec SEO.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {
    "@type": "Person",
    "name": "Kevin Maguire",
    "url": "https://semantecseo.com/about/kevin-maguire/",
    "description": "Founder of Semantec SEO and creator of MIRENA.",
    "jobTitle": "Founder",
    "worksFor": {
      "@type": "Organization",
      "name": "Semantec SEO",
      "url": "https://semantecseo.com/"
    },
    "knowsAbout": [
      "Semantic SEO",
      "Topical mapping",
      "Content briefs",
      "Content rewriting",
      "Internal linking",
      "Schema"
    ],
    "sameAs": [
      "https://www.linkedin.com/in/example-profile"
    ],
    "image": "https://semantecseo.com/path/to/profile-image.jpg"
  }
}
</script>

This pattern fits pages where one person is the page focus. It also sits well beside MIRENA and a profile page like Kevin Maguire, because the relationship between person, company, and product is clear on page.

Example 2: Person nested inside organization markup

Sometimes the better move is not a full person profile page. Sometimes the person belongs inside company markup as a founder or team signal.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Semantec SEO",
  "url": "https://semantecseo.com/",
  "founder": {
    "@type": "Person",
    "name": "Kevin Maguire",
    "url": "https://semantecseo.com/about/kevin-maguire/"
  }
}
</script>

This works well on pages where the company is the page focus, not the person. It pairs naturally with Schema for SEO and Entity Markup.

Example 3: author identity on article pages

For article pages, the person may belong inside the author field instead of as a full page level profile object.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Person Schema",
  "author": {
    "@type": "Person",
    "name": "Kevin Maguire",
    "url": "https://semantecseo.com/about/kevin-maguire/"
  }
}
</script>

This is a cleaner fit for article level identity. It keeps the page type and the person role in sync.

How sameAs should be used

sameAs is one of the easiest fields to misuse.

Use it for profiles or home pages that point to the same real person. Keep it tight. Link to stable, public identity pages that match the person on your site. On Google’s profile page documentation, sameAs is for other external profiles or home pages for that profile.

That means:

  • link to strong identity profiles
  • keep the list clean
  • do not add random URLs just to fill the field
  • do not point sameAs at pages that are not really the same person

If you are mapping site wide identity across people and companies, this page should sit close to Entity Markup and JSON LD Basics.

What a good person page needs on page

The markup should mirror the visible page.

A strong person page should include:

  • the person’s full name
  • a short role statement
  • a bio
  • a clear image
  • a relationship to the brand or company
  • expertise areas, if they are relevant
  • a clean page title and H1

Google’s general structured data rules say the markup should be a true representation of the page and should not describe hidden, irrelevant, or misleading content. Google also says structured data does not guarantee a search feature will appear.

Common mistakes

Marking up a person on a page that is not a profile page

A byline alone does not turn a page into a profile page.

Using placeholder images

If the image does not represent the person, leave it out until you have the right file. Google’s profile page documentation says not to use default icons or placeholder images in the image field.

Filling sameAs with weak links

Keep identity links tight and trustworthy.

Mixing person and organization focus

If the page is about the company, the page level type should reflect that. The person can still appear as founder, employee, or author inside a broader schema block.

Marking up fields that are not visible on page

If the page does not show the role, the expertise, or the profile detail, the markup should not pretend that it does.

Validation flow

A simple validation flow works best:

  1. write the page first
  2. add the JSON LD after the visible structure is set
  3. test the markup
  4. publish the page
  5. review the live page after launch

Google’s general structured data documentation says JSON LD is the recommended format for rich result eligible markup, and Google points publishers to Rich Results Test and URL Inspection for technical checks.

If you want the wider schema workflow, the next pages should be JSON LD Basics, Schema for SEO, and Docs Outputs.

Best fit uses on Semantec SEO

Person schema fits best on Semantec SEO when the page is centered on a real person tied to the brand.

The clearest examples are:

  • founder pages
  • author profile pages
  • contributor pages
  • expert bio pages tied to product and content trust

That gives this page a natural path into Kevin Maguire, MIRENA, and Schema for SEO.

Final take

Person schema is for person identity, not page decoration.

Use it when one person is the page focus, keep the fields aligned with what readers can see, and place it in the right schema pattern for the page. For Google facing profile pages, that often means ProfilePage + mainEntity + Person. For broader company pages, it can sit inside organization markup. Schema.org supports a rich Person type, while Google’s Search documentation puts its clearest support around profile pages and general structured data quality rules.

FAQ

Is Person schema the same as a profile page?

No. Person is the entity type. ProfilePage is the page type. On a true profile page, the clean pattern is often ProfilePage with mainEntity set to Person.

Can I use Person schema on an article?

Yes, often as part of an author field, when the person is the author of the article. That is different from making the whole page a person profile.

Which fields should I start with?

Start with name, url, image, description, and sameAs, then add fields like jobTitle, worksFor, and knowsAbout when the page supports them.

What should I read next?

Start with Schema for SEO, then JSON LD Basics, then Entity Markup.

Written by

Kevin Maguire

in