---
title: "Author Markup for AI: Getting Person Schema Right on a WordPress Blog"
url: https://hostmy.blog/person-schema-author-wordpress/
date: 2026-11-13
modified: 2026-11-13
lang: en
author: "Aditya Sharma"
description: "Person schema tells a machine who wrote a post. The fields, the common faults and the checks, built on Google's guidance on the author property."
categories:
  - "RankReady"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2797-1024x538.jpg
word_count: 1421
---

# Author Markup for AI: Getting Person Schema Right on a WordPress Blog

Person schema tells a machine who wrote a post, and most WordPress blogs either have none or have it wrong. The common faults are small. They include a job title inside the name, two authors joined in one field, a name in the markup that differs from the byline on the page, or a second Person node written by a second plugin. Each makes the author harder to resolve, and each is easy to check.

This post is about getting author markup right on a WordPress blog. It uses Google's guidance on the author property, and it deliberately skips what other posts here already cover. [Structured data in WordPress: Article, FAQPage, Speakable and Person](/structured-data-wordpress/) places Person among the four types, and [E-E-A-T for AI answers is judged one sentence at a time](/eeat-seo-ai-answers/) covers why authority works per claim. This one is the mechanics.

![Numbered outline of this post, Author Markup for AI: Getting Person Schema Right on a WordPress Blog: 1 What Google says about the author property; 2 The author page is half the job; 3 Match the byline; 4 Check what your site outputs; 5 The duplicate problem; 6 A checklist.](https://hostmy.blog/wp-content/uploads/2026/10/hmb-diagram-2797.png)The route through this post.

## What Google says about the author property

Google's [Article structured data documentation](https://developers.google.com/search/docs/appearance/structured-data/article) sets out several rules for the author property. Use Person for a person and Organization for an organisation, and not a generic type. In the name property, give only the author's name, and leave out job titles, honorifics, publisher names and introductory words such as posted by. Put those details in their own properties, such as jobTitle. The url should point to a web page that uniquely identifies the author, and the sameAs property is an alternative. Each author gets their own entry, not one field with several names. And every author presented as an author on the page should be in the markup.

Those rules are the checklist. Everything below is how to meet them on WordPress and how to test that you have.

## The fields that matter

| Field | What to put | The common mistake |
| ----- | ----------- | ------------------ |
| name | The author's name, and nothing else | Adding a title, such as Dr or Senior Editor |
| url | A page that is about this author | Pointing at the homepage, or at a page that is not about them |
| sameAs | Links to the author's profiles elsewhere | Linking to pages that are not theirs |
| jobTitle | Their role, as its own field | Putting it in the name |
| description or bio | One or two sentences on why they know the subject | Leaving it empty |
| knowsAbout | The topics they cover | Listing everything |
| image | A real photo | A placeholder |

The first two are the ones Google names. The rest are what make the Person useful to a system trying to work out whether this is a real, reachable human with a track record. An entry with a name and nothing else weighs very little.

## The author page is half the job

The url property asks for a page that uniquely identifies the author. On WordPress, that is usually an author archive or a dedicated about page. The author archive lists posts and often has no biography, so it may not identify anyone. A dedicated page with a photo, a bio, credentials and links gives the url something to point at. Make the page real, link to it from the byline, and make sure it says the same things the markup does.

Site owners often have an about page for the business and nothing for the writer. If the blog has one author, the about page can serve. If it has several, each needs their own, or the url has nothing to resolve to.

## Match the byline

Google's guidance says every author shown on the page should be in the markup. A byline that disagrees with the markup is the same problem seen from the other side. If the byline says Jane Doe and the markup says J. Doe, or an old display name, the two disagree. If a post shows two authors and the markup has one, the second is missing. Check the byline and the markup together, not separately.

## Two authors, or a company

For a post with two authors, create two Person entries in the author field, one each, as Google asks. Do not write the two names into one name property. For a company blog where the post is by the company and not a person, Organization is the correct type, and pretending a person wrote it is a worse choice than saying so. Where a real writer exists, name them.

## Check what your site outputs

View the source and count. These commands show how many Person nodes a post carries and whether sameAs is present.

`curl -s https://yourdomain.com/your-post/ | grep -oE '"@type" ?: ?"Person"' | wc -l
curl -s https://yourdomain.com/your-post/ | grep -o '"sameAs"' | wc -l`

One Person is the usual result for a one-author post, though a site may legitimately have a second for the publisher, so look at the markup and not only the count. Zero means no author markup at all. More than you expect means two plugins are writing it. The method is the same as in [adding schema in WordPress without duplicating what Yoast already writes](/schema-plugin-wordpress/). [Check your schema without Google's Rich Results Test, using curl and Python](/check-schema-without-google/) shows how to read the whole graph. Then run the page through a validator, as [schema validator compared: Schema.org vs Rich Results Test](/schema-validators-compared/) explains.

## The duplicate problem

The usual source of two Person nodes is an SEO plugin that writes one and an author box plugin that writes another. The two may disagree on the name or the url. Decide which owns the author data and switch the other off, or use one that adds to the existing graph and does not write a second. [Best SEO plugin for WordPress: pick one, then add the AI layer](/best-seo-plugin-wordpress/) and [Rank Math vs Yoast: which to run under an AI layer](/rank-math-vs-yoast-ai-layer/) cover how a layer should attach.

## What author markup does and does not do

It does not get you cited. No one can promise that. Google says that [E-E-A-T itself is not a specific ranking factor](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), although using a mix of factors that can identify content with good E-E-A-T is useful. What author markup does is remove a specific reason to discount you: a post with no identifiable author gives a system nothing to weigh, and a clear, consistent author gives it something. That is a smaller claim than the category often makes, and it is the accurate one.

It also does not replace the writing. A real author with a verifiable background is only useful if the post says something worth quoting, which is the point of [writing short sentences on WordPress](/write-sentences-ai-can-quote/).

## What we found on our own posts

We ran the two commands above on three live posts on this site on 12 November 2026: the Cited #8 post, the Bytespider and CCBot post, and the llms-full.txt post. Each page returned one Person node and one sameAs field, which looks like a pass. It is not. The Person node carries only the author's name in the name property, which is correct, but its url is the author archive, and that address answers with a redirect to the homepage. The table lists exactly that under url. The one sameAs we counted belongs to the publisher, so the author has none.

The count was fine and the content was not, which is why a count is only the first check. After it, open the url from the markup in a private window and read where it lands. It should load without signing in, name the author, give a short biography and link to their posts. The fix belongs on the author page and in the author fields.

## A checklist

`1. Each author has a Person entry with only their name in name.
2. url points to a page that is about that author.
3. sameAs lists real profiles.
4. The visible byline matches the markup.
5. Every author on the page is in the markup.
6. There is exactly one source of author data.
7. The page validates, and a reader can see the same facts.`

## Where Host My Blog fits

Host My Blog publishes RankReady, a free WordPress plugin with an author box that shows who wrote the post and writes Person as JSON-LD from the same fields, so the card and the markup cannot drift apart. According to [its free versus Pro page](https://hostmy.blog/docs/rankready/rankready-free-vs-pro/), the free version publishes basic Person schema, and the extended Person node with sameAs, knowsAbout and credentials is a Pro feature. The author box needs no AI provider key, and its own page says that it does not get you cited. The free [AI Readiness Checker](https://hostmy.blog/plugins/rankready/ai-readiness-checker/) runs 41 checks on your live site.

If you counted the Person nodes on your best post tonight, would the number match the names on the page?