How we log AI visibility: 10 questions × 4 engines, weekly

By metabygaurav · Published 20 September 2026

Starting September 2026, metabygaurav logs 10 buyer questions across 4 AI engines every week — 40 sampled answers per week — and publishes the method and data here.

Why we log manually

A single AI answer is one sample from a distribution. Ask ChatGPT the same question twice and you can get different brands cited. Any vendor showing you one screenshot as “proof” of visibility is showing you one coin flip.

So we do the boring version: the same fixed questions, asked fresh every week, on every engine, with the citations written down. Over weeks, that becomes a share-of-voice measurement you can actually act on.

The method

  1. Fix the question set. 10 questions a real buyer would ask an AI assistant. They are written once and never reworded mid-series, because rewording invalidates the trend.
  2. Fix the engines. ChatGPT (with web search), Perplexity, Gemini and Claude. Each engine retrieves differently — ChatGPT leans on Bing’s index, Perplexity on its own crawl, Gemini on Google — so results are logged per engine, never blended into one “AI visibility” number.
  3. Ask fresh, log everything. Each question is asked in a clean session. We record: date, question, engine, whether the target brand was cited (yes/no), which domains were cited instead, and notes.
  4. Weekly cadence. Every week, same day. 10 questions × 4 engines = 40 logged answers per week.

What this does and does not tell you

  • It does show which domains each engine repeatedly pulls from for your buyers’ questions — those domains are your target list.
  • It does show movement after content or schema changes, engine by engine.
  • It does not prove causation. If citations improve after a change, that is evidence, not proof. We say this to clients, too.

How to cite this

metabygaurav (2026). How we log AI visibility: 10 questions × 4 engines, weekly. First published 20 September 2026. The weekly dataset will be published on this page as a downloadable CSV once the first month of logs is complete.