geo-audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIER | No | Selects the server tier. `free` exposes check_robots, check_sitemap, check_meta, and run_audit. `paid` exposes all six tools, including check_schema and check_ai_files. | free |
| FREE_AUDITS_PER_DAY | No | Changes the daily limit for free full audits. The default is three full audits per UTC day. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_robotsB | 检查 robots.txt 对 OAI-SearchBot、GPTBot、ClaudeBot 的规则。 |
| check_sitemapC | 检查 sitemap 的数量、lastmod 与 noindex 页面。 |
| check_metaC | 检查 title、description、Open Graph、canonical 与 hreflang。 |
| run_auditB | 运行 GEO 可见度诊断并生成 Markdown 报告。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.