geo-lint
@ijonis/geo-lint is a Node.js/TypeScript CLI and programmatic linter for SEO + GEO (Generative Engine Optimization). It scans Markdown/MDX (and supports custom adapters for other content sources), reports structured violations as JSON (including file/field/line plus suggestion/fixStrategy), and can be used by AI agents to iteratively fix violations until the output is clean.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Primarily local tooling with no described network calls/auth. TLS enforcement is not applicable to typical local execution; score reflects lack of evidence about any remote fetching. Dependency list is very short in the provided manifest (gray-matter, jiti) but no CVE/security audit evidence is provided. No secret handling guidance is shown; assuming typical local CLI usage, but agents should avoid logging content that may include sensitive text.
⚡ Reliability
Best When
You have a content repo (Node >= 18) with Markdown/MDX and want deterministic, agent-friendly lint rules with machine-readable fix suggestions.
Avoid When
You need a hosted service with guaranteed uptime/SLA, or you require official REST/GraphQL/webhook interfaces; this appears to be primarily local CLI/library tooling.
Use Cases
- • Lint and auto-fix SEO/GEO issues in Markdown/MDX content
- • Integrate deterministic content QA into CI pipelines
- • Provide structured violation output (JSON) for agent-driven remediation loops
- • Create/update geo-lint configuration and run rule-specific audits/reports
- • Extend linting to other CMS/content formats via custom adapters
Not For
- • Real-time web crawling/hosting runtime validation
- • Security/compliance scanning of sensitive data
- • Authentication/authorization-protected APIs or SaaS workflows (appears to be local tooling only)
- • Batch processing of non-text/binary content without appropriate adapters
Interface
Authentication
No authentication is described; it appears to be local tooling run via CLI/Node library.
Pricing
No pricing details in provided content; appears to be an MIT open-source package.
Agent Metadata
Known Gotchas
- ⚠ Agent must stop on empty JSON array [] per docs; if an agent ignores this, it may loop unnecessarily.
- ⚠ Auto-fixes may alter formatting/structure; agents should preserve author voice as recommended.
- ⚠ Custom adapters require correct mapping to ContentItem objects; incorrect adapters will lead to misleading violations.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for geo-lint.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.