Case studies
ProfileArchitect ships on production infrastructure. Outcome metrics publish after formal re-baseline; until then we document implementation depth and baseline dates—not claimed SERP lifts.
REFERENCE IMPLEMENTATION (V1)
Ben Yeoh — live executive profile site
ProfileArchitect ships on production infrastructure, not mockups. benyeoh.com is the canonical proof of delivery: multi-tenant Next.js, Supabase-backed SEO, GEO, and AEO, and JSON-LD wired from published rows—not hardcoded per page.
Entity graph: Person on benyeoh.com (methodology and guides) ↔ Organization at profilearchitect.co (practice: audits and engagements). Pillar guides and thought leadership stay on benyeoh.com; hire and apply intent routes to ProfileArchitect.
Stack
- Next.js App Router, host-based tenant routing (studio + client sites)
- ProfileArchitect-Core: pages, SEO metadata, geo schemas, FAQ AEO in Supabase
- Structured data: Person, WebSite, WebPage, Service, FAQPage where published
- ISR with secured on-demand revalidation after Studio edits
Timeline
- Phase 0 baseline — 2026-10-02: Google SERP and AI prompt battery (ChatGPT, Gemini, Perplexity) before structural and content changes.
- Phase 1 technical — entity-aligned Person/WebSite, host-aware sitemap and robots, unified metadata pipeline.
- Content pillars — executive footprint guides on benyeoh.com (ongoing); studio documents process and delivery, not competing pillar URLs.
Measurement (deferred)
Outcome metrics—Search Console impressions, AI answer shifts, audit volume—publish only after a formal Phase 0 rebaseline on the same prompt battery. Until then, this case study documents implementation and baseline date, not claimed lifts.
Additional client studies
Anonymized engagement summaries will publish here as approvals allow. Engagements begin with a qualified audit.
Request an audit