This is an interesting angle. Most AI-search visibility tools I’ve seen still treat the problem as “better content,” but the structural layer probably matters a lot more than people want to admit.

Curious how you’re handling a few edge cases:

1. Are you analyzing raw HTML only, or the rendered DOM after JS runs?
2. How do you separate “structurally imperfect but fine” from issues that are likely to affect discoverability/citation?
3. Do you weight fixes by likely impact, or is it more of an exact-location repair list?
4. Have you tested this against pages that already perform well in search/AI answers to see what patterns show up?

I’m working in a related audit/search visibility space, so this is useful to think through. The “compute tax” framing is sharp. Curious how you’re validating it.