Skip to content

SOP 003: Schema Markup for Machine Trust

Fresh
Document Control
SOP IDSOP-003
Version1.0
CategoryTechnical Foundation
ComplexityMedium
SourceMachine Trust: Authority, Rebuilt for Retrieval

Purpose

Schema markup helps machines understand relationships between entities, verify content ownership, and establish trust signals. This procedure covers implementing schema that enhances AI retrieval and citation.

Why Schema Matters for AI

┌─────────────────────────────────────────────────────────────────────┐
│                    SCHEMA FOR AI SYSTEMS                             │
├─────────────────────────────────────────────────────────────────────┤
│                                                                      │
│   Without Schema                With Schema                         │
│   ──────────────                ───────────                         │
│   "Some company wrote          "TechCorp Inc (verified org)         │
│   about AI tools"              published via Dr. Jane Doe           │
│                                (verified author) on 2025-12-01"     │
│                                                                      │
│   Result: Low trust            Result: High trust                   │
│   Result: Rarely cited         Result: Frequently cited             │
│                                                                      │
└─────────────────────────────────────────────────────────────────────┘

Procedure

Step 1: Implement Organization Schema

Add to every page (typically in the header):

json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://yoursite.com",
  "logo": "https://yoursite.com/logo.png",
  "sameAs": [
    "https://linkedin.com/company/yourcompany",
    "https://twitter.com/yourcompany",
    "https://facebook.com/yourcompany"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-555-5555",
    "contactType": "customer service"
  }
}

Step 2: Implement Person Schema for Authors

For every content author:

json
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "Dr. Jane Doe",
  "jobTitle": "Head of AI Research",
  "worksFor": {
    "@type": "Organization",
    "name": "Your Company"
  },
  "sameAs": [
    "https://linkedin.com/in/janedoe",
    "https://twitter.com/janedoe",
    "https://orcid.org/0000-0001-2345-6789"
  ],
  "alumniOf": {
    "@type": "Organization",
    "name": "Stanford University"
  },
  "knowsAbout": ["Artificial Intelligence", "Machine Learning"]
}

Step 3: Implement Article Schema

For blog posts and articles:

json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "description": "Brief description of the article",
  "author": {
    "@type": "Person",
    "name": "Dr. Jane Doe",
    "url": "https://yoursite.com/authors/jane-doe"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yoursite.com/logo.png"
    }
  },
  "datePublished": "2025-12-01",
  "dateModified": "2025-12-15",
  "mainEntityOfPage": "https://yoursite.com/article-url"
}

Step 4: Add FAQPage Schema

For content with questions and answers:

json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is content chunking?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Content chunking is the process of breaking content into logical blocks of 100-300 tokens for optimal AI retrieval."
      }
    },
    {
      "@type": "Question",
      "name": "Why does chunk size matter?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "LLMs retrieve and score individual chunks, not full pages. Properly sized chunks improve semantic matching."
      }
    }
  ]
}

Step 5: Implement HowTo Schema

For procedural content:

json
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Optimize Content for AI Retrieval",
  "description": "Step-by-step guide to structuring content for LLM systems",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Audit existing content",
      "text": "Review current structure for chunk-friendly organization"
    },
    {
      "@type": "HowToStep",
      "name": "Define chunk boundaries",
      "text": "Break content into 100-300 token blocks with single ideas"
    }
  ]
}

Step 6: Validate Schema

  1. Use Google's Rich Results Test
  2. Use Schema.org Validator
  3. Check for errors and warnings
  4. Test on multiple pages

Priority Schema Types

Schema TypePriorityUse Case
OrganizationCriticalEvery site
PersonCriticalAuthor attribution
ArticleHighBlog/news content
FAQPageHighQ&A content
HowToHighTutorials/guides
ProductMediumE-commerce
LocalBusinessMediumPhysical locations
WebPageMediumGeneric pages

Verification Checklist

  • [ ] Organization schema on all pages
  • [ ] Person schema for all authors
  • [ ] Article schema on blog posts
  • [ ] FAQPage schema where applicable
  • [ ] HowTo schema for procedural content
  • [ ] All sameAs links are valid
  • [ ] Dates are in ISO 8601 format
  • [ ] Schema validates without errors

Common Mistakes

MistakeImpactFix
Missing sameAs linksReduced entity verificationAdd all official profile URLs
Inconsistent namesEntity confusionUse exact same name everywhere
Missing author schemaLow trust signalsAdd Person schema for authors
Outdated datesFreshness penaltyUpdate dateModified regularly

See Also

Based on insights from Duane Forrester Decodes Substack