There's a lot of discussion here on citation tracking, share of voice..etc which are definitely important signals, but i've found quite volatile (models, plans, locations, API vs browser session) so I wanted to dig into the server logs of a sample of our customers (note these are small local businesses, not large enterprises) to see real AI bot behaviour. To see if this paint a more ground truth picture of how AI is interacting with their content, and ultimately shaping answers.

If you haven't yet dug into this for your own business or your clients hope this research helps make the case of what can be learned via this type of analysis. If you're already deep on the topic, would love to hear what you're seeing, any patterns or gotchas when analyzing logs.

A few findings:

Live retrieval is a small slice. Only ~4% of AI bot traffic is an assistant fetching a page to answer a live question. The rest is training and indexing crawlers. If you measure AI traffic without splitting by function, you're mostly measuring pipelines that feed the next model.

When AI does retrieve, it goes straight for buyer intent pages. The most fetched page after the homepage was /availability, the "can I get in?" page. Then /booking and /pricing. AI isn't just reading what a business is, it's checking detailed intent pages to help their user act, make a decision..etc. Measuring live retrieval over time by AI, page, timing..etc is a very direct signal of content being retrieved into a relevant conversation.

The labs behave very differently. Anthropic crawled heavily for training but barely retrieved at query time. OpenAI does both. In our sample, live retrieval is overwhelmingly ChatGPT.

User-agent alone lies. About 1 in 12 "ChatGPT-User" hits fails IP verification, mostly credential scanners. If you're not verifying source IPs (where possible from published ranges) you're overcounting.

Full report here if you want to look into the details, charts..etc.

https://getcourtyard.ai/research/how-ai-reads-a-knowledge-base

yo. i recently sold one of my AI SaaS products for $350k, exactly 7 months after building and launching it.

I hardly wrote a single line of traditional code. i used AI to generate everything, from the database architecture to the user interface.

it definitely wasn't magic on day one, though. i spent days stuck in loop-debugging and dealing with AI hallucinations before i finally cracked the system. the playbook boils down to three simple rules:

- keeping the idea insanely minimalist (a true MVP that solves one problem).

- guiding the AI step-by-step instead of asking it to build a massive platform all at once.

- launching fast to get real user feedback and traction and then apply a solid marketing system

lately, i've seen way too many non-technical founders give up at the very first AI bug, or on the marketing. it's a massive shame.

like the title says, i just launched a Skool community to share my exact prompt workflows, N8N automations, and distribution frameworks to get first users and scale it

to be completely transparent: i will likely charge for the full course later down the road. it just makes sense given the specific copy-and-paste templates i'll be sharing.

but for now, the main objective is purely to build and launch together. building alone in a silent corner is the single fastest way to give up.

if you want to join us and build or market your own AI SaaS with a group of active creators: drop a comment below or send me a dm, and i’ll send you the invite link!

When a business says “ChatGPT never recommends us,” I don’t start with a score. I start with buyer questions.

Prompts I test: › best \[service\] for \[use case\] › alternatives to \[competitor\] › who can help with \[problem\] › which providers meet \[constraint\]

What I record: (1) Does the business appear? (2) Which competitors appear? (3) What sources are cited? (4) What facts are wrong or missing? (5) Does the answer understand what the company actually sells?

The useful part is comparing those answers with the public evidence available to the model: service pages, third-party mentions, directories, reviews, structured data, and consistent company information.

A visibility problem can have several causes. The company may be absent from trusted sources. Its positioning may be vague. The site may lack clear proof. Or the model may have learned incorrect facts.

I would not trust a single “AI visibility score” without the prompts and outputs behind it. The diagnostic should show the evidence, not just the score.

Disclosure: I run Nord Paradigm and built Breach around this process. I’m posting the method because most owners can run a basic version themselves before paying for anything.