C11 — Chapter 3 - Schema.org

Criterion C11 : Schema Person for authors — guide + checklist

PART 1 - Fundamentals Chapter 3 - Schema.org Keyword : schema person pour auteurs

This criterion is discreet… until it blocks SEO performance.

The **C11 — Schema Person for authors** criterion is part of our SEO checklist (335 criteria). Here, you have a **practical** method to check and fix it — with a concrete example.

What exactly this criterion covers

This criterion is discreet… until it blocks SEO performance.

**C11 — Schema Person for authors** (Chapter 3 - Schema.org): name, url, image, sameAs, jobTitle, worksFor, knowsAbout for E-E-A-T

Why it matters (SEO + UX)

Why it matters: it is a technical quality factor (crawl, rendering, indexing). When poorly applied, we often observe: ambiguity (wrong associated query), duplication between pages, or performance loss on loading time.

On volume-generated sites, this criterion also acts as a **safeguard**: a stable rule prevents 1,000 errors at once.

How to check (step by step)

Approach: validation via Search Console (real data). Recommended tool: **Screaming Frog (JSON-LD extraction)**.

  1. Test the URL in Google Rich Results Test.
  2. Validate the JSON-LD (types, mandatory properties, consistency with content).
  3. Check Search Console → “Enhancements” (if available) for errors/warnings.

Tip: first isolate 10 “representative” URLs (top pages + generated pages) before scaling the fix.

How to fix properly

Strategy: repair, re-crawl, and monitor in Search Console.

  • Choose **one main type** (Article / FAQPage / LocalBusiness…) that is coherent.
  • Fill only what you can justify in the content (no invented fields).
  • Validate, then monitor errors via Search Console.

Then: re-crawl 50–200 URLs, then monitor Search Console for 7–14 days (impressions/CTR/indexing).

Concrete example (illustrative)

Example (illustrative):

  • **Context**: service landing page for a hotel in Nice
  • **Before**: No schema (or incomplete JSON-LD).
  • **After**: Added a FAQPage schema coherent with the content.
  • **Note**: Objective: structure information and reduce ambiguity for the engine.

Checklist to tick

  • [ ] Coherent schema type
  • [ ] Respects: sameAs
  • [ ] Mandatory fields present
  • [ ] No unjustified info
  • [ ] Validation OK (0 errors)
FAQ

Frequently asked questions — C11

What is the most common error on “Schema Person for authors”?

Applying an overly generic automatic pattern (same logic on all pages) without adding a differentiating element.

Which tool is fastest for large-scale checking?

For this type of criterion, a crawl (e.g., Screaming Frog) plus targeted verification in Screaming Frog (JSON-LD extraction) is generally the fastest combo.

How to prevent this from happening on 10K generated pages?

Freeze an auto-generation rule (title/structure/schema/URLs) plus add automatic control (crawl or test) before production import.

Ready to go from theory to action?

Validate this criterion with an audit, then deepen the method in the Academy.

Audit with the tool → Learn in the Academy →