---
title: "AI Readiness Audit for Agencies: Add It to Care Plans"
url: https://hostmy.blog/agency-ai-readiness-audit/
date: 2026-11-14
modified: 2026-11-14
lang: en
author: "Aditya Sharma"
description: "How agencies can package an AI readiness audit as an add-on to a care plan: what it covers, how long it takes, the report, the pricing, and what never to promise."
categories:
  - "RankReady"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2687-1024x538.jpg
word_count: 1444
---

# AI Readiness Audit for Agencies: Add It to Care Plans

An AI readiness audit for agencies is a short, repeatable check of whether a client's WordPress site can be reached, read and quoted by AI assistants. It is delivered as a one-page report and priced as an add-on to a care plan. It suits agencies because the work is mostly the same checks you already run for technical health, with a few new ones, and because clients are starting to ask.

This post is about how to package that audit: what it covers, how long it takes, what the client receives, and what you must not promise. It uses the five layer audit as the method. It is honest about the limits of the evidence, because the fastest way to lose a client's trust is to promise citations you cannot deliver.

![Numbered outline of this post, AI Readiness Audit for Agencies: Add It to Care Plans: 1 Why clients are asking; 2 The checks that carry the audit; 3 How long it takes; 4 How to price and package it; 5 What not to promise; 6 Making the first one easy.](https://hostmy.blog/wp-content/uploads/2026/10/hmb-diagram-2687.png)The route through this post.

## Why clients are asking

Clients read that search is changing, and some have seen AI assistants answer questions about their own market without naming them. The natural question is whether their site is ready. A good agency has an answer that is practical and does not oversell. Google's own [guide to generative AI in Search](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide), last updated on 10 July 2026, says that optimising for it is still SEO. It also lists things you can ignore, such as chunking content , creating unnecessary AI text files and chasing inauthentic mentions. So the honest position has two parts. Most of the work is the fundamentals, and there is a small set of access and structure checks that are worth doing for the other assistants. Both parts fit a maintenance relationship, which is why this belongs with a care plan. [GEO vs SEO on WordPress](/geo-vs-seo-wordpress/) sets out what carries over and what changes.

## What the audit covers

The method is [the five layer AI SEO audit, run by hand with curl](/five-layer-ai-seo-audit/). Package it as five checks, each with a clear pass or fail and a fix.

| Layer | The question | How to check |
| ----- | ------------ | ------------ |
| Access | Can AI crawlers fetch the site, or does something turn them away? | robots.txt, firewall and host settings, and a request with a crawler's user agent |
| Readability | Is the text in the HTML, and not added by a script? | Fetch the page without scripts and look for body text |
| Structure | Is the structured data present, valid and not duplicated? | Count nodes, and run a validator |
| Quotability | Are the key answers short, direct and early on the page? | Read the top posts |
| Visibility | Does an assistant name the client when asked? | The 15 second test, or monitoring |

The first three are technical and can be checked with commands. The fourth is editorial. The fifth is the only one that depends on something outside the site, and it is the one to treat with the most care.

## The checks that carry the audit

Access is where agencies find the most surprises, because a security plugin, a host rule or a CDN setting can turn crawlers away without any message in WordPress. [Test whether AI crawlers can reach your site, in five curl commands](/ai-crawler-test/) is the quickest test, and [your host may be blocking AI crawlers without telling you](/host-blocking-ai-crawlers/) explains the cause. The rules in robots.txt are in [WordPress robots.txt: what to allow, block and test](/wordpress-robots-txt/). The choice between crawlers that train models and ones that search is in [OAI-SearchBot: the crawler behind ChatGPT search](/oai-searchbot-wordpress/).

Readability and structure are quick once you have the commands. [Finding every page an AI cannot parse](/find-pages-ai-cannot-parse/) covers the first, and [schema validator compared: Schema.org vs Rich Results Test](/schema-validators-compared/) covers the second. Count nodes with curl, because the validators will not tell you about duplicates.

We ran this node count on three of our own posts on 12 November 2026. Each returned one Person node, which is correct. The author url inside it, however, redirects to the home page, so a count alone would have passed it. Read the values as well as the number. The [Person schema post](/person-schema-author-wordpress/) shows the commands.

## How long it takes

For one typical blog, the technical checks take under an hour once you have a routine, and the report takes a little longer. A larger site, or one with a store, takes more because there are more templates to test. Test one page of each template, not every page. Use the same approach as the general audit in [website audit: what it is and how to run one yourself](/website-audit-wordpress/), and add these five checks to it.

## What the client receives

A one-page report is enough. It should say what was checked, what passed, what failed, what you recommend and what it would take. Use plain words, and avoid jargon the client will not use.

`AI readiness report for [client], [date]

Access: pass or fail, with the reason.
Readability: pass or fail, with the pages tested.
Structure: pass or fail, with duplicate nodes counted.
Quotability: the three posts most worth improving.
Visibility: what an assistant said when asked, with the date.

Recommended fixes, in order, with effort and owner.`

Date the visibility result, because assistant answers vary and change. It is a sample of one, and the report should say so.

For the visibility check, ask the questions a customer of the client would ask, on more than one assistant, and write down the exact wording and the date. Record what was said about the client, not only whether they were named. Run it again at the next quarterly check, so the client can see the change over time.

## How to price and package it

There are three sensible ways to offer it. As a one-off audit, sold before a care plan or as a project. As a quarterly check inside a higher care tier. Or as an add-on to any tier, billed per audit. The principle is the same as for any maintenance line: state the scope, the response and what is excluded. [WordPress maintenance pricing: how agencies package plans](/wordpress-maintenance-pricing-agencies/) covers packaging in general, and [what a care plan should include](/wordpress-care-plan/) lists the lines a client expects.

Price it from your own costs, not from a list, and include the time to explain the report to the client, which is often the longest part. A cheap audit that takes a long meeting to explain is a bad deal.

## What not to promise

This is the most important section. Do not promise that an assistant will cite the client. No tool controls what an assistant chooses to quote, and Google's own guidance says there is no special markup or file that guarantees inclusion in its AI features. What you can promise is a check of the things that are in your control. Crawlers can reach the site, the text can be read, the structure is sound, and the best pages are written to be quoted.

Also do not sell llms.txt as a ranking lever. Google lists unnecessary AI text files such as llms.txt among the tactics it says you can ignore for Google Search. Our post [llms.txt does not work, and we generate it anyway](/llms-txt-does-not-work/) sets out the honest position. If you add one, add it because it is cheap and tidy, and say that. [AEO tools: what to measure, fix and skip](/aeo-tools-wordpress/) gives the full list of what to be careful of.

## Fitting it into a white-label arrangement

If you use a partner for maintenance, the audit can be part of what they deliver, and you present it under your name. The questions to ask a partner are in [white-label WordPress maintenance: how it works for agencies](/white-label-wordpress-maintenance/). Agree who runs the checks, who writes the report, and who talks to the client about it.

## Making the first one easy

Run the audit on your own agency site first, then on one friendly client. You will find the awkward parts before a paying client does, and you will have a worked example to show. The free [AI Readiness Checker](https://hostmy.blog/plugins/rankready/ai-readiness-checker/) runs 41 checks on a live site and needs no account to see the score. It makes a useful starting point for the conversation with a client, though it is a scan and not a substitute for your own judgement.

## Where Host My Blog fits

Host My Blog makes RankReady, the plugin that does the work behind several of these checks. It offers crawler controls for 29 AI crawlers, a log of their visits, schema that adds to what the SEO plugin writes, and files such as llms.txt. It is free on WordPress.org and runs alongside Yoast, Rank Math, AIOSEO and SEOPress. Agencies that use it get a place to make the fixes the audit finds. It cannot promise that any assistant will cite a client, and no plugin can.

If a client asked you today whether their site was ready for AI search, what would you hand them?