Published Site
Runtime truth
- SEO + metadata
- Accessibility + structure
- Public behavior
╭──────────────────────────────────────────────────────────────╮ │ PUBLISHED SITE DESIGNER STATE POLICY SNAPSHOT │ │ │ │ │ │ │ └──────────┬──────┴──────┬──────────┘ │ │ ANALYZER MCP REVIEW ARTIFACT │ │ observable • queued • versioned • manual-bounded │ ╰──────────────────────────────────────────────────────────────╯
This case study explains how the Webflow Site Analyzer MCP was created, the review problem it solves, and the architectural pattern it demonstrates for other system architects. The key move was treating review as a governed MCP system across three surfaces: published pages, Designer-only metadata, and external policy that changes over time.
Architecture View
The analyzer only lands when runtime evidence, authoring metadata, and policy versioning meet in one observable system.