---
title: "824 AI Fetches. No Proof of Recommendation."
description: "groas’s 30-day edge figures show why verified AI fetches are not recommendations—and what an AI-search report must show before you buy."
url: "https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to"
image: "https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9d0877bf-5bea-4c1d-be9a-dcb5107e5420.png"
published: "2026-11-08T06:24:45.374Z"
modified: "2026-11-08T06:24:45.428Z"
---

November 8, 2026 · 10 min read

# 824 AI Fetches. No Proof of Recommendation.

[](https://groas.com/author/alexander-perelman)

[Alexander Perelman](https://groas.com/author/alexander-perelman)Personally Tested

Head Of Product @ groas

[LinkedIn](https://www.linkedin.com/in/alexander-433793253/)

![Tiny workers wheel carts of web pages into a sealed black box while a clerk tallies each delivery, but nothing visible comes out the other side.](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9d0877bf-5bea-4c1d-be9a-dcb5107e5420.png)

In this article

1. [What the 824 fetches actually establish](#what-the-824-fetches-actually-establish)
2. [Compare the request profiles before comparing performance](#compare-the-request-profiles-before-comparing-performance)
3. [Calculate live-answer share without turning it into a quality score](#calculate-live-answer-share-without-turning-it-into-a-quality-score)
4. [What each kind of provider report can answer](#what-each-kind-of-provider-report-can-answer)
5. [Put competing proposals on the same measurement terms](#put-competing-proposals-on-the-same-measurement-terms)
6. [The decision: buy evidence of visibility, not a larger crawler count](#the-decision-buy-evidence-of-visibility-not-a-larger-crawler-count)

**824 verified live-answer fetches. Not 824 recommendations.** That is the gap between what groas’s supplied homepage logs record and what an agency might let a buyer assume.

Over the measured period, the homepage recorded 2,039 verified bot hits, including those 824 live-answer fetches. The requests are genuine. The leap from requests to recommendations is not.

I used to tell clients that a crawl meant interest. I was wrong. A fetch records a request for a page. It does not tell me whether the resulting answer named the brand, cited the URL, or told the buyer to choose a competitor. Technical access, live-answer retrieval, and brand recommendation are different measurements. Calling all of them _AI visibility_ does not make them interchangeable.

The supplied figures cover three URLs with very different request profiles. I’ll compare their counts and live-answer shares, then use those distinctions to judge provider reporting. The buying question is not whether a bot reached the site. It is whether the evidence answers what you hired someone to improve.

## What the 824 fetches actually establish

The homepage recorded **824 verified live-answer fetches, not 824 proven recommendations**. A [ChatGPT-User-type request](https://www.shiftrank.ai/blog/gptbot-vs-chatgpt-user) is associated with a person’s question, unlike a bulk training crawl running on its own schedule. That distinction makes live-answer activity worth separating from general crawler traffic.

It still does not reveal the answer. Requesting a page during answer-building and recommending the business on that page are different events. The log records the request, not the model’s final judgment.

The source here is groas’s supplied edge-log extract: **30 measured days of request-level counts from a truncated path list**. It is not a whole-site census. The supplied dataset has no public source URL; the linked material explains the collection and verification method, not an independently published copy of these figures.

“Verified” means a request passed checks against published IP ranges or reverse-DNS plus forward-DNS. That matters because [user-agent strings are easy to spoof](https://www.shiftrank.ai/blog/gptbot-vs-chatgpt-user). A familiar bot name in a log is not enough.

These are server or edge-log measurements, not GA4 session counts. I can report which pages were requested. I cannot identify how many people saw an answer, which prompt triggered each fetch, or whether it produced a sale.

![Infographic separating bot-matched hits, verified requests, and live-answer fetches](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/2accfaab-f64d-4f11-9af2-205d7fe53990.png)

## Compare the request profiles before comparing performance

The table keeps the supplied counts separate. Each column answers a narrower question than the one before it:

- **Bot-matched hits:** requests matching the bot-identification criteria before verification.
- **Verified hits:** requests that passed the verification checks.
- **Verified live-answer fetches:** the subset classified as live-answer activity.

| URL                            | Bot-matched hits | Verified hits | Verified live-answer fetches |
| ------------------------------ | ---------------: | ------------: | ---------------------------: |
| Homepage `/`                   |            5,645 |         2,039 |                          824 |
| Google Ads updates page        |              850 |           833 |                          513 |
| Second Google Ads changes page |              483 |           479 |                          392 |

_Source: groas’s supplied edge-log extract, covering the same measured period and truncated path list. For the collection approach, see [Track the Client Pages AI Crawlers Actually Fetch](https://groas.com/post/tutorial-prove-which-client-pages-ai-bot)._

The biggest gap appears on the homepage. Of its bot-matched hits, 36.1% passed verification. The editorial pages retained almost all their matched requests: 833 of 850 and 479 of 483.

That difference matters, but it does not explain itself. The table does not establish why the homepage has more unverified activity, or why the editorial pages have less. It establishes that the headline count changes substantially when verification enters the picture.

**Compare verified activity with verified activity.** A report that shows only the largest column leaves out information you need before judging even the narrower claim of crawler access.

## Calculate live-answer share without turning it into a quality score

The next calculation is straightforward: divide verified live-answer fetches by all verified hits for each URL.

| URL                            | Calculation from supplied counts | Live-answer share of verified hits |
| ------------------------------ | -------------------------------: | ---------------------------------: |
| Homepage `/`                   |                      824 ÷ 2,039 |                              40.4% |
| Google Ads updates page        |                        513 ÷ 833 |                              61.6% |
| Second Google Ads changes page |                        392 ÷ 479 |                              81.8% |

_Source: calculations from the supplied edge-log counts above; percentages are rounded._

The editorial pages have a higher proportion of live-answer requests than the homepage. That is the finding. **It is not a ranking of content quality, recommendation frequency, or commercial value.**

The pages address specific Google Ads topics, while the homepage serves a broader purpose. That is useful context, but these counts alone do not prove what caused the different request mixes. I would not turn an explanation that sounds plausible into a result the data never measured.

To measure the answer, I need to separate [mention, citation, and recommendation](https://chungdigital.com/blog/how-to-measure-ai-visibility):

- **Mention:** the answer names the brand.
- **Citation:** the answer lists the URL as a source.
- **Recommendation:** the answer suggests the brand as a choice.

A page can be cited while the answer recommends a competitor. A brand can also be named without a citation. Neither outcome is visible in these logs.

Requests must not be relabeled as users or answers, either. An answer can trigger several fetches, and prompts can be retried across engines. The [variability discussed in the SparkToro/Gumshoe work](https://pathmonk.com/measure-ai-search-visibility/) is another reason not to treat a single answer run as a stable picture of brand visibility.

Keep the ratio’s label attached. _Live-answer share of verified requests_ is less glamorous than _AI authority score_, but at least it tells me what was divided by what.

## What each kind of provider report can answer

Different reports are useful for different jobs. The problem starts when a provider uses evidence from one layer to claim success in another.

| Reporting layer                | Evidence to inspect                                | What it does not establish by itself            |
| ------------------------------ | -------------------------------------------------- | ----------------------------------------------- |
| Technical access and retrieval | Verified requests, separated by URL and assistant  | What the answer said                            |
| Observed answer visibility     | Repeated prompt runs and raw answers               | Site visits or revenue                          |
| Business activity              | Site sessions, qualified enquiries, closed revenue | Every unobserved answer that influenced a buyer |

**A useful combined report keeps these layers separate rather than blending them into a score.** Here is what I expect from each.

### Access reporting: show the verification, not just the volume

Access-focused reporting asks whether verified crawlers can retrieve the site and whether live-answer requests occur. This is the work behind the supplied fetch counts.

A proper report separates bot-matched requests, verified requests, and live-answer fetches from training crawls. It also breaks activity out by URL and assistant. The edge-logging method operates on the site’s own domain, where those requests can be recorded.

This evidence is useful for diagnosing access. It does not show whether an answer praised the brand, ignored it, or used its page to support another recommendation.

**Buy access reporting as access reporting.** Do not pay for a crawl count dressed as an answer audit.

### Answer monitoring: inspect what the model actually wrote

Answer monitoring asks whether the brand appears for a defined set of buyer prompts. An honest version [repeats the same prompts across engines in clean sessions](https://citedgeo.com/measurement/) and retains the resulting answers.

The denominators belong in the report:

- **Mention rate:** answers naming the brand divided by all tested answers.
- **Citation rate:** answers linking the brand’s URLs divided by all tested answers.
- **Competitor comparison:** how named competitors appear within that same prompt set, reported by engine.

If the report claims recommendations, I want the underlying answers showing recommendations. Naming a business is not the same as suggesting it as the pick.

The results describe the tested prompts and runs. They are not a census of everything people ask ChatGPT, Gemini, or Perplexity. **Demand the prompt list, engines, dates, and raw answers behind the score.**

### Business reporting: keep the commercial denominator intact

Business reporting asks what happens on the site afterward: sessions, qualified enquiries, and closed revenue. [Visibility and traffic are recorded in different places](https://pathmonk.com/measure-ai-search-visibility/), so a citation count cannot stand in for either visits or sales.

A brand may be cited often and receive few visits. It may be named without a citation. That is why I want access, observed visibility, and attributable business activity presented alongside one another, not added together.

**A fetch, a mention, and a qualified enquiry are not interchangeable units.** If they move into a single blended score, I can no longer tell which part improved.

![Cartoon of a marketer mistaking a server log for a customer recommendation](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/14c60f81-eca5-41f1-9232-5385d9d5e9b5.png)

## Put competing proposals on the same measurement terms

When I compare ongoing SEO and generative engine optimisation proposals, I start with definitions, not the dashboard preview. A polished chart can conceal a very loose promise.

The [published GEO-retainer pricing range of $390 to $10,000 per month](https://www.useomnia.com/blog/generative-engine-optimization-services) is broad. It is context from that source, not evidence that any particular scope or price is justified. The deliverables still have to survive inspection.

I want these items in writing:

- **The prompt list:** what buyer questions the provider tests.
- **The engines:** where those prompts run, without hiding differences in a blended average.
- **The repeat schedule:** how often the same prompts are tested again.
- **The evidence:** raw answers and cited URLs behind reported rates.
- **The baseline:** what the provider compares later results against.
- **The work:** monthly deliverables, not just a monthly score.

A guaranteed ChatGPT position, a score with no baseline, or deliverables that never make it into writing are reasons to stop the conversation.

I also keep the business’s existing measurements distinct. Google rankings describe positions in classic results. Traffic describes site sessions, with conversions tracked separately. AI visibility describes observed mentions and citations across repeated prompt runs. Qualified enquiries are the form fills, calls, and booked jobs sales accepts.

**The report should connect the work, not erase the distinctions.** Improving access may be necessary before a page can be retrieved. Improving retrieval does not, by itself, prove that buyers now see a recommendation. That is the next measurement, not a complimentary upgrade to the first one.

### Where groas’s managed approach fits—and where the evidence stops

What I want from groas is the same separation I demand from anyone else. groas runs paid ads, SEO, and visibility in ChatGPT and Google answers as a managed service, with actions and their reasoning logged in plain language.

The advantage of that structure is the operating model: **the service acts on the evidence rather than handing the client another dashboard to interpret.** Goals and budget stay with the client. Execution sits with the machine, with a named strategist accountable for direction and results. The [groas philosophy](https://groas.com/our-philosophy) explains that logic; [groas](https://groas.com/) sets out the managed scope.

That is a better buying proposition than a reporting-only engagement that leaves the client to diagnose and fix every weak signal. But the reporting still has to show which signal is weak. Edge logs establish retrieval. Repeated prompt tests establish observed mentions and citations. Site measurement tracks qualified pipeline. A managed service does not make those boundaries disappear.

Nor do the supplied logs prove that the full measurement chain is already present. They support the access and retrieval part. Evaluating the rest requires the corresponding answer records and business records.

The homepage and editorial counts remain request-level fetches from a truncated path list. They do not reveal the triggering prompts, prove that an answer named groas, or establish whether several fetches fed the same answer.

**I would rather buy that narrow truth than a bigger blended number.** Hire the provider that keeps the layers visible, then does the work on the weakest one.

![Painting of an analyst separating crawler logs from buyer enquiries on a workbench](https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/f4bc8256-5fba-4770-b957-dbcb99271712.png)

## The decision: buy evidence of visibility, not a larger crawler count

The supplied figures establish a clear difference between matched bot activity, verified requests, and live-answer retrieval. The homepage loses a substantial share of its matched activity at verification. The editorial pages retain much more, and live-answer requests make up a higher share of their verified traffic.

None of that establishes a recommendation. The same limitation applies whether the headline number is large or small.

**Judge proposals on separate denominators and inspectable evidence.** Access logs for retrieval. Repeated prompt runs and raw answers for mentions, citations, and claimed recommendations. Site records for qualified enquiries and revenue.

If a provider supplies those layers in writing, with dates and limits stated, keep talking. If it hands over a crawler count and calls it AI visibility, the missing evidence is the answer.

Buy the evidence, not the count.

## Frequently Asked Questions

### Do 824 AI fetches mean a brand was recommended 824 times?

No. The 824 figure counts verified live-answer fetches, meaning AI assistants requested the page while building an answer. The log records the request only, not whether the resulting answer named the brand, cited the URL, or suggested a competitor instead.

### How do you verify that a bot request in a log is really from that AI assistant?

A request is considered verified only if it passes checks against published IP ranges or reverse-DNS plus forward-DNS confirmation. A familiar bot name in the user-agent string is not enough, because user-agent strings are easy to spoof.

### Why did the homepage lose so many bot hits during verification while the editorial pages did not?

Only 36.1% of the homepage's bot-matched hits passed verification, while the Google Ads updates and changes pages retained almost all of theirs (833 of 850 and 479 of 483). The logs show that the difference exists but do not explain why the homepage attracts more unverified activity.

### Is a high live-answer fetch share a sign that my content is better?

No. Live-answer share is simply the number of verified live-answer fetches divided by all verified hits for a URL. It describes the composition of requests, not content quality, recommendation frequency, or commercial value, and the logs cannot prove what caused the different request mixes.

### What is the difference between a mention, a citation, and a recommendation in AI answers?

A mention means the answer names the brand. A citation means the answer lists the brand's URL as a source. A recommendation means the answer suggests the brand as a choice. A page can be cited while the answer recommends a competitor, and access logs cannot show which of these occurred.

### What should I look for in a report about AI visibility before buying?

Check that the report keeps three layers separate: verified access logs for retrieval, repeated prompt runs with raw answers for mentions and citations, and site records for sessions, qualified enquiries, and revenue. A fetch, a mention, and a qualified enquiry are not interchangeable units, and blending them into one score hides which part improved.

### What should I ask a provider to put in writing when comparing GEO proposals?

Ask for the prompt list, the engines where those prompts run, the repeat schedule, the raw answers and cited URLs behind reported rates, the baseline for comparison, and the monthly deliverables. A guaranteed ChatGPT position, a score with no baseline, or unwritten deliverables are reasons to stop the conversation.

## Run Your Marketing On groas

Plug ChatGPT, Claude or any AI agent into groas and let it do the work of a whole marketing team: $19 a month flat with every feature included, and autopilot whenever you’re ready.

[Start For $19](https://groas.com/pricing)

[Or have groas run it for you](https://groas.com/done-for-you)

## Structured data

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://graph.groas.com/entity/groas","name":"groas","url":"https://groas.com/","description":"groas is the marketing infrastructure for your own AI: it connects your AI to all your marketing and gives it proprietary marketing data collected 24/7. Plug Claude, ChatGPT or any AI agent into groas and run all your marketing from it, for a tiny fraction of the usual cost, with the groas app there whenever you want to see more. It is the layer ChatGPT, Claude and any AI assistant run a business’s online marketing on. Through groas an assistant can do anything you could do natively in Google Ads, Bing Ads, Meta Ads and ChatGPT ads, on your website and in AI search, and, where the owner switches it on, can run connected campaigns by itself, so AI agents do the work a whole marketing team used to. groas also gives those agents large-scale proprietary marketing data it collects around the clock, on any schedule the owner chooses: every ad competitors run on Google and Meta, their landing pages and full funnels with the offers and prices in them, Reddit customer research, AI search answers from ChatGPT, Google AI Overviews, Gemini, Claude and Perplexity, and SEO data from Semrush and Ahrefs, backlinks included ($19 a month, flat, with everything included, for unlimited teammates on one shared workspace and unlimited ad accounts and websites, delivered as an MCP server). Separately, its done-for-you service has senior people and proprietary quantitative systems run paid ads, SEO and AI search for businesses, and white label for agencies, from $5,000 a month.","logo":{"@type":"ImageObject","url":"https://groas.com/icon-512.png","width":512,"height":512},"sameAs":["https://www.linkedin.com/company/groas/"]},{"@type":"WebSite","@id":"https://groas.com/#website","name":"groas","url":"https://groas.com/","inLanguage":"en-US","publisher":{"@id":"https://graph.groas.com/entity/groas"}},{"@type":"WebPage","@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#webpage","url":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to","name":"824 AI Fetches. No Proof of Recommendation.","description":"groas’s 30-day edge figures show why verified AI fetches are not recommendations—and what an AI-search report must show before you buy.","inLanguage":"en-US","isPartOf":{"@id":"https://groas.com/#website"},"about":{"@id":"https://graph.groas.com/entity/groas"},"primaryImageOfPage":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9d0877bf-5bea-4c1d-be9a-dcb5107e5420.png"},"breadcrumb":{"@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#breadcrumb"},"dateModified":"2026-11-08T06:24:45.428Z","mainEntity":{"@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#article"}},{"@type":"BreadcrumbList","@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://groas.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://groas.com/blog"},{"@type":"ListItem","position":3,"name":"824 AI Fetches. No Proof of Recommendation.","item":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to"}]},{"@type":"BlogPosting","@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#article","url":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to","mainEntityOfPage":{"@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#webpage"},"isPartOf":{"@id":"https://groas.com/blog#blog"},"headline":"824 AI Fetches. No Proof of Recommendation.","description":"groas’s 30-day edge figures show why verified AI fetches are not recommendations—and what an AI-search report must show before you buy.","datePublished":"2026-11-08T06:24:45.374Z","dateModified":"2026-11-08T06:24:45.428Z","image":{"@type":"ImageObject","url":"https://pub-87da24ecbbfc4c3bad6875f3aa013712.r2.dev/generated-images/9d0877bf-5bea-4c1d-be9a-dcb5107e5420.png"},"author":{"@id":"https://groas.com/author/alexander-perelman#person"},"publisher":{"@id":"https://graph.groas.com/entity/groas"},"keywords":"verified, fetches, answer, live-answer, 824, recommendation, requests, answers","wordCount":1992,"inLanguage":"en-US"},{"@type":"Person","@id":"https://groas.com/author/alexander-perelman#person","name":"Alexander Perelman","jobTitle":"Head Of Product @ groas","description":"My background includes Goldman Sachs and Stanford Computer Science.","image":"https://groas.com/media/blog/4f17cac3a81acc224cc1b2cfab8f94bbc295a3089d13e8421125771ef8d4064f.jpg","worksFor":{"@id":"https://graph.groas.com/entity/groas"},"sameAs":["https://www.linkedin.com/in/alexander-433793253/"]},{"@type":"FAQPage","@id":"https://groas.com/post/824-live-answer-fetches-are-not-824-recommendations-how-to#faq","mainEntity":[{"@type":"Question","name":"Do 824 AI fetches mean a brand was recommended 824 times?","acceptedAnswer":{"@type":"Answer","text":"No. The 824 figure counts verified live-answer fetches, meaning AI assistants requested the page while building an answer. The log records the request only, not whether the resulting answer named the brand, cited the URL, or suggested a competitor instead."}},{"@type":"Question","name":"How do you verify that a bot request in a log is really from that AI assistant?","acceptedAnswer":{"@type":"Answer","text":"A request is considered verified only if it passes checks against published IP ranges or reverse-DNS plus forward-DNS confirmation. A familiar bot name in the user-agent string is not enough, because user-agent strings are easy to spoof."}},{"@type":"Question","name":"Why did the homepage lose so many bot hits during verification while the editorial pages did not?","acceptedAnswer":{"@type":"Answer","text":"Only 36.1% of the homepage's bot-matched hits passed verification, while the Google Ads updates and changes pages retained almost all of theirs (833 of 850 and 479 of 483). The logs show that the difference exists but do not explain why the homepage attracts more unverified activity."}},{"@type":"Question","name":"Is a high live-answer fetch share a sign that my content is better?","acceptedAnswer":{"@type":"Answer","text":"No. Live-answer share is simply the number of verified live-answer fetches divided by all verified hits for a URL. It describes the composition of requests, not content quality, recommendation frequency, or commercial value, and the logs cannot prove what caused the different request mixes."}},{"@type":"Question","name":"What is the difference between a mention, a citation, and a recommendation in AI answers?","acceptedAnswer":{"@type":"Answer","text":"A mention means the answer names the brand. A citation means the answer lists the brand's URL as a source. A recommendation means the answer suggests the brand as a choice. A page can be cited while the answer recommends a competitor, and access logs cannot show which of these occurred."}},{"@type":"Question","name":"What should I look for in a report about AI visibility before buying?","acceptedAnswer":{"@type":"Answer","text":"Check that the report keeps three layers separate: verified access logs for retrieval, repeated prompt runs with raw answers for mentions and citations, and site records for sessions, qualified enquiries, and revenue. A fetch, a mention, and a qualified enquiry are not interchangeable units, and blending them into one score hides which part improved."}},{"@type":"Question","name":"What should I ask a provider to put in writing when comparing GEO proposals?","acceptedAnswer":{"@type":"Answer","text":"Ask for the prompt list, the engines where those prompts run, the repeat schedule, the raw answers and cited URLs behind reported rates, the baseline for comparison, and the monthly deliverables. A guaranteed ChatGPT position, a score with no baseline, or unwritten deliverables are reasons to stop the conversation."}}]}]}
```
