AEO StrategyLLM InvisibilityMagnetic Messaging Framework

How do we audit our website for what AI assistants say about us?

Greg Rosner

By Greg Rosner

Founder of PitchKitchen · Author of StoryCraft for Disruptors

· 7 min read

Hero image for How do we audit our website for what AI assistants say about us?

TL;DR

To audit your website for what AI assistants say about you, ask the assistants first and read your site second. Write five category-level questions in your buyer's words, run them across ChatGPT, Claude, Perplexity and Google's AI Overview in a logged-out session, and log how you're described, who's named beside you, and which URLs get cited inline. Then trace every claim back to a source sentence on your own site. Anything you can't source was invented or borrowed. Four patterns explain nearly every result: a recall gap, a distinctiveness gap, a source gap, or a format gap. Only one of the four is technical. When we ran this on ourselves across 50 tracked prompts, nine of our ten most-retrieved pages were listicles or comparisons and no long-form essay made the list, out of more than 250 posts.

You audit your website for what AI assistants say about you by asking the assistants first and reading your site second. Open ChatGPT, Claude, Perplexity and Google's AI Overview, type the questions your buyers actually type, and record the answers word for word: how you get described, which competitors get named beside you, and which pages get cited. Then go back to your own site and find the sentence that produced each answer. The gaps show up where no such sentence exists.

That's the whole method, and it takes an afternoon. What makes it hard isn't the procedure. It's that most audit advice points you at the wrong layer. Search "AI visibility audit" and you'll get a crawl checklist: schema markup, robots.txt, an llms.txt file, render-blocking JavaScript, whether your content sits behind a client-side render. Those checks tell you whether a machine can read your site. They tell you nothing about whether it found anything worth repeating.

Do we even need to run this audit?

Answer one question before you spend the afternoon. Take the sentence your best customer used when they described their problem to you, before they knew your company existed. Type that into ChatGPT as a question. If your name doesn't come back, run the audit. If it does come back, run the audit anyway, because being named and being recommended are different outcomes and the difference is the whole game.

Skip it if you sell to a market of forty named accounts who all know you personally, or if you're pre-revenue with no public footprint for an engine to read. Everyone else in the $5M to $75M range is being summarized by these systems right now, whether or not anybody on the team has looked.

What are we actually auditing, the site or the answer?

Both, in that order, and the sequence matters more than any single check. An engine doesn't rank your pages the way search did. It compresses everything public about you into a few sentences, keeps whatever is distinctive, and drops whatever is vague. We've written before about why AI describes B2B companies inaccurately, and the mechanism is the same one at work here: generic material gives the model nothing to hold onto, so it fills the space with category boilerplate or a competitor's language.

That's why this is a comprehension audit. You're measuring what survived the compression. A crawl audit asks whether the machine could reach your words. This one asks what it did with them.

An AI audit measures one thing: whether your website gave the machine anything worth repeating.

... Greg Rosner, PitchKitchen

How do we run the audit in an afternoon?

Six steps. Use a spreadsheet, one row per engine per question. Don't delegate the reading, because the value is in seeing your own company described by a stranger who owes you nothing.

  1. 1Write down five questions in your buyer's words, not your keywords. Category-level, no brand names. "Who helps a healthtech company fix messaging that isn't landing with hospital buyers" beats "B2B messaging consultant." If you can't write five, that's a finding on its own.
  2. 2Run each question in a logged-out or temporary session across ChatGPT, Claude, Perplexity and Google's AI Overview. A logged-in session carries your history and will flatter you.
  3. 3For each answer, log three things verbatim: how you were described or that you were absent, which companies were named beside you, and which URLs the engine cited inline. Inline citations matter more than what merely got crawled.
  4. 4Now ask the branded version at each engine: "What does [your company] do, who is it for, and when should someone choose it over alternatives?" This separates a recall gap from a description gap. Most companies pass this one and fail step 2, and the reason that happens is covered in detail here.
  5. 5Trace every claim in every answer back to a specific sentence on your site. Open the page, highlight the line. Where you can't find a source sentence, mark the answer as invented or borrowed.
  6. 6Score each page the engines cited against the pages you expected them to cite. The gap between those two lists is usually the most useful thing the audit produces.

What do the results actually mean?

Four patterns cover nearly everything you'll see. Find yours in the left column.

What you sawWhat it meansWhere the fix lives
Not named at all on the category question, but described fine when asked by nameA recall gap. The engine has your facts and no reason to surface them. Your positioning doesn't state a buyer and a moment clearly enough to be filed under the question.Positioning, then third-party sources that answer comparative questions
Named, but described in words that would fit any competitorA distinctiveness gap. The compression found nothing worth keeping, so it kept the category.Your narrative identity, starting with the homepage and the sentence that says who you're for
Named, but the facts are wrong or you're in the wrong categoryA source gap. The engine is reading old pages, stale directories, or a job posting, because your own site left the question open.Entity consistency across every public surface, not just the site
Named and accurate, but the cited pages aren't the ones you'd have pickedA format gap. The engines quote pages shaped like answers to comparative questions.Which pages you publish, not what your positioning says

