Free AEO Audit: How to Test Your Website's AI Readiness in 60 Seconds

If you're guessing whether AI systems like ChatGPT, Claude, and Perplexity can find and cite your content — you're probably losing traffic and citations you don't even know you're missing.

An AEO audit changes that. In 60 seconds, using a free Chrome extension, you can see exactly how AI answer engines evaluate your pages and get a prioritized list of what to fix first.

This guide walks you through every step: what an AEO audit checks, how to run one, what every score component means, and how a single afternoon of targeted fixes drove a 23-point score improvement.

What Is an AEO Audit — and Why Does It Matter Now?

AEO stands for Answer Engine Optimization — the practice of making your website's content visible, trustworthy, and accessible to AI systems that provide direct answers rather than lists of links. An AEO audit measures how well your pages meet those requirements.

Traditional SEO audits focus on ranking signals: page speed, backlinks, keyword density — the factors that influence where you appear in Google's search results. An AEO audit focuses on citation signals — the factors that determine whether an AI answer engine will trust and reference your content in its responses.

The distinction matters because AI answer engines use fundamentally different signals than traditional search engines. A page can rank #1 on Google while being completely invisible to ChatGPT, Claude, or Perplexity. The reasons are usually structural: AI crawlers blocked in robots.txt, missing structured data, no authorship information, or content formatted in ways that AI systems can't parse into a citable answer.

As AI search grows — and it's growing fast — the cost of not knowing your AEO status is increasing every quarter. To understand the five underlying pillars that make up your AEO score, see our detailed breakdown. This article focuses on the practical audit process.

Step 1 — Install AEO Tester (Takes 30 Seconds)

AEO Tester is a free Chrome extension that audits any webpage for AI readiness directly from your browser. No account required. No setup. No configuration needed.

To install it:

1. Click the link in the CTA below to open the Chrome Web Store listing
2. Click "Add to Chrome"
3. Confirm the installation when prompted

The extension icon appears in your Chrome toolbar immediately after installation. That's all there is to it — you're ready to run your first audit.

Start your free AEO audit now — install AEO Tester from the Chrome Web Store and run your first AI readiness test in under a minute.

Step 2 — Run Your First AI Readiness Test

Navigate to any page on your website you want to audit. Start with your most important pages: your homepage, your main product or service page, or your highest-traffic blog post. These are the pages where AI visibility has the most direct impact on your business.

Click the AEO Tester icon in your Chrome toolbar. The extension scans the current page — analyzing its HTML, meta tags, schema markup, robots.txt configuration, and other signals — and returns your full AEO audit within seconds.

You'll see:

• An overall AEO score from 0 to 100
• A breakdown of each individual score component
• Color-coded indicators: green (passing), orange (needs improvement), red (failing)
• Specific details about what each component found on your page

The breakdown is the most valuable part. Not all score components are equally important — some failures are critical, others are minor. The detailed view lets you prioritize which issues to address first rather than treating every finding as equally urgent.

Step 3 — Understanding Each Check

AEO Tester runs 26 automated checks, grouped below by what they protect. Each check carries a point weight, shown in brackets, and the weights tell you what matters most: blocked AI crawlers cost far more than a missing Twitter card.

1. Crawler Access (31 points)

If AI crawlers can't reach or index a page, nothing else in the audit matters.

• AI bot crawlability (12): Reads your robots.txt for rules affecting GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, OAI-SearchBot (ChatGPT search), Google-Extended and other AI crawlers, including crawl delays. A wildcard rule can block all of them by accident.
• Indexability (8): Validates the canonical tag and looks for noindex/nofollow meta robots and soft-404 pages.
• llms.txt (6): Looks for an /llms.txt file, checks that robots.txt doesn't block it, and gives a bonus point when it follows the llmstxt.org format. It's a proposed standard that no major AI platform has confirmed reading, so treat it as low effort rather than high impact. See what llms.txt is and whether you need one.
• Sitemap (5): Finds your sitemap, checks that robots.txt references it and that the current page is listed.

AI bot crawlability is one of the heaviest checks in the audit, second only to structured data. See our complete guide on checking AI crawler access for a full breakdown of every major bot and what to allow or block. To check a domain's robots.txt on its own, use our free AI robots.txt checker.

2. Structured Data (20 points)

• Structured data (15): Detects JSON-LD and weights it by type. FAQPage carries the most weight, followed by HowTo, Product and Organization, then Article, with supporting types like BreadcrumbList and Person worth the least.
• Schema validation (5): Checks that the JSON is valid, required properties are present and values are properly formatted.

Structured data is how you make content machine-readable: without it, AI systems have to guess what type of content a page contains and who produced it. Our free schema markup validator checks each schema type for the properties AI models use.

3. Content and Structure (26 points)

• Semantic headings (8): Exactly one descriptive H1, a logical H1 → H2 → H3 hierarchy with no skipped levels, and no generic headings like "Home" or "Overview".
• Content quality (5): Word count, paragraph structure and the use of lists for structured content.
• Image alt text (5): The share of images with descriptive alt attributes. AI crawlers can't see images, so alt text is the only way they learn what an image shows.
• Internal linking (4): The number and variety of internal links and the quality of their anchor text. Links help AI understand how your pages relate to each other.
• Semantic structure (4): Semantic HTML elements (main, nav, article), ARIA landmarks, form labels and skip links.

AI systems use heading structure to split a page into sections and match them to questions. Our free heading checker shows your full heading hierarchy.

4. Trust and Freshness (12 points)

• Author and E-E-A-T signals (5): An identified author, found in Person or Article.author schema, author meta tags or a visible byline, plus signs of expertise such as a bio or profile. AI systems prefer citing identified, credible authors over anonymous pages.
• Content freshness (5): datePublished and dateModified in JSON-LD, article:published_time/article:modified_time meta tags, or <time> elements.
• HTTPS (2): The page is served over HTTPS without mixed-content resources.

