Person and Organization schema: best practices explained

Why Person and Organization schema matter for SEO

Search engines need to understand who you are and what your organization does—and they learn this through structured data. Person and Organization schema are two of the most powerful markup types you can implement to strengthen your entity presence in search results. When implemented consistently across your site, these schemas help Google and other search engines build a reliable knowledge graph entry for you or your company, which can improve visibility in knowledge panels, increase click-through rates, and establish authority in your field.

In this guide, we'll explore how to implement Person and Organization schema: best practices explained so your brand appears exactly as you intend it to across search engines and knowledge bases.

Person schema on your about page

Your about page is the natural home for Person schema. This is where you tell search engines who you are: your name, professional title, image, and how to find you across the web. The goal is to create a single canonical identity that search engines can reference whenever your name appears elsewhere on the web.

Here's a practical JSON-LD example for a senior engineer's about page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Sarah Chen",
  "jobTitle": "Senior Full Stack Engineer",
  "url": "https://sarahchen.dev",
  "image": "https://sarahchen.dev/images/sarah-headshot.jpg",
  "sameAs": [
    "https://www.linkedin.com/in/sarah-chen-dev",
    "https://github.com/sarahchen",
    "https://twitter.com/sarahchen_codes"
  ],
  "email": "sarah@sarahchen.dev",
  "workLocation": {
    "@type": "Place",
    "name": "Remote"
  }
}
</script>

The critical fields here are name, jobTitle, and most importantly, sameAs. The sameAs array links your Person entity to your verified profiles on LinkedIn, GitHub, and other platforms. This tells Google: "This person is Sarah Chen, and you can verify that identity by checking these links."

Use your professional headshot for the image field—a clear, well-lit photo that matches your LinkedIn avatar. Consistency in appearance across profiles strengthens entity recognition. Make sure the image URL is stable and won't change.

Connect authors to articles consistently

Every article you publish should point back to your Person schema. When you do this consistently, search engines learn to associate articles with an author entity, which strengthens both your personal brand and your article's credibility signal.

Here's how to markup an article's author relationship:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Building Scalable Node.js APIs with PostgreSQL",
  "datePublished": "2024-01-15",
  "dateModified": "2024-01-18",
  "author": {
    "@type": "Person",
    "name": "Sarah Chen",
    "url": "https://sarahchen.dev"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Expona",
    "url": "https://expona.dev",
    "logo": {
      "@type": "ImageObject",
      "url": "https://expona.dev/logo.png",
      "width": 600,
      "height": 60
    }
  },
  "image": "https://expona.dev/images/article-header.jpg",
  "description": "Practical patterns for building high-performance Node.js APIs"
}
</script>

The key is using the same url in the author's Person object that you use in the about page schema. This is how search engines connect the dots: "The author Sarah Chen at https://sarahchen.dev wrote this article." Repeat this pattern for every article you publish.

If you're a team of writers, create a Person schema for each author and reference the appropriate one in each article. Over time, search engines will associate each author with their body of work, making it easier for readers to find all articles by that person.

Organization schema for companies and publications

If you run a company, publish a newsletter, or maintain a publication like Expona, you need Organization schema. This markup tells search engines the basics: who you are, where people can find you, and what you stand for across social media.

Here's a comprehensive Organization schema example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Expona",
  "url": "https://expona.dev",
  "logo": "https://expona.dev/logo.png",
  "image": "https://expona.dev/og-image.jpg",
  "description": "Practical development write-ups from senior engineers",
  "email": "hello@expona.dev",
  "phone": "+1-555-0100",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Tech Street",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94103",
    "addressCountry": "US"
  },
  "sameAs": [
    "https://twitter.com/exponadev",
    "https://linkedin.com/company/expona",
    "https://github.com/expona"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer service",
    "email": "support@expona.dev"
  }
}
</script>

Place this on your homepage or site-wide in the footer. The logo field should point to a high-quality PNG or SVG (at least 112x112 pixels, but ideally 600x600). Google uses this logo in knowledge panels when your organization appears in search results.

The sameAs array here works exactly like it does for Person schema: it links your Organization entity to verified social profiles. This prevents confusion if another company has a similar name. Search engines trust verified social profiles as proof of identity.

If you operate in multiple locations, you can add a contactPoint array instead of a single object, specifying different departments or regions. For a remote publication like Expona, one contact point is usually sufficient.

Building entity consistency across your site

The real power of Person and Organization schema emerges when you maintain consistency. Search engines don't just look at one page—they track how your entity appears across your entire site and across the web.

Here's what consistency means in practice:

• Same name everywhere: If your Person schema says "Sarah Chen," don't publish articles under "S. Chen" or "Sara Chen." Use the exact same spelling on bylines, author pages, and social profiles.
• Same URLs: If your about page is at https://sarahchen.dev, always use that URL in sameAs links and article author references. Never link to https://sarahchen.dev/ or http://sarahchen.dev.
• Same profile links: If you list your LinkedIn profile in your Person schema, maintain that profile with current information. An outdated LinkedIn page confuses search engines about whether this is really you.
• Unified org markup: Use the same Organization name, logo, and description across every page where you reference your company. Don't say "Expona" on one page and "Expona Inc." on another.

When search engines see consistent markup, they consolidate information into a single entity graph. This entity becomes stronger: more trustworthy, more visible, more likely to appear in knowledge panels and rich results.

Testing and validation

Before you launch your schema, test it with Google's Rich Results Test (search.google.com/test/rich-results). Paste your page URL and the tool will parse your markup and show you any errors or warnings.

Common issues to watch for:

• Missing required fields (name, url, or logo for Organization)
• Malformed URLs (missing https:// or typos)
• Image URLs that return 404 errors
• Mismatched names between your site content and your schema markup

After you fix errors, submit your pages to Google Search Console so the search engine recrawls and re-indexes your markup.

Common mistakes

Mistake 1: Inconsistent name spelling. Your schema says "Sarah Chen" but your bylines say "Sarah Chen Ph.D." Search engines treat these as different entities. Pick one official name and use it everywhere.

Mistake 2: Broken or outdated sameAs links. If you link to a LinkedIn profile that no longer exists or has been deleted, search engines can't verify your identity. Maintain your external profiles or remove the links from your schema.

Mistake 3: Generic or low-quality images. Using a logo that's blurry, tiny, or looks unprofessional hurts your brand credibility. Invest in a clean, high-resolution logo and headshot.

Mistake 4: Orphaned author markup. If you publish an article under an author Person schema that doesn't have its own about page or public profile, search engines can't verify that person exists. Always link authors to real, accessible pages.

Mistake 5: Ignoring the publisher field. In BlogPosting or NewsArticle schema, always include both an author (Person) and a publisher (Organization). This tells search engines who wrote it and where it was published, strengthening both entities.

Key takeaways

• Person schema on your about page creates a canonical identity that search engines use to connect you to your articles and online presence.
• The sameAs field is your verification mechanism—link to real, maintained profiles on LinkedIn, GitHub, Twitter, and other platforms you actively use.
• Every article should reference the same Person URL for its author; over time this builds author entity strength and recognition in search results.
• Organization schema should live on your homepage or site-wide footer and provide a single source of truth for your company's name, logo, contact info, and social profiles.
• Consistency is everything: same names, same URLs, same external links across your entire site and external profiles make entity consolidation possible.
• Test your markup with Google's Rich Results Test before launch and monitor Google Search Console for any markup issues over time.
• Well-implemented Person and Organization schema can lead to knowledge panel appearances, improved click-through rates from search results, and stronger author/publication entity recognition.