Notice that only the third row is anything close to a technical problem. The other three are messaging findings wearing a technical costume, which is why teams that run a schema audit and then wait for the numbers to move usually wait a long time. If you're also being handed dashboard percentages by a vendor, read them carefully first, because most AI visibility scores are inflated by design.

What did this audit find when we ran it on ourselves?

We track 50 buyer prompts daily across five engines. Over a five-week window we pulled the ten pages the engines retrieved most often from pitchkitchen.com, out of more than 250 published posts.

Nine of the ten were listicles or comparison pages. The tenth was the homepage. Not a single long-form essay made the list. We'd spent months writing the essays.

That's what a real receipt from this audit looks like. It contradicted something we believed. If your audit confirms everything you already thought, you probably asked the engines your own marketing questions instead of your buyer's questions.

What do we fix first?

Fix the sentence before you fix the schema. If the audit showed a distinctiveness or recall gap, the work is on the words that state who you serve, what changes for them, and when someone should pick you over the alternative. That's the raw material every engine compresses, and it's also what a list-maker, a new sales rep, and a buyer's internal champion all need. One fix, four audiences.

Verbal identity is the half of your brand that machines can read at all, and most companies have never written it down. Once it exists, the technical layer starts earning its keep, because there's finally something specific for the crawler to carry.

If you'd rather not run the six steps yourself, we do this as a free AEO audit: we run your category questions across the engines and send back how you're described today, where you're invisible, and how your closest competitor is positioned in the same answer. If you want the messaging-side version, the Brand Signal Score scores your homepage on narrative clarity, trust, AI-readiness and conversion. Either one gets you a real finding this week.

And if the audit turns up the pattern we see most often, where every engine describes you competently and none of them recommend you, the problem isn't discoverability. Your positioning hasn't given anyone, human or machine, a reason to name you. That's fixable, and it's the work we do.

Questions People Ask

FAQ

How do I audit my website for how AI assistants understand and describe my company?

Ask the assistants first, then read your site. Write five category-level questions in your buyer's words, run each across ChatGPT, Claude, Perplexity and Google's AI Overview in a logged-out session, and log three things verbatim for each answer: how you were described, which competitors were named beside you, and which URLs were cited inline. Then ask the branded version of the question at each engine, and trace every claim back to a specific sentence on your site. Any claim you can't source is either invented or borrowed from a competitor. It takes an afternoon and needs no tooling.

Is an AI visibility audit a technical SEO audit?

No. A technical audit tells you whether a machine can read your site. This one tells you whether it found anything worth repeating. Of the four failure patterns we see in these audits, only one (wrong facts from stale sources) is genuinely technical. The other three are messaging findings: a recall gap, a distinctiveness gap, or a format gap in which pages you publish.

Do I need a paid AI visibility tool to run this?

Not for the first pass. Trackers are useful for watching movement over weeks, but the initial audit is more valuable done by hand because you read the answers yourself instead of a percentage. Be careful with vendor scores in any case: many lean on brand-seeded prompts and biased query sets, which measures recall rather than real discovery.

How often should we re-run it?

Quarterly for the full six steps, and again roughly 60 to 90 days after any significant messaging or homepage change, since that's the lag before engines re-read and re-summarize you. Re-run it immediately if you change category language, launch a new product line, or notice inbound leads describing you in words you don't use.

What if the engines describe us accurately but never recommend us?

That's the most common result, and it's a recall gap rather than an information gap. The model has your facts and no reason to surface them when a buyer asks the category question. The fix is positioning that states a specific buyer and a specific moment clearly enough for the answer to be filed under that question, plus presence in the third-party sources engines reach for on comparative questions.

Want this kind of thinking shipping for you?

An audit gives you the finding. It doesn't give you the sentence that fixes it. If yours turned up a recall or distinctiveness gap, the work is rebuilding the positioning underneath, so that the thing an AI engine says about you is the thing you'd say yourself. That's what the 90-Day Magnetic Messaging Sprint produces: the narrative identity, documented so both your team and the machines can use it.

That's the 90-Day Magnetic Messaging Sprint. One quarter, one fixed price: we extract your story, build the Magnetic Messaging Framework and your AI Brand Twin, then ship the website and sales enablement that run on it. $25K–$45K fixed for the quarter, and you own all of it at the end.

About the Author

Greg Rosner

Greg Rosner

Founder, PitchKitchen · Author of StoryCraft for Disruptors · Creator of the Magnetic Messaging Framework™

Greg is a B2B messaging therapist for growth-stage CEOs ($5M-$75M). He helps founders extract the truth they've been hiding from themselves, name the villain in their industry, and build the messaging infrastructure that scales their voice through AI. PitchKitchen has worked with 100+ B2B companies across SaaS, healthtech, fintech, cybersecurity, and AI-driven solutions.