geo-audit
Related Servers
Alternatives to geo-audit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAudits public websites for AI crawler access, public technical signals, and deployment readiness. Includes a focused path to the full readiness report when deeper remediation guidance is needed.MIT
- AlicenseNot gradedqualityFmaintenanceEvaluates any website's AI visibility with 15 checks across crawlability, structure, content, and connectivity, and provides actionable fixes.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.373 npm2MIT
- AlicenseAqualityCmaintenanceCheck whether a website is visible to AI search engines (ChatGPT, Perplexity, Claude, Google AI Overviews). Returns a 0-100 readiness score, a grade, and a specific fix for each gap. Dependency-free, no API keys.21MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform instant SEO audits, check robots.txt, sitemaps, and AI crawler access for any URL without API keys.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to run read-only technical SEO and AI-search-readiness audits on any URL via GET/HEAD requests. Checks on-page elements like titles, meta descriptions, headings, canonical and Open Graph tags, JSON-LD validity, alt text and link health, plus robots.txt, sitemaps and llms.txt for crawler access.3MIT
TDQS
Scored across 4 tools
Each tool targets a distinct audit surface: robots.txt rules, sitemap structure, meta tags, and a full aggregate audit run. The only overlap is run_audit vs. the individual checks, but that aggregate-vs-detail pattern is clear and intentional, so an agent can easily pick the right tool.
All four tools follow a consistent verb_noun snake_case pattern (check_robots, check_sitemap, check_meta, run_audit). The single verb deviation (run_audit) is semantically appropriate for an aggregate action.
Four tools is a tight, well-scoped set for a GEO audit, with each tool earning its place. However, the surface is slightly thin—structured-data or content-readability checks would be natural additions—so it's reasonable rather than ideal.
The set covers the core technical GEO checks (robots/bots, sitemap, meta/OG/canonical/hreflang) plus an aggregate report generator, giving a coherent lifecycle. Minor gaps exist—e.g., structured data (JSON-LD/schema.org) and llms.txt or page-content readability checks are often central to GEO and are absent.