V Digital Services — Dated Case Study | AnswerShare

Measured on the prompt “Recommend a good digital advertising agency in Phoenix” — audit dated 2026-07-16, three days after the machine layer went live at 2026-07-13 08:45 UTC. Perplexity #1, Grok #1, ChatGPT #2.

Last updated:

Client case study · V Digital Services

Invisible to #1
— in 3 days.

Measured on the prompt “Recommend a good digital advertising agency in Phoenix” — audit dated 2026-07-16, three days after the machine layer went live at 2026-07-13 08:45 UTC. Perplexity #1, Grok #1, ChatGPT #2.

On 17 June 2026, five AI engines were asked which digital marketing agencies to consider for enterprise SEO. None of them named V Digital Services. The AnswerShare machine layer went live at the edge of www.vdigitalservices.com on 13 July.
Three days later, the audit above returned V Digital Services first on Perplexity, first on Grok, and second on ChatGPT. On 2 August, Perplexity returned it first again. On 22 July, ChatGPT did not return it at all.

Every statement on this page carries its date and its source, the 22 July dip included. The full before-state, the exact queries behind each measurement, and the figures we withheld are all below.

2026-06-17Pre-cutoverOmitted by 5 of 5 engines on the enterprise-SEO query; 4 of 5 on the Phoenix queryArchived receipts, read directly2026-07-1308:45 UTCFirst AI-crawler request recorded at the edgeCrawl log, first row2026-07-16+3 daysPerplexity #1 · Grok #1 · ChatGPT #2Client dashboard engine auditThe starting condition · 2026-06-17

Before AnswerShare, AI rarely named V Digital Services when buyers were choosing an agency.

On June 17, 2026, five AI engines were asked two buyer-intent questions about choosing a digital marketing agency. V Digital Services was omitted from nine of ten answers, including every answer to the enterprise-SEO question. That baseline established the starting point for the machine layer.

Query 1

“Which digital marketing agencies should I consider for enterprise SEO?”

EngineModelResultCompetitors namedSHA-256 of answer text
Perplexitysonar-proOmittedDigital Authority Partners; AMP Agency; Clay Agency78c8e9e63e…f4f113
ChatGPTgpt-4.1Omittedb39b18550e…1e3a52
Geminigemini-2.5-proOmitted7b22e100f4…474ef2
Claudeclaude-sonnet-4-5-20250929Omitted9f5727a19d…5ca071
Grokgrok-4Omittedd5d0e91a84…9aa430
Query 1 baseline results by engine, captured 2026-06-17Query 2

“What is the best digital marketing agency in Phoenix AZ for SEO and paid search?”

EngineModelResultCompetitors namedSHA-256 of answer text
Perplexitysonar-proNamed7e7a0a1625…73c8b0
ChatGPTgpt-4.1Omitted307411bf1e…004500
Geminigemini-2.5-proOmittedd2ca88973a…af8541
Claudeclaude-sonnet-4-5-20250929Omitted4b2938a9cf…549f0f
Grokgrok-4Omittedef39d78daf…141bd5
Query 2 baseline results by engine, captured 2026-06-17Results, in order, with the dips

What we observed, on the day we observed it.

Rankings in generative engines move. A sequence that only moved upward would be a sequence that had been edited. This one includes the day ChatGPT dropped V Digital Services entirely.

DateObservation
2026-07-15AnswerShare GEO composite reported as moving from 77 at cutover to 89. This is AnswerShare’s own composite metric, not an engine ranking. No engine placed anything on this date.
2026-07-16Engine audit on the query “Recommend a good digital advertising agency in Phoenix”: Perplexity #1, Grok #1, ChatGPT #2. Gemini and Claude were not measured on this query. Three days after first recorded crawl.
2026-07-19Perplexity, on the query “recommend a digital agency in Phoenix”, run in an incognito browser: V Digital Services cited. The observation was ours, not the client’s — “The citation is important. But look how its opinion of VDS has changed.”
2026-07-22ChatGPT did not surface V Digital Services on two prompts that day. On a “best digital advertising agency in Phoenix” prompt: “You didn’t come up.” Later the same day, on a separate run: “It didn’t list you in the top5.”
2026-07-28An internal email carrying the subject line “VDS from 82 to 90”. The figures appear only in the subject line — the message body does not restate or evidence them. Recorded here for completeness, not offered as a measurement.
2026-08-02Perplexity: V Digital Services #1. The clearest dated first-place result in the record.
Dated observation sequence, 2026-07-15 through 2026-08-02

The 2026-07-16 audit, cell by cell

EnginePosition
Perplexity#1
Grok#1
ChatGPT#2
Gemini—not measured on this query
Claude—not measured on this query
Query: “Recommend a good digital advertising agency in Phoenix”. “—” means the engine was not measured on this query — it does not mean a null result.Current instrumentation

The measurements, including the ones that are not where we want them.

Metric codes are reproduced as they appear on the client dashboard. Where the dashboard and the underlying store disagree, we say so and withhold the figure rather than choose between them.

Crawler traffic

Trailing 30 days as of 2026-08-08. This is a rolling window — it is not anchored to any capture date elsewhere on this page.

15,829Cleaned AI-crawler requeststrailing 30 days5,116User-intent30% of cleaned volume9,282Training1,431Search

Grand total before cleaning: 16,820. Source: crawl log, client_slug vdigitalservices, queried 2026-08-08.

The GEO composite, as a series

