Person schema identifies an individual — an author, a founder, a team member — as a distinct, connected entity, using their existing, confirmed bio and credentials, which can support how search engines and AI systems attribute and understand authorship on your site.
Person & author entity schema
An author or team member identified as a schema entity, from their confirmed bio.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- The individual’s confirmed name, role, and bio as it should appear
- Any professional profiles or credentials that should be linked, confirmed as genuinely theirs
- Confirmation of which pages or posts should attribute to this person
This or something else?
| You want a specific individual identified with Person schema | This fix covers it |
| You want the business itself represented as an entity, not an individual person | Organization & WebSite entity graph build |
| You want Article schema connecting posts to this person, not just the Person entity itself | Breadcrumb & Article schema implementation, worth doing alongside this |
| You want multiple people’s profiles linked together as an organisation’s team | Worth discussing scope directly if this covers several individuals at once |
What we do
- Confirm the individual’s accurate bio, role, and credentials
- Implement Person schema reflecting those confirmed details
- Link genuinely relevant, current professional profiles
- Connect the Person entity to relevant authored content where applicable
- Verify the schema validates correctly
- Check for consistency with any existing author box or bio content on the page
What is included
- Person schema implemented with confirmed, accurate details
- Genuine professional profiles linked where applicable
- Connection to relevant authored content, where applicable
- Verified, valid schema output
Not included
- Writing or embellishing a bio beyond what’s confirmed as accurate
- Organization-level entity schema, a separate, related fix
- Ongoing updates as the individual’s role or credentials change
- Multiple individuals’ schema as a larger, separate scope if not specified upfront
Questions about this fix
Will this improve how search engines attribute authorship to our content?
It provides clearer, structured information connecting a person to content they've authored, which can support more accurate attribution, though it doesn't control how any specific platform ultimately displays or uses that information.
What if the person's role or bio changes later?
The schema would need updating to stay accurate — worth flagging to us if a significant change happens, since inaccurate schema is arguably worse than none at all.
Can this be done for someone who's no longer with the company?
We'd recommend against maintaining schema for someone no longer accurately associated with your business — that's a case for removing or updating the schema rather than implementing it fresh.
Is this worth doing for a small team where nobody has a public profile?
It's most valuable when there's genuine, verifiable information and credentials to connect — for a very informal setup with little public presence, the practical benefit may be limited until that changes.
Does this help with E-E-A-T (experience, expertise, authoritativeness, trust) that Google talks about?
Structured author information is one relevant signal among the several factors that contribute to how Google and other systems assess content quality and trust, though it's not the whole picture on its own.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.