You do not need a paid tool to know whether your brand is being recommended in AI answers. This is the SOP our teams use to track visibility across ChatGPT, Gemini and Perplexity, start to finish.
Your brand's position in ChatGPT, Gemini and Perplexity answers is not static. Content updates, model refreshes, a new Reddit thread, a competitor's review push, or a search-index change can all move you from absent to recommended, or from recommended to omitted, within a few weeks. Without a recurring measurement process, you only discover these moves by accident, usually when a sales conversation reveals a competitor that now appears where you used to.
The goal of monitoring is to make optimization evidence-based: to know which questions you win, which you lose, which sources the engines use when they describe you, and how that changes month over month. This article walks through the manual SOP we use internally for overseas English-language GEO programs. It assumes no paid software; everything runs from a browser and a spreadsheet.
The library is the whole foundation: the quality of your measurement is only as good as the questions you ask. Build 30-50 English questions per engine, organized by the four stages of a buyer's decision, with roughly 10-15 questions in each stage:
| Decision stage | Query pattern | Example phrasing |
|---|---|---|
| Awareness | What is / how does X work | "What is a cloud cost optimization tool?" |
| Comparison | X vs Y / best X for a use case | "Best CRM for a 200-person manufacturer" |
| Decision | Worth it / pricing / review | "Is [category] software worth the price?" |
| Negative / trust | Complaints / scam / trustworthy | "Is [brand] trustworthy? Any complaints?" |
Cover your brand name, your category terms and your competitor names within the same set, so the engines describe the whole market rather than only your corner. We keep a core library of about 20 questions for monthly reporting and an extended library of 50-100 for quarterly review, and we retire outdated phrasing every quarter. Each row records the question text, the decision stage, the engine, the test date, whether you were mentioned, your position, description accuracy, which competitors appeared, and which source the answer cited.
Three execution rules protect comparability. First, run every question in a fresh conversation, so previous chat context cannot tilt the next answer. Second, test the same three engines every time: ChatGPT on the latest model, Perplexity on its Pro search, and Gemini with Google search grounding enabled. Third, run on a fixed weekday schedule and from a fixed geographic node, because the engines tailor answers partly to the requester's region. If you test from the US West Coast one week and from Singapore the next, the series breaks.
Because a single AI run is noisy, run each question three times and record the majority result. Our convention: mentioned in three of three runs is a stable mention; two of three is an edge mention; zero to one of three means you are not yet in the candidate set for that query. Never judge a query from a single answer.
For every row, log three dimensions rather than a yes/no note: how many times your brand name appears; your position (first recommendation, co-listed, tail mention, inside a comparison table, or a negative mention); and the source the answer leaned on (your own site, a third-party review site, Reddit, YouTube, an industry publication). Archive the full answer text or screenshot for every run, so a later report can be checked and reproduced. The metric definitions themselves are covered in our companion piece on citation rate and share of voice.
From the logged rows we compute three rates per engine, and we compare them week over week rather than chasing any single value:
Once a month we run an attribution pass. For every question where visibility changed, we ask why: did a new Reddit thread or review page appear? Did a specific article on your site get updated? For questions that never mention you, we ask which signal is missing, then assign next month's work against those gaps. That loop is what turns a dashboard into a plan.
The biggest failure mode in GEO measurement is the black box: an agency claims results but cannot show how it measured them, and the client's own checks disagree. The fix is white-box monitoring: the question library is documented, the raw answers are archived for audit, results are reported separately per engine rather than blended, and trends are shown as monthly curves with competitors included on the same chart. A number that a client cannot reproduce is a number no one should be asked to approve budget against.
At AoWang, our overseas monitoring delivery follows exactly this pattern: each month clients receive a mention-rate trend, a per-engine comparison across ChatGPT, Gemini and Perplexity, a citation-source distribution, an attribution note for unattributed questions, and recommended actions for the next month. We serve more than 700 enterprise clients across 60+ countries and 20+ industries, with 99.8% detection accuracy and adaptation to major LLM updates within 48 hours (company operating figures, measured on our AI-search monitoring platform); over a full cycle, measured visibility has risen by an average of 300%+.
Key takeaway: Monitor overseas AI visibility with a documented English question library, fixed engines and a fixed geographic node, fresh conversations per query, and a three-times majority rule. Track mention rate, first-mention rate and owned-source rate separately, archive every raw answer, and report monthly trends with competitors shown. Move to paid tooling only when the library exceeds about 100 queries, the engines exceed five, or the team exceeds three.
If you would rather start with a managed baseline, read our end-to-end GEO measurement guide or ask the AoWang team to run a ChatGPT, Gemini and Perplexity visibility audit for your brand. New to the channel? Our beginner's guide to GEO covers the fundamentals first.
Start with 30-50 English questions per engine, spread across the buyer decision stages: awareness, comparison, decision and negative queries, with roughly 10-15 questions per stage. Keep a core set of around 20 for monthly measurement and an extended set of 50-100 for quarterly review, then refresh the library as buyer phrasing changes.
AI answers vary with context, model version and recency settings, so a single run is not reliable. Our SOP runs each question three times and takes the majority result: three out of three means a stable mention, two out of three means a marginal or edge mention, and zero to one means you are not yet in the AI candidate set for that query.
Yes, and the location must stay fixed. These engines adjust their answers partly based on the requester's region, so testing from a different city or country each week makes the numbers incomparable. Pick a stable node in your target market, for example the US West Coast, and run every test from that same location.
Manual testing is the most accurate method early on because you read the full answer text. Consider dedicated tools once your question library exceeds about 100 queries, you monitor more than five engines, or three or more people run the process. Until then, a spreadsheet and a fixed weekly cadence are enough.
Talk to the AoWang GEO team about visibility diagnosis, content optimization and AI-search monitoring for your brand.
Contact Us →