How Person schema works
Person describes an individual human being rather than a page or a company. The properties cover the name, a url for the profile page that represents them, an image, a job title, the organisation they work for, the subjects they know about, and sameAs — the professional profiles and author pages elsewhere that are the same person.
It is normally used in two places. On an author or about page, the markup identifies whose page it is. On an article, the author property points to that person, which is how a set of posts becomes attributable to one identifiable writer rather than to a site.
Where a single person is effectively the business — a consultant, a freelancer, a solo practice — a site may describe both a Person and an Organization and connect them, so that the individual and the trading entity are related rather than competing as two descriptions of the same thing.
Why Person schema matters
Search engines are increasingly asked who is behind a piece of advice, not just whether the page reads well. Markup that names the author, links to their profile and connects that profile to their professional presence elsewhere makes the answer explicit instead of leaving it to be inferred from a byline.
That matters most on the pages where trust is doing the work: advice about money, health, legal matters, or anything a reader will act on. A named individual with a verifiable track record is the on-page evidence behind experience, expertise, authoritativeness and trust. The markup does not create that credibility — it makes existing credibility legible.
Common mistakes with Person schema
The first is describing a business as a Person because one individual runs it. If the entity signs contracts and issues invoices, it is an organisation, and mixing the two produces a confused description of who you actually are. Describe both and link them instead.
The second is markup pointing at nothing. An author property naming someone with no profile page, no biography and no presence anywhere else asserts an identity that cannot be checked. Inventing an author outright, complete with a stock photograph, is the version of this that does real damage when a reader notices.
The third is expecting the markup to produce a knowledge panel. Those are built from what the wider web says about a person, not from what a person’s own site claims about themselves.
How to act on it
Give every author who publishes on the site a real page: their name, what they actually do, how long they have done it, where else they write, and a way to reach or verify them. Then mark that page up as a Person and point each article’s author property at it, so one identity serves the whole archive.
Keep the sameAs list to profiles the person genuinely controls and keeps current. If your professional identity is part of how you win work — which it is for most consultants and freelancers — treat the profile page, the markup and the external profiles as one connected job rather than three, and align it with the way you present yourself professionally everywhere else.