5. Page Metadata (22 points)

• Meta title (5): Present, 50–60 characters, and not a generic default.
• Meta description (5): Present, around 150–160 characters, and not duplicated or generic.
• Open Graph (3): og:title, og:description, og:image, og:url and og:type.
• Twitter cards (3): twitter:card, twitter:title, twitter:description and twitter:image.
• Language tags (3): An html lang attribute, plus hreflang tags for international versions.
• Mobile viewport (3): A viewport meta tag with width=device-width and an initial scale.

6. Agent Readiness (27 points)

AI agents don't just read pages, they fetch and act on them. These checks cover what agents need that a human visitor doesn't.

• Server-rendered content (6): Compares the raw HTML with the page after JavaScript runs. Most AI crawlers don't execute JavaScript, so content that only appears after it runs is invisible to them.
• Markdown for agents (5): Whether the site can serve a Markdown version of the page, which costs an agent far fewer tokens than HTML.
• Content Signals (3): Whether robots.txt declares what AI may do with your content once fetched: search, ai-input (grounding answers) and ai-train.
• HTTP behavior (3): Unknown URLs return a real 404 instead of a "soft 404" page, and no X-Robots-Tag: noindex header hides the page.
• Agent-usable controls (4): Buttons have accessible names, links go somewhere real, click handlers sit on interactive elements, and personal-data fields declare autocomplete.
• Agent protocol discovery (6): Well-known files that advertise tools and APIs to agents, such as an MCP server card, A2A agent card or OpenAPI document. This check only counts on sites that expose an API; for a blog or brochure site it's marked not applicable.

Step 4 — Interpreting Your Overall Score

Your overall AEO score is the share of available points you earned, from 0 to 100. Checks that don't apply to your site, like agent protocol discovery on a blog, are left out of the total rather than counted as failures. AEO Tester labels the result like this:

Few sites reach the top band on their first audit. In our study of 10 well-known websites, only one was rated Ready for AI. The goal isn't a perfect 100; it's getting your most important pages to the point where AI systems can confidently cite them.

Case Study: From 47 to 70 — A 23-Point AEO Score Improvement

To show what targeted AEO fixes look like in practice, here's a real-world example of an audit and the changes that drove a 23-point improvement. It was measured with an earlier, 14-component version of AEO Tester's scoring, so the per-fix points below won't match today's 26-check weights exactly, but the priorities are the same.

Starting Score: 47/100

A content-focused website ran its first AEO audit and found four critical failures:

• AI Bot Crawlability: Failing. The site's robots.txt contained a wildcard Disallow: / rule inherited from a staging environment setup years earlier. GPTBot, ClaudeBot, and PerplexityBot were all blocked.
• Structured Data: Failing. No JSON-LD schema markup existed on any page. AI systems had no machine-readable information about the author, publication dates, or content type.
• Author Attribution: Failing. Articles had no visible bylines and no Person schema identifying the author.
• Publication Dates: Failing. No datePublished or dateModified in schema or visible HTML. AI systems treating freshness as a signal had no way to evaluate content recency.

The site was also missing og:description and og:image on most pages, contributing to a low Open Graph score.

The Fixes (Less Than Two Hours of Work)

Fix 1 — Updated robots.txt: Removed the problematic wildcard disallow rule and added explicit Allow: / directives for GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, and Google-Extended. +8 points.

Fix 2 — Added Article schema: Implemented JSON-LD Article schema on all blog posts, including headline, datePublished, dateModified, author (with Person sub-schema), and publisher fields. +7 points.

Fix 3 — Added author bylines: Added author names and role labels to each article page, linking to author profiles on social platforms. +4 points.

Fix 4 — Completed Open Graph tags: Added missing og:description and og:image to all pages that lacked them. +4 points.

Result: 47 → 70

The score jumped 23 points in a single afternoon. None of the fixes required a site redesign or content rewrite — they were targeted, structural improvements that an AEO audit surfaced in seconds.

What to Do After Your Audit

Once you have your AEO score and component breakdown, here's how to turn the results into a prioritized action plan.

Fix Critical Failures First

Red-flagged components — blocked AI crawlers, missing HTTPS, absent structured data — have the highest impact on your overall score and your actual AI visibility. Address these before anything else. A single critical failure can suppress your score by 8–10 points and may be preventing AI systems from indexing your content entirely.

Group Fixes by Effort Level

Some improvements take five minutes: adding a meta description, updating a canonical tag, completing missing Open Graph tags. Others require development time: implementing structured data sitewide, updating robots.txt configuration, adding author schema to legacy content. Plan your quick wins first to build momentum, then schedule the technical work.

Audit All Your Key Pages

Run AEO Tester on each of your important pages, not just the homepage. Your product pages, top blog posts, and landing pages may have entirely different scores and different issues. A homepage that scores 75 doesn't mean your other pages are equally optimized.

Verify Every Fix

After making changes, re-run the audit to confirm your score improved and no new issues appeared. AEO Tester gives you instant feedback — you don't need to wait for a crawler to revisit your site. The audit-fix-verify loop is the fastest path to meaningful improvement.

Prioritize Freshness Over Time

Once your structural signals are in place, content freshness becomes an ongoing factor. Update publication and modification dates in your schema whenever you revise content. AI systems actively prefer recently updated sources — a page refreshed last month will outperform an identical page last updated two years ago.

The goal isn't optimizing every page to perfection. It's ensuring the pages that matter most to your business are meeting the threshold where AI answer engines will confidently cite them. For most sites, getting key pages to 80 or above (Nearly Optimized) is a realistic target that produces measurable visibility improvements within weeks of implementation.