I14 — Chapter 9 - E-E-A-T

Criterion I14: Documented Process — guide + checklist

PART 1 - Fundamentals Chapter 9 - E-E-A-T Keyword : processus documenté

This is often seen as an error on mass-generated sites.

Criterion I14 — Documented Process 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 is often seen as an error on mass-generated sites.

I14 — Documented Process (Chapter 9 - E-E-A-T): Detail steps, tools used, methodology

Why it matters (SEO + UX)

Why it matters: it is a UX point that eventually translates into SEO. When poorly applied, we often observe: ambiguity (wrong associated query), duplication between pages, or loss of performance on Core Web Vitals.

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

How to check (step by step)

Approach: check by crawl (list + export). Recommended tool: Your WG Analyzer.

  1. Open the source code and locate the concerned element (tag/structure).
  2. Check the hierarchy and consistency with H1 + intro.
  3. Run a crawl to detect pages violating the criterion.

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

How to fix properly

Strategy: fix the minimum necessary, then stabilize.

  • Rewrite the plan: clear H1, H2 = sub-questions, H3 = details.
  • Add a differentiating element (scope, method, example) to avoid duplication.
  • Check consistency with the intent (info / comparison / action).

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

Concrete example (illustrative)

Example (illustrative):

  • Context: FAQ page for auto garage in Algiers
  • Before: generic H1 + sections without hierarchy (incoherent H2/H3).
  • After: intent-oriented H1 + H2 by sub-questions (case: FAQ page — auto garage).
  • Note: Goal: make the plan scannable and aligned with intent.

Checklist to tick

  • [ ] Matches the intent
  • [ ] Respects: detail steps
  • [ ] Unique
  • [ ] Concrete examples
  • [ ] Natural keywords
FAQ

Frequently asked questions — I14

What is the most common mistake on “Documented Process”?

Fixing an isolated page without correcting the template/import: the error returns on the next generation.

What tool is the fastest to check at scale?

For this type of criterion, a crawl (e.g. Screaming Frog) plus targeted verification in Your WG Analyzer 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 →