The account began with contradictory signals: aggressive CDN caching for readers, stale schema dates for crawlers, and newsletter CTAs that obscured primary text in mobile renders. Teams fixed access first—robots, status codes, and parameter hygiene—before touching copy experiments.
Editors adopted a lightweight “answer-first” checklist for flagship explainers. Engineers shipped Organization and Article JSON-LD templates tied to CMS fields rather than hand edits.
KPIs mixed classic SEO (crawl errors, indexed templates) with qualitative monitoring of answer surfaces. The lesson: sustainable GEO work mirrors good product delivery—shared definitions of done and fewer hero projects.