Ask HN: Would you use an ESLint-like tool for SEO that fails your CI/CD build?

I’m building Indxel — an open-source SEO infrastructure for developers (npm package + CLI + MCP server for AI agents).
The core idea: SEO breaks silently. You delete a page, rename a route, forget an og:image — nothing tells you. Your traffic drops weeks later and you have no idea why.
Indxel treats SEO like code quality. npx indxel check runs 15 validation rules against your pages (meta tags, Open Graph, structured data, canonical URLs, etc.) and gives you a score. npx indxel check –ci fails your build if something’s broken.
It also crawls your live site, checks your sitemap against actual pages, verifies that referenced assets (og:image, favicon) actually return 200, and does keyword research via Google Autocomplete — all from the terminal.
The MCP server exposes all of this to AI agents (Claude, Cursor) so they can audit SEO while working on your code.
Stack: TypeScript SDK, Commander CLI, MCP protocol. MIT licensed.
My question: is this a real pain point for you, or do you just fix SEO manually when you notice it? Would CI/CD integration change your workflow?