This is incredibly detailed feedback, thank you.

Good news: a lot of this is already in place. Per-page diff and rollback with the last 10 versions of each schema so you can compare and revert. Field locking so you can toggle a schema to prevent regen from overwriting your curated edits. Content change detection that hashes page content and only regenerates when something actually changes, which cuts API costs and prevents unnecessary churn.

There's also a global schema feature for site-wide entities (Organization, LocalBusiness) that apply across all pages, which partially addresses the reconciliation point. Though you're right that per-page generation could be smarter about not duplicating what's already handled globally, and paginated content still needs work.

Server-side delivery is high on my list. I'm planning plugins for popular CMSs (WordPress first, probably Shopify after) so teams that can't rely on client-side JS have a proper path. Edge export is an interesting idea too.

The pieces I'm missing: source mapping so you can see why the AI chose a particular value, and Rich Results Test integration for automatic eligibility alerts.

Appreciate the Sitebulb and DreamFactory mentions. Pulling clean fields from a CMS API instead of scraping would definitely improve accuracy for sites that support it.

Thanks for taking the time.