Agent Ready Website Audit

ONLINE Agent Ready Website Audit answered an MCP connection on 06 Nov 2026 and introduced itself as agent-ready-by-workpods 0.1.0 (MCP protocol 2025-06-18).

12 tools offered to AI assistants

• check_page · Checks one web page the way search engines, AI answer engines and AI agents read it: indexing (status, robots, canonical), title and meta description, headings and copy, structured data (JSON-LD), links, image alt text and AI readiness. Use
• check_site_files · Reads a site's own files: robots.txt with the verdict for each AI crawler (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended and more), Content-Signal lines, the sitemaps, llms.txt, the agent files
• can_ai_fetch · Answers whether AI crawlers may read one URL, from robots.txt, the robots meta tags (including ones naming the crawler), the X-Robots-Tag header and the HTTP status. Use it when the person asks whether ChatGPT, Claude, Perplexity or Google
• check_agent_readiness · Checks whether AI agents can use a page and its site: labelled forms and buttons, declared WebMCP tools, a Markdown version (content negotiation or a Link header), the agent files and MCP server cards under /.well-known, and whether the dom
• compare_pages · Runs the check_page checks on the person's page and a competitor's page that targets the same search or task, and lists the checks where they differ. Use it when the person asks why a competitor shows up in search or AI answers and they do
• check_local_nap · Checks whether a local business's web page states the business name, address and phone the person gives (NAP consistency), and whether it has LocalBusiness schema, click-to-call links and an embedded Google map. Use it for local SEO questio
• draft_llms_txt · Drafts a starter llms.txt (llmstxt.org) for a site from its home page and sitemap: an H1 with the site name, its description as the summary, and links to its main pages grouped by section, titled from the pages where they were fetched. Use
• draft_ai_crawler_policy · Drafts robots.txt groups for the AI crawlers Agent Ready tracks, and a Content-Signal line, from what the site owner wants: crawlers that index for AI search, crawlers that fetch a page because a user asked, and crawlers that collect traini
• draft_json_ld · Drafts schema.org JSON-LD for a page: Organization, WebSite, FAQPage (questions read from headings that end in a question mark, with the text under them) or LocalBusiness. Values the person gives win over values read from the page. Use it w
• start_site_crawl · Starts a crawl of up to 50 pages of one site, in the background, for the problems one page cannot show: broken links, duplicate titles and descriptions, orphan and deep pages, noindex and sitemap mismatches and soft 404s. Use it when the pe
• get_site_crawl · Reads a crawl started by start_site_crawl. While it runs, result has status (queued or running) and pagesDone; call again in 20 to 30 seconds. Once done, result has the site-wide findings and the crawled pages with their problems, 10 pages
• request_full_audit · Files a request for a full WorkPods audit of a site: how AI answers (ChatGPT, Gemini, Perplexity, Google AI Overviews) mention the brand and its competitors, search rankings and a prioritised fix list, done by WorkPods with paid data. Use i

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.