What Is Author Schema and Why It Matters for SEO

Google crawls and indexes vast numbers of web pages, and for most of those pages, it has no direct way to connect the content to a real, credible creator without a helping hand from the publisher. Author schema is that helping hand. It’s a structured data signal that tells Google exactly who wrote a piece of content, links that person to their broader identity on the web, and helps search engines evaluate authorship context with far more confidence than reading raw text alone.

At Brandleap Agency, we treat author markup as a standard component of any content-authority strategy, not an optional add-on. This guide covers four things: what author schema actually is, why it matters for search, how to write valid JSON-LD, and how to test your implementation.

What author schema actually is

Author schema is a structured data property drawn from the schema.org vocabulary that explicitly connects a piece of content to its creator. The schema.org definition is precise: the author property describes “the author of this content or rating.” The expected values are a Person or Organization entity, not a plain text string. This distinction matters more than most people realize.

The property lives on CreativeWork and Rating types. In practice, that means it’s valid on any subtype of CreativeWork, including Article and BlogPosting, since both types inherit from CreativeWork. Article author schema, the combination of an Article block and a typed author entity, is the most common pattern you’ll implement in the real world.

The schema.org property, plain and simple

The author property is not a standalone schema type. It’s a relationship property that sits inside a larger Article or BlogPosting schema block and points outward to a creator entity. Many people confuse authorship markup with a separate schema type when it’s actually a connector between a piece of content and the person or organization that created it. Getting that distinction clear makes the rest of the implementation much easier to follow.

JSON-LD is the format Google recommends for delivering author structured data, and it’s what all three major WordPress SEO plugins output by default. Author microdata, the older inline HTML attribute approach, is technically valid but harder to maintain and more error-prone in practice. For any new implementation, JSON-LD is the right choice.

Person vs Organization: choosing the right type

Use Person when a real individual wrote the content, whether that’s a staff writer, a subject-matter expert, or a contributing author. Use Organization when the content is published by a brand newsroom, an editorial team, or a company without a named individual author. Using the wrong type won’t necessarily break parsing entirely, but it does reduce entity clarity for Google, which may affect how well it can disambiguate the author identity. Per Google’s Article structured data documentation, if a real person wrote the content, give them a Person entity, also referred to as a person schema (Person) in the schema.org vocabulary.

Why author schema matters for search and topical authority

Google recommends author markup for understanding and representing authorship, not as a guaranteed rich-result trigger or a direct ranking dial. That framing can undersell what it actually enables. According to Google Search Central’s guidance on author properties, typed author entities help Google perform entity disambiguation, build clearer content-to-creator linkages, and develop stronger topical authority signals over time across both the author and the site.

How Google uses author entities to understand your content

When you mark up an author with a name, url, and sameAs pointing to their LinkedIn or other authoritative profiles, Google can connect that author to a broader knowledge graph entity. That’s fundamentally different from text parsing. It means Google can recognize that the same person has written dozens of articles across your site, and that they’re the same individual who appears on LinkedIn and other credible platforms. That consistency supports topical authority at both the author level and the site level.

The connection to E-E-A-T and content trust

Google Search Central doesn’t publicly label author schema as a direct E-E-A-T ranking signal, and E-E-A-T itself isn’t described as a specific ranking factor. What structured author data does is help Google understand and disambiguate who is responsible for content. Sites with clearly and consistently marked-up authors are easier for Google to evaluate on the Experience, Expertise, Authority, and Trust dimensions than sites that publish anonymous content. That distinction carries the most weight on YMYL topics, health, finance, legal, and similar categories where authorship credibility influences how Google interprets the content’s reliability.

Writing a valid author JSON-LD block

This is where implementation gets concrete. The examples below cover both the Person and Organization patterns and include the @id approach that makes your markup reusable across every post on your site.

The Person author JSON-LD example

The following block shows a complete Article with a Person author entity. The four properties that matter most are @type, name, url linking to the author’s bio page, and sameAs linking to LinkedIn, X, or other authoritative profiles. Properties like jobTitle and image are useful but optional.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title Here",
  "datePublished": "2026-07-22T08:00:00+00:00",
  "author": {
    "@type": "Person",
    "@id": "https://yourdomain.com/authors/jane-smith#person",
    "name": "Jane Smith",
    "url": "https://yourdomain.com/authors/jane-smith",
    "sameAs": [
      "https://www.linkedin.com/in/janesmith",
      "https://x.com/janesmith"
    ],
    "jobTitle": "Senior Editor",
    "image": "https://yourdomain.com/images/jane-smith.jpg"
  }
}

One specific Google guideline that trips people up: author.name should be the author’s name only, with no job titles, honorifics, or publisher names included. “Jane Smith” is correct. “Jane Smith, Senior Editor at Acme Media” is not. That extra text reduces Google’s confidence in the entity match.

The Organization author JSON-LD example

When a company editorial team publishes content without a named individual, the Organization pattern applies. The same core properties apply: name, url, and sameAs. One clean structural benefit here is that the publisher and author can share the same Organization entity via a shared @id, which avoids repeating the same organization data twice in the markup.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title Here",
  "datePublished": "2026-07-22T09:00:00+00:00",
  "author": {
    "@type": "Organization",
    "@id": "https://yourdomain.com/#org",
    "name": "Your Company Name",
    "url": "https://yourdomain.com",
    "sameAs": [
      "https://www.linkedin.com/company/your-company"
    ]
  },
  "publisher": {
    "@type": "Organization",
    "@id": "https://yourdomain.com/#org",
    "name": "Your Company Name",
    "url": "https://yourdomain.com"
  }
}

Using @id and sameAs to build a reusable author entity

When the same author writes 50 articles, repeating their full entity definition in every post creates bloated markup and inconsistent data. The cleaner approach is to define the author as a named node with an @id on their bio page, then reference that @id from each article post instead of rewriting the full entity. Here’s what a reference-only pattern looks like in practice:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title Here",
  "author": {
    "@id": "https://yourdomain.com/authors/jane-smith#person"
  }
}

Each Article block points to the author’s @id, and Google builds its understanding of that author incrementally across the site. This produces cleaner markup and a more confident entity association over time.

Adding author schema in WordPress

Many publishers use WordPress, so the most direct implementation path is one of three SEO plugins. Each handles author markup differently, and knowing where to look saves a lot of time.

How Yoast, Rank Math, and AIOSEO handle it by default

Yoast outputs Article schema for posts by default and includes author entity data depending on how the site’s representation is configured. Customizing the author output requires using Yoast’s schema filters, such as wpseo_schema_article, rather than a UI toggle, though Yoast’s UI has evolved across versions, so check your current plugin docs to confirm exact controls. Rank Math has a dedicated “Author Schema Entity” toggle under Titles & Meta, which makes the setting easier to locate than in the other two plugins. AIOSEO outputs Person schema as part of its Article markup and lets you configure author behavior under Search Appearance.

None of these plugins are the wrong choice. The key is knowing where each one buries its author schema controls. In our experience, Rank Math surfaces those controls most directly; Yoast offers more flexibility once you’re comfortable working with WordPress filters.

Adding or overriding author markup manually

If you’re not using a plugin or need precise control over the output, add a