Audits a public website for AI-assistant readiness: robots.txt rules, llms.txt drafting, and citable content gaps.
What you can do
Run a GEO readiness check on a public page and get weighted blocking, important and to-decide gaps across six parts
Read a site's robots.txt and see, robot by robot, whether AI crawlers and user-triggered fetchers may read the site
Draft an llms.txt from the site's home page and sitemap, grouped by section, and review an existing one
Retrieve the vendor's paid GEO module offer, including what it applies and measures, with prices and a payment link
When to use it
Useful when you want to check whether a site is readable and citable by AI assistants, diagnose robots.txt blocks for specific AI crawlers, or produce a first llms.txt draft before deciding on paid tooling.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. It works on publicly reachable sites, so the target site must be accessible over the web.
Before you install
One tool returns a commercial offer with prices and a Stripe payment path, so treat it as sales material rather than neutral advice. The audit and draft tools read public pages and robots.txt of whatever site you name, which discloses that site to the provider.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.seorecords%2Fgeo-seo-records/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Runs the GEO SEO Records engine on a public page and returns the gaps, weighted blocking / important / to decide, across six parts: the door (robots.txt rules for the robots that read for a person), the map (llms.txt present and verifiable), the answer (does the page answer under its title, declared questions), the citable (figures with a source or a date), the publisher identity, and the structure (blocks that stay true when quoted alone). Free. Docs: https://seorecords.com/assistants
Parametersurlrequired
open_robots_txt_to_ai
Open robots.txt to AI assistants
Reads the site's robots.txt and tells, robot by robot (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, Claude-SearchBot, PerplexityBot, Perplexity-User, DuckAssistBot, Meta, Common Crawl, Google-Extended, Applebot-Extended), whether it may read the site, separating robots that read for a person (live) from robots that harvest for training. Returns the corrected robots.txt that lets the live readers in while keeping the site's existing rules, ready to paste. Docs: https://seorecords.com/assistants
Parametersurlrequired
draft_llms_txt
Draft the llms.txt of a website
Builds an llms.txt for a website from facts read on it — the site name and description from its home page, then pages from its sitemap with their titles and meta descriptions, grouped by section — and reviews the existing llms.txt if there is one (declared name, links, claims no machine can verify). The draft is ready to edit and publish at /llms.txt. Docs: https://seorecords.com/assistants
Parametersurlrequired
get_geo_offer
GEO SEO Records: offer and payment links
Returns the GEO SEO Records module (WordPress, PrestaShop, network edge; from €490 for a year): what it applies (door, map, answer, publisher) and what it measures (assistant reads certified by IP range, demand read in the log, paying pages joined to revenue), with prices and secure Stripe payment links. Docs: https://seorecords.com/assistants
Parameterslanguage
Version history
1
v1.0.0LatestOct 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.