Skip to content

SOP 007: Author Identity Signals

Fresh
Document Control
SOP IDSOP-007
Version1.0
CategoryTrust & Authority
ComplexityLow
SourceMachine Trust: Authority, Rebuilt for Retrieval

Purpose

Named authorship matters to both Google and GenAI systems. LLMs weigh authorship cues when ranking or generating responses. This procedure establishes consistent author identity across all platforms.

Why Author Identity Matters

┌─────────────────────────────────────────────────────────────────────┐
│                    AUTHOR IDENTITY SIGNALS                           │
├─────────────────────────────────────────────────────────────────────┤
│                                                                      │
│   Without Author Signals         With Author Signals                │
│   ──────────────────────         ──────────────────                 │
│   Anonymous content          ──► Named, credentialed author         │
│   No verification possible   ──► Linked to social profiles          │
│   Low trust signal           ──► High trust signal                  │
│   Rarely cited               ──► Frequently cited                   │
│                                                                      │
│   AI Systems Check:                                                 │
│   ✓ Is author name consistent across platforms?                    │
│   ✓ Do credentials match claimed expertise?                        │
│   ✓ Is there a traceable publication history?                      │
│                                                                      │
└─────────────────────────────────────────────────────────────────────┘

Procedure

Step 1: Create Author Hub Page

Create a dedicated author profile page on your website:

html
<!-- /authors/jane-doe.html -->
<article itemscope itemtype="https://schema.org/Person">
  <h1 itemprop="name">Dr. Jane Doe</h1>
  <img itemprop="image" src="/images/jane-doe.jpg" alt="Dr. Jane Doe">

  <p itemprop="jobTitle">Head of AI Research</p>
  <p itemprop="worksFor" itemscope itemtype="https://schema.org/Organization">
    <span itemprop="name">TechCorp Inc.</span>
  </p>

  <div itemprop="description">
    <p>Dr. Jane Doe is a leading expert in AI and machine learning
    with 15 years of experience...</p>
  </div>

  <h2>Connect</h2>
  <ul>
    <li><a itemprop="sameAs" href="https://linkedin.com/in/janedoe">LinkedIn</a></li>
    <li><a itemprop="sameAs" href="https://twitter.com/janedoe">Twitter</a></li>
    <li><a itemprop="sameAs" href="https://github.com/janedoe">GitHub</a></li>
  </ul>

  <h2>Articles by Dr. Doe</h2>
  <!-- List of articles -->
</article>

Step 2: Implement Consistent Bylines

Every article should include:

html
<article>
  <header>
    <h1>Article Title</h1>
    <div class="byline">
      <img src="/images/jane-doe.jpg" alt="Dr. Jane Doe" class="author-photo">
      <div>
        <a href="/authors/jane-doe" rel="author">Dr. Jane Doe</a>
        <p>Head of AI Research | PhD, Stanford University</p>
        <time datetime="2025-12-01">December 1, 2025</time>
      </div>
    </div>
  </header>

  <!-- Article content -->
</article>

Step 3: Add Person Schema

Include on author hub and every article:

json
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Dr. Jane Doe",
  "givenName": "Jane",
  "familyName": "Doe",
  "honorificPrefix": "Dr.",
  "jobTitle": "Head of AI Research",
  "image": "https://yoursite.com/images/jane-doe.jpg",
  "url": "https://yoursite.com/authors/jane-doe",
  "sameAs": [
    "https://linkedin.com/in/janedoe",
    "https://twitter.com/janedoe",
    "https://orcid.org/0000-0001-2345-6789",
    "https://github.com/janedoe"
  ],
  "worksFor": {
    "@type": "Organization",
    "name": "TechCorp Inc.",
    "url": "https://techcorp.com"
  },
  "alumniOf": {
    "@type": "Organization",
    "name": "Stanford University"
  },
  "knowsAbout": [
    "Artificial Intelligence",
    "Machine Learning",
    "Natural Language Processing"
  ]
}

Step 4: Align Third-Party Profiles

Ensure consistency across all platforms:

PlatformMust Match
LinkedInName, title, photo, bio
Twitter/XName, handle, bio
GitHubName, bio
MediumName, bio, photo
SubstackName, bio, photo
Company websiteAll of the above

Step 5: Use Consistent Photo

Use the same professional headshot everywhere:

  • Same crop/framing
  • Same expression
  • Updated within last 2-3 years

Step 6: Publish on Third-Party Platforms

Extend your author identity:

  1. LinkedIn Articles - Publish thought leadership
  2. Medium - Share expertise with broader audience
  3. GitHub - For technical content
  4. Guest posts - On industry publications

Each must link back to your author hub.

Step 7: Participate in Expert Content

Join or create expert roundups:

markdown
"In a recent survey of AI experts, Dr. Jane Doe,
Head of AI Research at TechCorp, noted:
'The shift to retrieval-based systems is
fundamentally changing how we optimize content.'"

Author Identity Checklist

  • [ ] Author hub page created on website
  • [ ] Person schema implemented
  • [ ] Consistent bylines on all content
  • [ ] Same name used everywhere
  • [ ] Same photo used everywhere
  • [ ] LinkedIn profile matches
  • [ ] Twitter/X profile matches
  • [ ] GitHub profile matches (if applicable)
  • [ ] Medium profile matches (if applicable)
  • [ ] All profiles link to author hub

Common Mistakes

MistakeImpactFix
Different names on platformsEntity confusionStandardize to one format
Missing schemaNo machine verificationAdd Person schema
No author hubWeak authority signalCreate dedicated page
Outdated photosIdentity mismatchUpdate consistently
No credentials visibleLow expertise signalAdd qualifications

Monitoring

Check quarterly:

  • [ ] All profiles still accessible
  • [ ] Information current and accurate
  • [ ] New platforms added to sameAs
  • [ ] Schema still validating

See Also

Based on insights from Duane Forrester Decodes Substack