
A two-phase lint for catching factual drift in hand-maintained static HTML SEO content
Original: I built a lint that caught 3 tax-rule lies my manual sweep missed — a pattern-based safety net for hand-maintained SEO
Short summary
The author discovered that pre-rendered static HTML mirrors on their Blazor WASM site had drifted from correct razor sources, showing false Indian tax claims about Section 80CCD(1B). After a manual fix missed three additional pages, they built a two-phase PowerShell lint: first finding suspicious co-occurrences of deduction names near 'New Regime', then filtering out safe-indicator words like 'disallow' or 'not allowed'. The approach catches factual drift in hand-maintained SEO content that regex alone cannot.
- •Static HTML mirrors drifted from correct razor sources, showing false Indian tax claims across multiple pages
- •Manual sweep missed three additional pages with identical errors
- •Two-phase lint pattern: wide-net co-occurrence detection, then safe-indicator filtering to exclude negations
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



