All resources
Agency workflow·Beginner·6 min

Audit a client's AI readiness in 10 minutes

Before you promise a client more AI visibility, you need to know what's holding them back. The GEO Audit turns a site into a 0–100 readiness score with a prioritised fix list in a single pass — and now carries a separate Agent Readiness sub-score for the emerging class of AI agents. Here's how to run one and turn it into a deliverable.

What you'll be able to do: A prioritised, plain-language AI-readiness report for any client site — with fixes you can hand to a developer.

  1. 1

    Run the GEO Audit

    Open the client's AI Visibility project, go to GEO Audit, and the domain is pre-filled from their saved website. Click Run audit — CrunchJunkie fetches robots.txt, the homepage, llms.txt and the sitemap the same way an AI crawler does (plain HTTP, no JavaScript) and scores concrete signals into one number.

  2. 2

    Read the score and categories

    The composite 0–100 score weights five categories: AI crawler access, content accessibility / SSR, structured data, technical hygiene and llms.txt. A high score means the site is well-positioned to be cited — it's a readiness measure, not a promise of mentions, which you track separately on the Visibility tab.

  3. 3

    Work the prioritised fixes

    The audit ranks every non-passing check by the points it would recover — highest-impact first. Each comes with a plain-language explanation, and "Draft the fix with Crunch" writes a concrete, copy-pasteable remediation grounded in that specific finding, ready to drop into a ticket.

  4. 4

    Check the Agent Readiness sub-score

    Alongside the GEO score is a separate Agent Readiness sub-score: can real-time AI agents fetch the site, read it without JavaScript, and parse a breadth of structured data. It's deliberately kept out of the main score because the category is still emerging — but it's a forward-looking differentiator few audits offer.

  5. 5

    Turn it into a client deliverable

    The audit history saves every run, so you can re-audit after the client ships fixes and show the score move over time. Drop the score, the prioritised fixes and the Draft-the-fix remediations into a report or a short email — a credible, specific action plan rather than vague advice.

Frequently asked

It fetches the site as an AI crawler does and grades: whether robots.txt and the CDN allow the AI crawlers, whether key content is server-rendered (not JavaScript-only), whether valid schema.org structured data is present, technical hygiene (sitemap, canonical, titles, HTTPS), and llms.txt. Present-but-incomplete schema is flagged with the exact missing properties.

The GEO score is about being crawled and cited by AI answer engines. The Agent Readiness sub-score is about the newer class of real-time AI agents that fetch on a user's behalf — whether they can reach the site, read it without JavaScript and parse its structured data. It's shown separately and doesn't affect the GEO score.

Yes. Every run is saved to the audit history with its date and score, so after a client applies fixes you re-audit and the history strip shows the improvement — a clean before-and-after for your report.

No, and we're deliberate about that. The score measures readiness — that the technical barriers to being cited are removed. Whether the brand is actually mentioned is tracked separately by Visibility % on the AI Visibility tab. Readiness is necessary but not sufficient; pair the two for the full picture.
GEO Audit docs

Try it on your own brand

AI search visibility and white-label reporting in one console — put this playbook to work inside the 14-day free trial.

Start free