Is your website
agent ready? — Free Agent Readiness Audit

A free live scan that runs 36 checks across 8 categories: Discovery, Crawl Access, Rendering, Machine-Readable Structure, Freshness Signals, Agent Discovery & Protocols, Authentication & API Quality, and Agentic Commerce. We fetch your robots.txt, sitemap, llms.txt, well-known endpoints, and parse the rendered HTML for schema markup, then return a prioritized list of fixes. No signup required.

PageSpeed measures human visitor performance through Core Web Vitals and render-blocking resources. It does not check whether AI agents can read your robots.txt, parse your schema, or discover your llms.txt. Agent readiness is its own discipline, separate from performance optimization, even though the two overlap on rendering and response time.

Free, unlimited scans, no signup, no account. We fetch only the public surfaces of your domain (robots.txt, sitemap, well-known paths, homepage HTML) which are already accessible to any AI crawler. We do not store your URLs or sell scan data.

Agent readiness is how well your website supports AI agents and crawlers that read, parse, and act on your content. It covers eight layers: whether agents can discover what exists on your site, reach your pages, render the content, parse the structure, detect what’s new, identify your protocols, authenticate against your APIs, and transact through agentic commerce standards. A site can rank well in Google and still be invisible to ChatGPT, Claude, and Perplexity if these layers are misconfigured.

SEO optimizes for search engines that rank pages and send clicks. AEO optimizes for AI answer engines like ChatGPT, Claude, Perplexity, and Google AI Mode that synthesize answers from multiple sources and cite a few. SEO is about ranking. AEO is about being retrieved, cited, and recommended inside an AI-generated answer. The signals overlap on technical hygiene, but the playbook for citations is different from the playbook for rankings.

llms.txt is an emerging standard that gives large language models a curated, markdown-formatted map of your most important content. Think of it as a sitemap optimized for AI reasoning rather than crawling. Major LLMs have begun honoring it, and adoption is accelerating. Yes, you should publish one at yoursite.com/llms.txt.

At minimum, allow the retrieval and search crawlers that determine your visibility inside AI answers: OAI-SearchBot for ChatGPT, Claude-SearchBot for Claude, PerplexityBot for Perplexity, Google-Extended for Gemini and AI Overviews, and Meta-ExternalAgent for Meta AI. Training crawlers like GPTBot and ClaudeBot are a separate decision based on whether you want your content used for foundation model training. Most brands should allow both categories; some publishers choose to block training while allowing retrieval.

GPTBot collects content to train OpenAI’s foundation models. OAI-SearchBot crawls in real time to power ChatGPT’s live search and citations. Blocking one has zero effect on the other. If you want your site cited in ChatGPT answers, OAI-SearchBot must be allowed even if you block GPTBot from training. Anthropic, Perplexity, and Google all run similar two-tier or three-tier separations.

For most brands, no. Blocking the retrieval bots that power citations (OAI-SearchBot, Claude-SearchBot, PerplexityBot) removes you from those AI surfaces entirely. Blocking the training bots (GPTBot, ClaudeBot) is a defensible content-licensing decision but does not affect your real-time citation visibility. The wrong move is a blanket block of every AI user agent, which is the default state of many CMSs and accidentally caps your AI visibility before any optimization work begins.

Start with the three highest-leverage moves: allow major AI retrieval crawlers in robots.txt, publish complete schema.org markup in JSON-LD (Organization sitewide, Article and Product where relevant), and serve content via server-side rendering so agents see it without executing JavaScript. The audit above identifies your specific gaps and ranks fixes by impact. Most are infrastructure changes that ship in days.

Create a plain text or markdown file at the root of your domain at yoursite.com/llms.txt. Outline your most important pages with brief descriptions, organized by topic. Pair it with /llms-full.txt for the long-form expanded version. Goodie’s full platform generates and maintains both automatically from your sitemap and content updates.

Use JSON-LD format inside <script type="application/ld+json"> tags. Start with Organization schema on every page sitewide, then add page-type-specific schema: BlogPosting or Article on editorial content, Product with full price and availability on commerce pages, FAQPage on Q&A pages, BreadcrumbList for navigation hierarchy. Validate with Google’s Rich Results Test. Agents extract these entities more reliably than they parse prose.

Start with the Priority Fixes section. The three items there are ranked by impact, calculated as signal weight multiplied by visibility lift. Most teams ship those three within a week, which moves the overall score 15–30 points. Then work through the Full Audit category by category. For ongoing monitoring across AI surfaces and competitive citation tracking, Goodie’s full platform handles that continuously.