What are the six properties of a maximum-authority author schema and what does each one do?
The Schema.org Person type has over 40 possible properties. For a business building for AI recommendation, six are strategically critical. Here is exactly what each one does:[2]
1. name. Your identity anchor
The most critical property. Your name must be exact, complete, and identical across every platform where you have a presence. If your LinkedIn says "Cindy Molchany," your schema says "Cindy Anne Molchany," and your Instagram bio says "Cindy," AI may treat these as three separate entities rather than one authority.
Choose the version of your name you will use everywhere. Typically your full legal name or consistent professional name. And standardize it across all platforms before building your schema.
2. url. Your identity home base
This should be your official website URL. The canonical home for your professional identity. Not a social media profile. Not a landing page. Your primary domain.
The url property tells AI: this is where the definitive record of this person lives. It becomes the identity anchor that all other signals point back to.
3. jobTitle. Your expertise signal
This is where most experts leave signal on the table. "Coach" tells AI almost nothing. "Executive coach for founders scaling from $500K to $2M" tells AI your specialty, your client type, and the stage of business you serve. The more specific your jobTitle, the stronger the topical authority claim.
Write your jobTitle the same way you would introduce yourself at a conference: specific enough that the right person in the room knows immediately that you can help them.
4. sameAs. Your verification network
An array of URLs pointing to your verified profiles on other platforms. This is the most underused and most powerful property in author schema. Each sameAs link creates an entity connection that allows AI to incorporate off-site signals into its assessment of your on-site authority.
Minimum sameAs links for a business:
- LinkedIn profile URL
- Instagram or other social platform where you publish substantive content
- Any industry directory profile where you are listed
5. description. Your credential summary
One to three sentences summarizing your expertise, audience, and credentials. This is machine-readable context that helps AI disambiguate between people with the same name and reinforces the topical territory claimed by your jobTitle.
Write it as a tight credential statement: what you do, who you serve, and what qualifies you. Keep it consistent with your LinkedIn headline and about page bio.
6. image. Your identity visual anchor
A URL pointing to your professional photo. This is optional but contributes to entity recognition, particularly as AI systems become more multimodal. Use a consistent headshot across your schema, LinkedIn, and website bio. The same face appearing in multiple places adds a visual corroboration layer to your identity claim.
Which author schema property do most experts miss. And why does it matter most?
In practice, the sameAs array is what most websites omit entirely. They include a name and sometimes a URL, and stop there. The result: AI has a name and an on-site claim. But no mechanism for verifying the claim against independent sources.
Think of it from the AI's perspective. It has encountered thousands of people claiming expertise in business coaching, health consulting, or marketing strategy. The ones it can verify. Whose identity is confirmed by LinkedIn data, by podcast appearances, by directory listings. Are the ones it trusts and recommends. The ones who simply assert expertise with no corroboration are weighted accordingly.[3]
Adding sameAs links is the mechanism for shifting from assertion to corroboration. It takes five minutes to add four sameAs URLs. The return is a fundamentally stronger identity signal on every page where you include it.
What does maximum-authority author schema look like as complete JSON-LD?
Here is a complete, maximal example using real data as a template:
"author": {
"@type": "Person",
"name": "Cindy Anne Molchany",
"url": "https://perfectlittlebusiness.com",
"jobTitle": "Founder, Perfect Little Business",
"description": "Cindy Anne Molchany is the founder of Perfect Little Business and creator of the Authority Directory Method. She helps entrepreneurs build AI-discoverable authority systems that generate leads without chasing.",
"image": "https://www.vibecodeyourleads.com/assets/images/cindy-molchany.jpg",
"sameAs": [
"https://www.linkedin.com/in/cindyannemolchany/",
"https://www.instagram.com/cindyannemolchany/",
"https://perfectlittlebusiness.com"
]
}
Note that the official website also appears in the sameAs array. reinforcing the url property with an additional identity link. This is intentional redundancy that strengthens entity coherence.
Why does consistent author schema across every page act as an authority multiplier?
A single page with perfect author schema is a data point. Fifty pages with identical, perfect author schema is a pattern. AI systems build entity profiles over time by reading many signals from many sources. Consistent authorship data across a large content cluster tells the AI: this is a real, persistent, prolific expert who has built a substantial body of knowledge in this area.
The practical implication: once you write your author schema block, it should not change from page to page. The headline, description, and breadcrumb change. The author block stays identical. This consistency is not laziness. It is the architectural principle that turns a collection of pages into a coherent identity signal.[4]
This is why the Authority Directory Method builds 125 content nodes. Each carrying the same author schema, linking back to the same LinkedIn, the same official website, the same Instagram. After 125 nodes, the entity record is unmistakably established. That is the architecture of authority, not just the content of it.
How do you audit your existing author schema for gaps?
If you have existing content, run this checklist for each page:
- Does the page include a JSON-LD script block in the static HTML source?
- Is there a BlogPosting or Article type with an author property?
- Is the author a Person type (not a string, not an Organization)?
- Does the Person block include: name, url, jobTitle, sameAs?
- Are all sameAs URLs pointing to active, complete profiles?
- Is the name property identical to your name everywhere else?
- Does the schema appear in View Source (not just in DevTools)?
Any "no" answer is a gap. Prioritize adding sameAs first if it is missing. It delivers the largest incremental signal value on pages that already have basic author attribution.
The VCYL Perspective
The way I think about author schema properties: each one is a question the AI is trying to answer about you, and your schema is your structured response.
Who is this? → name. Where do they live online? → url. What is their professional role? → jobTitle. Who else confirms they are who they claim to be? → sameAs. What are their credentials in brief? → description. What do they look like? → image.
Most experts answer maybe two of these questions in their schema. Answering all six is a significant competitive advantage in AI recommendation. Not because it is technically complex, but because almost no one does it.
The most important thing I want you to take from this page is not the property list. It is the principle behind it. AI is trying to verify you. Your job is to make that verification as easy and as multi-directional as possible. Every property you add is another pathway the AI can use to confirm: this is a real expert, with real credentials, with a consistent identity across the web. Give it those pathways.
