What exactly this criterion covers
This is typically the kind of detail that prevents contradictory signals.
**H1 — Descriptive filename** (Chapter 8 - Images): descriptive-keyword-name.jpg before upload, not IMG_1234.jpg
This is typically the kind of detail that prevents contradictory signals.
The criterion **H1 — Descriptive filename** is part of our SEO checklist (335 criteria). Here, you have a **practical** method to check and fix it — with a concrete example.
This is typically the kind of detail that prevents contradictory signals.
**H1 — Descriptive filename** (Chapter 8 - Images): descriptive-keyword-name.jpg before upload, not IMG_1234.jpg
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 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.
Approach: validation via Search Console (real data). Recommended tool: **Screaming Frog (images)**.
Tip: first isolate 10 “representative” URLs (top pages + generated pages) before scaling the fix.
Strategy: fix the minimum necessary, then stabilize.
Then: recrawl 50–200 URLs, then monitor Search Console for 7–14 days (impressions/CTR/indexing).
Example (illustrative):
Applying a too generic automatic pattern (same logic on all pages) without adding a differentiating element.
For this type of criterion, a crawl (e.g. Screaming Frog) + targeted verification in Screaming Frog (images) is generally the fastest combo.
Freeze an auto-generation rule (title/structure/schema/URLs) + add automatic control (crawl or test) before production import.
Validate this criterion with an audit, then deepen the method in the Academy.