I’m going to do something slightly uncomfortable and tell you exactly how my own audit went.

The uncomfortable part isn’t the score. 7 out of 24 is a genuine gap and I’m not pretending otherwise. The uncomfortable part is that I work in this field. I built the audit framework I used on myself. I know what the signals mean and why they matter, and I still have a significant gap in my own citeability for the thing I’m now known for.

But that’s actually the point. Understanding something and having fixed your own situation are different things, and the gap between them is where most of the real learning lives. So I’m documenting this.

How does the citeability audit work?

The audit I ran covers 24 criteria across three areas: legibility, consistency, and quotability. Each criterion gets scored on a three-point scale: 0 for absent, 1 for partial, 2 for clear. Maximum score is 48 across both roles being compared. Each role is scored separately on 24 points.

The two roles I scored against:

  • Ops expert: I help founder-led service businesses build the operational systems that let them grow without chaos. Five years of documented, referenced, client-confirmed work.
  • Citeability expert: I help founder-led service businesses get found and cited by AI engines, as themselves. Current pivot, six months into public positioning.

I also ran the client-query prompts across ChatGPT 4o, Perplexity (search mode), and Google AI Overviews. These weren’t just a data-gathering exercise: they tell me what the engine actually says about me in practice, as opposed to what the audit criteria predict it should say.

What did I score on each part of the audit?

Ops expert: 18/24

Still my stronger role by a distance, but not as clean as I’d assumed. The breakdown:

Legibility: 8/8. The language is consistent and specific. My website ops pages describe the problem, the method, and the client type with enough precision that the engine can summarise it accurately.

Consistency: 5/8. The biggest deductions sit here. A directory listing from 2023 still references freelance project work from before the Studio1 GM role. And there’s a thread of older-career signals the engine still picks up, including makeup-artist references from an earlier chapter that linger in older bios and indexed pages. None of it is wrong, and some of it is deliberately part of my story, but it muddies the ops picture and pulls confidence down.

Quotability: 5/8. The weak spot even on ops. My ops content is written for human readers building an argument. The answers are there but they’re buried. Good case study material with no liftable summary lines. FAQ sections that answer general questions rather than the specific client questions I should be targeting.

The engine’s recommendation for ops queries, which I confirmed across all three platforms, was clear and roughly accurate. I appeared in results for “operations consultant for service businesses”, “business systems for founder-led businesses”, and several related variants. The descriptions were accurate but slightly generic. Still, 18/24 is a solid foundation.

Citeability expert: 7/24

This one I expected to be low. I didn’t expect it to be this low. Here’s the breakdown:

Legibility: 3/8. I’ve published the positioning and the website reflects the pivot, but it’s recent and the signal weight behind it is thin against five years of ops content. The engine is reading a newer, barely-reinforced picture next to the older, heavily-reinforced one, and it hedges hard toward ops.

Consistency: 2/8. The lowest area, and the one that surprised me with how bad it is. LinkedIn still leads with operations. My Clutch listing is completely out of date. An Indie Hackers post from early 2025 introduces me as an ops consultant. A podcast episode that still ranks well for my name is entirely about operational systems. The old signals are active, indexed, and the engine is reading all of them.

Quotability: 2/8. I haven’t yet built the structured citeability content in the new positioning. This post is the start of that. There are no self-contained, liftable answers about my citeability method, my audit process, or my specific approach to visibility work. The content is on its way. The structure isn’t there yet.

The engine query results confirmed everything the audit predicted. On citeability and AI visibility queries, I don’t appear. Perplexity returned three competitors with more established signal trails. ChatGPT gave a generic answer with no specific practitioners named. Google AI Overviews offered a framework without attributing it to anyone.

What is the citeability gap actually about?

It’s not a capability gap. The work is real, the method is tested, the results are there with the clients I’ve been doing this with.

It’s an entity gap. The engine has built a picture of me over five years of public content, interviews, client references, and directory listings, and that picture is predominantly about operations. The pivot happened in my head and my calendar before it happened in the indexed record of my public presence.

The engine sees both versions of me, the old ops identity and the newer citeability positioning, and it averages them. The result is a hedged, blurred entity that’s confident about one category and uncertain about the other.

The fastest people to resolve this are the ones who catch it early and move fast on the signals cleanup before the old picture becomes too dominant. I caught mine at six months. That’s early enough to fix it without a multi-year rebuild, but it requires doing the work deliberately and not just publishing content in the hope that it updates the picture automatically.

How am I fixing my own citeability gap?

I’m documenting the fix in public because the most useful thing I can do is show the method working in the most inconvenient possible case: me.

The fix list, in order:

1. Website positioning. This is the priority, and it’s where I’m starting. The ops language on key pages is being subordinated to the citeability work, so the site reads primarily as the home of a citeability strategist who has an ops background, not an ops consultant who sometimes does visibility work. Everything else points back here, so the site has to be right first.

2. Structured content in the new positioning. This post is the start. The blog cluster being built around citeability work will add quotable material at scale. Each post is designed to answer a specific client question in a liftable format.

3. Indexed profile cleanup. Clutch, directory listings, bio boxes on guest posts, and the older-career references still floating around. Working through the list methodically, updating what I can, noting what I can’t.

4. LinkedIn summary and headline. High-authority and high-impact, but deliberately sequenced after the new website is live. There’s no point pointing my most-indexed profile at a site that doesn’t yet match the new positioning. Once the site is live, the LinkedIn summary and headline get rewritten to lead with citeability work and reference ops as the foundation it sits on.

5. New external citations. Getting quoted in the new positioning in other people’s content, in interviews, in shared posts. This is slower to build but it’s what shifts the attributed-expertise component of the entity.

I’ll post the 30-day results here when I have them. If you want to see the full method, including how I ran the prompts and what I was looking for in each result, how to check if AI recommends your business has the framework.

What does this tell you about your own citeability audit?

A few things.

First: the entity lag is real and it’s common. If you’ve evolved what you do in the past two years, your AI visibility probably reflects who you were more than who you are. That’s not a character flaw. It’s a structural feature of how the signals accumulate over time.

Second: scoring yourself honestly is harder than it sounds. Every criterion has a temptation to be generous. “Well, I do say that somewhere” is not the same as “the engine can find it, read it, and cite it.” Apply the standard a stranger would apply.

Third: the gap is fixable and the order matters. Legibility and consistency work, the boring stuff, before content. Content in the new positioning, but structured for quotability. External citations as the slower tail that reinforces everything else.

If you’d rather have someone run the full version of this on your business, with the client-query testing and the prioritised fix list, that’s what the Citeability Snapshot is built for.

Get your Citeability Snapshot.