Skip to main content
Glama
geo-seo-readiness-lite

geo-seo-readiness-lite

Related Servers

Alternatives to geo-seo-readiness-lite

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Checks whether a website is readable and citable by AI search engines — llms.txt, Schema.org structured data, AI-bot access in robots.txt, content freshness, answer directness, E-E-A-T signals, plus a LocalBusiness Rich Results validator. Free, no API key, remote Streamable HTTP.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that checks a website's AI-search (GEO) readiness: robots.txt access for 16 AI crawlers (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot, Google-Extended, Bingbot...), JSON-LD schema, llms.txt, sitemap and basic SEO tags. Python, stdio, MIT.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      3
      73 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Checks a site for AI crawlers: which of 11 AI crawlers its robots.txt lets in, whether its llms.txt follows llmstxt.org, and what its home page says without scripts. Findings with evidence; no scores, no model calls, no telemetry.
      5
      49 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Check 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.
      2
      5 npm
      1
      MIT

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation4/5

    The four granular checks target clearly distinct artifacts (robots.txt, /llms.txt, page HTML structured data, XML sitemap), so they are easy to tell apart. quick_readiness_report overlaps in purpose with the other four because it aggregates them, but its description explicitly frames it as an all-in-one check, making the boundary understandable rather than confusing.

    Naming Consistency4/5

    All names use snake_case and four of five follow a clean verb_noun pattern (check_ai_crawler_access, check_llms_txt, extract_structured_data, check_sitemap). quick_readiness_report deviates by using an adjective instead of a verb, but it remains readable and clearly signals its composite role.

    Tool Count5/5

    Five tools is well-scoped for a 'lite' readiness checker: one convenient aggregate plus four focused checks, each earning its place. There is no bloat or thin single-tool surface.

    Completeness4/5

    The surface covers the declared readiness areas fully: AI crawler access, llms.txt, structured data/canonical, and sitemap, plus a prioritized aggregate report. Minor gaps remain, such as page-level meta robots/noindex checking and broader indexability diagnostics, but these are reasonable omissions for a lite tool.