Author and Person schema

01What is author schema?

Author schema is the author property inside Article, BlogPosting or NewsArticle structured data, filled with a Person or an Organization. It states who wrote the piece in a form a machine can read without parsing the byline. A Person, in schema.org terms, is any individual; the vocabulary defines it in one line as a person, alive, dead, undead or fictional.

For search engines and AI answer engines, the useful part is not the name. Names collide: there are many writers called Jane Doe. The useful part is the link from the name to a page that identifies one specific person. This guide, part of the AI answers section, covers how to make that link cleanly in WordPress or any other CMS.

The schema.org Person type offers dozens of properties, from jobTitle to alumniOf. Google uses a small subset for article authors. Start there, and add more only when the author page shows the same facts.

02Article author vs Person: what is the difference?

The Article is the page. The Person is the human who wrote it. The author property is the connection between them. You can write the Person inline inside each article, or describe the Person once and refer to it everywhere by an identifier.

Google's Article structured data documentation sets out the properties it reads for authors. author.name holds the name and nothing else: no job title, no publisher, no "posted by". author.url is a link to a page that uniquely identifies the author, such as a bio page or a profile. Google recommends the Person type for people and Organization for organizations, and warns against the generic Thing type.

03Author pages and @id

An author page is a page on your site about one writer: who they are, what they cover, and how to check their background. It is the natural target for author.url, and Google's Article documentation suggests marking such an internal profile page up with ProfilePage structured data.

An @id is an identifier you give a node in your JSON-LD so other nodes can refer to it. A common pattern is the author page URL plus a fragment, such as https://example.com/authors/example-author/#person. Every article then sets author to {"@id": "...#person"}, and the full Person description lives once, on the author page. One person, one identifier, used everywhere.

The same pattern works for the publisher. The guide to Organization schema and entity markup shows how to give the site's Organization an @id and refer to it from every article's publisher property.

04How does sameAs help an author?

sameAs is a list of URLs for pages that identify the same person elsewhere: a professional profile, a university staff page, a publication's contributor page. It turns a name into a set of cross-references a machine can follow.

Choose sameAs links with care. Each one should be a page about that exact person, controlled by them or by an institution that knows them, and it should name them the way your byline does. A sameAs pointing to a search results page, a namesake or a dead profile adds noise rather than certainty.

Write the author page first and add sameAs second. A profile link is only as useful as the page it confirms, and an author page that says who the writer is and what they know does more for a reader than any list of links.

Shared links travel without their byline, which is a related problem covered in the explainer on byline schema for shared links.

05Multiple authors and reviewers

When a piece has more than one author, Google's author markup best practices say to list each author in their own entry in an array, not to join names with "and" in one field. Everyone shown as an author on the page should be in the markup, and no one should be in the markup who is not shown on the page.

Reviewers, editors and fact checkers are different roles. Schema.org offers properties such as editor and, on WebPage, reviewedBy. Use them only for people who actually did that work and are named on the page. A reviewer listed in markup but invisible to readers tells machines something the page does not, which is the opposite of what markup is for.

06Author schema in WordPress

WordPress gives every user with published posts an author archive, usually at /author/username/. By default that archive is a list of posts with little or no information about the writer, which makes it a weak target for author.url. Turn it into a real author page: a short biography written in the first person or by an editor, the topics the writer covers, and links to profiles that identify them.

Then check what your site prints. Themes, SEO plugins and schema plugins can each output a Person for the post author, and they do not always agree on the name, the URL or the @id. View the page source, search for "Person", and count the nodes. One Person per author, with one @id used everywhere, is the goal.

• Fill in the display name exactly as the byline should read, because many plugins copy it into author.name.
• Add the biography and profile links in the user profile screen if your plugin reads them from there.
• Do not let a generic "admin" account publish articles; it produces an author called admin.
• Keep guest authors as their own users, or mark them up by hand, rather than crediting the editor who pasted the text.

07Common author schema mistakes

Most author problems are honesty problems, not syntax problems. Google's guidance on creating helpful, reliable, people-first content asks whether it is self-evident who wrote a page and whether bylines lead to more information about the author.

The same Google page warns that fabricating creator profiles, including AI-generated headshots, made-up names or false credentials, is a form of deception. The mistakes to look for in an audit:

• A persona with no real person behind it, given a stock or generated photo and a borrowed list of credentials.
• Job titles or "Dr" packed into author.name.
• A site or brand name used as a Person.
• Theme and plugin each printing a different author block for the same article.
• Author pages that are empty archives with no information about the writer.
• AI-assisted drafting presented as a named expert's work. If AI helped, say so; the guide to disclosing AI-assisted content covers how.

An editorial byline is a legitimate choice. A publication can name an Organization as author, as long as that is what the page shows. This is part of structured data for bylines done honestly: the markup says exactly what the reader sees.

08JSON-LD example

The example below describes an article and its author on one page, with the Person given an @id so other articles can point to it. Values are examples. Keep datePublished and dateModified equal to the visible dates, as the guide to Article schema and dateModified explains.

1{2  "@context": "https://schema.org",3  "@graph": [4    {5      "@type": "Article",6      "@id": "https://example.com/guides/soil-testing/#article",7      "headline": "Example Guide to Garden Soil Testing",8      "datePublished": "2026-10-02",9      "dateModified": "2026-11-04",10      "author": {111        "@id": "https://example.com/authors/example-author/#person"12      },13      "publisher": {14        "@id": "https://example.com/#organization"15      }16    },17    {18      "@type": "Person",19      "@id": "https://example.com/authors/example-author/#person",20      "name": "Example Author",221      "jobTitle": "Soil Scientist",22      "url": "https://example.com/authors/example-author/",323      "sameAs": [424        "https://example.org/people/example-author",25        "https://example.net/profile/example-author"26      ]27    }28  ]29}