AnswerShare’s own composite score — not an engine ranking, and not a third-party measurement. We present it as a dated series rather than a headline number because the stored values disagree with one another.

DateValueWhere it is storedNote
2026-07-1377Reported as the value “at cutover”Email, Robert Maynard, 2026-07-15
2026-07-1589Reported same morningEmail, Robert Maynard, 2026-07-15
2026-07-2790quant_metrics + comparison_scoresBoth tables agree on 90; they disagree on the underlying Grok and Gemini values (97 vs 100)
2026-07-2782quant_metrics, later row, same dayUnreconciled against the 90 recorded hours earlier
2026-08-0292quant_metrics, row id 128Most recent stored value. The client dashboard does not surface it — it still shows 90.
GEO composite values by date and store

The five-model median underlying the 90 was captured 2026-07-27; that is the correct date for that score. A further update ran 2026-08-07, but 2026-07-27 remains the authoritative capture for the composite the dashboard displays.

In band

INFRAInfrastructure100SENSentiment+85ASQAnswer surface quality78RRRetrieval reliability0.991RTCRetrieval time cost0.008TTFBTime to first byte16 msTTLBTime to last byte17 msSCHEMASchema depth2

Out of band, or withheld

SGRtarget ≥ 0.250.211LMRtarget ≤ 30 days53 daysSEOsoft — below the range we consider settled57EGRsoft — below the range we consider settled33%CITEwithheldThe dashboard reads 55%; the underlying store reads 60. Not published until the two are reconciled.RPCdroppedThe dashboard displays 6,176. No corresponding field exists in the measurement store, so we cannot say what it counts. Removed rather than reprinted.2026-08-08/Client dashboard refreshed 2026-08-08; underlying values read from the measurement store the same day.In the client’s words

“Working with the AnswerShare team has fundamentally changed how we think about AI visibility. At V Digital Services, we’ve always focused on helping clients win in search, and we have been very successful at doing it. But it’s a new world. With AnswerShare as a partner, we are now prepared to implement for clients for where “search” is heading next. I have seen, firsthand, the value that perspective brings.”

Kurtis BartonSenior VP of Strategy & Sales, Voice Media Group

Approved for publication by Kurtis Barton, 2026-07-23.

“just wow...”

Kurtis BartonSenior VP of Strategy & Sales, Voice Media Group

Unprompted, on seeing a result. Email, 2026-07-18 21:41 UTC, subject line “wow”. This is the whole message — it is a reaction, not a testimonial, and it is not part of the quote above.

“And the hits just keep on coming!”

Jayson AkersDirector of SEO/AEO/GEO, V Digital

Email, 2026-07-19 15:40 UTC.

What this page does not claim

The limits are part of the result.

This section is not a disclaimer. It is the part of the record that tells you how much weight the rest of it will carry.

No one can guarantee a specific answer to a specific prompt

Not us, not any vendor. What is engineered is retrieval, grounding and trust architecture — the conditions under which a model can find, parse and rely on a source. That raises the probability of a citation. It does not determine any individual generation.

Results vary by user, device, cache and RAG timing

On 2026-07-27 Kurtis Barton ran a prompt from a colleague's computer and got a different answer than he got from his own, and asked why. The honest answer is that the model frequently is not reading the live site — retrieval-augmented generation has its own refresh cadence, and even an explicit instruction to visit the page is not always honoured. Two people running the same prompt on the same day can legitimately see different results.

Email exchange, 2026-07-27

The headline compresses a sequence — it is not a controlled experiment

“Invisible to #1 in 3 days” is the observed order of events: omitted by five of five engines on the enterprise-SEO query at the 2026-06-17 baseline, then first on Perplexity and Grok at the 2026-07-16 audit, three days after go-live. The baseline asked two specific queries; the audit asked a third. A controlled re-run of the baseline queries has not been performed, which is why this page quotes no lift figure and no percentage anywhere.

Our own delivered artifacts are not evidence that the layer works

The machine-readable files now published on the client's domain — llms.txt, llms-full.txt, the MCP manifest, the entity record — are our work product. They belong in the description of what was shipped. They are not third-party validation and are not cited as such here. Every result on this page comes from an engine, a crawl log, or a probe.

Rankings move, and this one moved down

Six days after the audit that placed V Digital Services #1 on Perplexity and Grok and #2 on ChatGPT, ChatGPT returned it on neither of two prompts. That is on the sequence above with its date. A case study that showed only the upward days would be describing a different system than the one that exists.

2026-07-22

Four measurements are out of band right now

SGR is 0.211 against a target of 0.25 or better. LMR is 53 days against a target of 30 or fewer. SEO sits at 57 and EGR at 33% — both softer than we consider settled. These are published beside the strong numbers because a panel with no weak readings is not a measurement panel.

Dashboard, 2026-08-08

Two figures are withheld outright

CITE reads 55% on the dashboard and 60 in the underlying store; we will not pick one. RPC displays 6,176 with no corresponding field in the store at all, so we cannot say what it counts. Both are named here rather than quietly dropped.

Reconciliation, 2026-08-08Methodology and receipts

How to check any of this.

The baseline probe and its receipts exist as files — 30 of them across 10 screenshots, 10 raw API responses and 10 text transcripts, each raw response carrying a recorded SHA-256. The crawl log, the composite series and the instrumentation panel are read from the measurement store and dated at the point of reading.

Our measurement rules, and what we do when a number cannot be substantiated, are written down.

FAQ