Methodology8 stages

The Answer Chain: how LoudFace gets a B2B SaaS named in AI answers

Our own domainJune to August 2026, our own domain
ChatGPT6.2%15.9%
Google AI Overviews12.3%8.0%
Blended9.4%12.4%

The blend moved from 9.4% to 12.4% and showed neither.

The short answer

The Answer Chain is LoudFace's eight-stage generative engine optimization (GEO) method for getting a B2B SaaS named in AI answers. LoudFace measures that work against revenue outcomes rather than vanity metrics. Share of answers and citations are tracked per engine, then read against search demand, signups, booked demos and captured leads. Engagements start from $5,000 a month.

The eight stages, in order: baseline per engine, crawler access, brand entity, liftable artifact, original material, third-party corroboration, selective placement, and per-engine reporting through to revenue.

Why the method starts with a distinction most agencies skip

Three different things happen inside an AI answer, and they happen separately.

ChatGPT, 40 answers sampledRetrieve, cite, name
Answers sampled
40
Retrieved a page
24
Named LoudFace
7

Each step can fail while the one before it succeeded.

The citation step is not drawn: this read counted answers, not citations.

We know the size of that gap because we measured it on ourselves. Across 120 recent AI answers, 40 on each engine, ChatGPT retrieved a loudface.co page in 24 of 40 answers and named LoudFace in 7 of them. In 30 days, mentions of LoudFace across the three engines rose from 968 to 1,905 while citations of our URLs stayed nearly flat, 4,075 to 4,183. Being read is not being recommended.

The Answer Chain moves a brand along those three steps, and it shows you where a brand currently stalls.

30 days, three engines

Mentions of LoudFace

from 968 moved

1,905

Citations of our URLs

from 4,075 flat

4,183

Every visibility number is measured against revenue

LoudFace measures AI search work against revenue outcomes, not vanity metrics.

1Engine signals, per engineshare of answers, citations, position, sentiment
2Search demandclicks and impressions, your own property
3AI-referred visitsfirst touch
4Signups, booked demos, lead capturethe events your site collects
5Revenuejoined to your CRM

Every signal in the method is a means to that end. Share of answers, citations, position when cited and sentiment are tracked on each engine separately, and clicks and impressions come from your own Search Console property. Each one is then read against the commercial events on your side: signups, booked demos, and any other lead capture you run. A program that moves the visibility numbers and leaves the pipeline flat is a program we call failing, and we say that in the report rather than leading with the chart that went up.

That standard only holds if the readings behind it are public, and ours are. We publish first-party studies instead of resting on other people’s statistics: a 90-day citation study of our own category, and a public record of our own domain’s share of answers over time. We record a per-engine baseline before any work starts, so later movement is compared against a number that existed first. Every factual statement on a page we ship is tied to a persisted primary source. And we publish the readings that make us look weak next to the ones that do not. The weakest numbers we hold, our own AI-referred traffic and our own AI-attributed lead capture, are published with the floors labelled rather than left out.

Each of the eight stages exists to move one link of the chain from engine signal to commercial event.

The eight stages

Each stage opens onto the same three things: what we do, what it outputs, and the reading that says whether it worked.

Stage 1. Baseline, per engineWe measure before we ship.

We measure before we ship. Share of answers naming your brand, citations of your URLs, average position when cited, and sentiment, on every tracked prompt, on each engine separately. That baseline is the number every later claim is compared against. Without it, an agency can attribute any later movement to its own work.

Stage 2. AccessEach engine documents which crawler decides eligibility, and they are not the same crawler.

Each engine documents which crawler decides eligibility, and they are not the same crawler.

OpenAI states that "OAI-SearchBot is used to surface websites in search results in ChatGPT’s search features" and that "Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though can still appear as navigational links." GPTBot is a separate control and governs training rather than search. Perplexity states that "PerplexityBot is designed to surface and link websites in search results on Perplexity." Google states that to appear as a supporting link in AI Overviews or AI Mode, "a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements."

So stage 2 is unglamorous and non-negotiable. It means robots rules, and indexing that leaves the page eligible for a snippet. It also means text that exists in the HTML rather than only after a script runs. We confirm which crawlers actually arrived by reading the raw server logs, rather than trusting a tracker’s estimate. We do that where your hosting gives us access to them. Where it does not, we tell you, and the crawler picture comes from the tracked readings alone.

Stage 3. EntityAn engine can only repeat language it can find.

An engine can only repeat language it can find. If your category label reads one way on the homepage and another way on the service pages, and your verticals drift with it, the engine invents its own summary, and its invention is usually the flattest thing it can say about you.

We fix one sentence that describes the company, one category name, the named verticals, and the proof that travels with them. Then we put that same wording on the homepage, the service pages and every roster entry that names you.

The category label matters too. The engines treat generative engine optimization (GEO) as the head term, with answer engine optimization and AI search optimization as synonyms. We use the words a buyer would actually type, rather than only the ones we prefer.

Ours reads like this: LoudFace is a full-stack organic growth agency for B2B SaaS, running SEO, AEO and GEO, content and Webflow as one program on a single retainer, measured as share of answer rather than traffic alone. Getting those exact words onto every surface, our own site included, is the stage 3 work.

Stage 4. ArtifactFormat decides citation.

Format decides citation. In our own 90-day study of 128,515 citations in the B2B SaaS growth-agency category, listicles carried 52.76% of every citation, more than every other page type combined. Our own most-cited page is a listicle as well. It carried 819 citations in the 30 days to 1 September 2026.

The pattern underneath that number is simple. Engines lift a pre-formatted unit: a ranked list that names brands with a one-line verdict, or a comparison table with real figures, or a short answer at the top of the page. A page that buries the same content in prose gets fetched and skipped. So every page we build for a buyer prompt leads with the unit that prompt wants, in the first screen.

Our own August 2026 output points the same direction on a small sample. We published sixteen pieces. The three listicles among them have earned 12 citations between them so far, and the other thirteen earned 2.

128,515 citations, 90 days, B2B SaaS growth-agency category

52.76%Every other page type

Listicles carried more of every citation than every other page type combined.

Stage 5. Original, not simulatedFormat decides which pages an engine reaches for. What sits inside the page decides whether your brand survives the answer.

Format decides which pages an engine reaches for. What sits inside the page decides whether your brand survives the answer.

So we do not publish thin programmatic pages, and we do not publish pages engineered to look original. Every page we ship is built from material nobody else holds. That material comes from three places, and a gate stands over all three. Each one is a step in the build with an output we can show you.

Your own measurement. Share of answers per engine, your Search Console data, and server logs showing which AI crawler fetched which page and when. The server logs come in only where your hosting gives us access to them. Those readings exist because we took them, on your domain, in a window we recorded. A competitor can restate a public statistic. They cannot restate yours.

Your experts, captured. Every correction and expansion your subject-matter people make to a draft becomes a proposed entry in a knowledge base of your positions, your results and the claims your category avoids. You approve each entry before it is written in. The next piece starts from that base. Expertise compounds across a program instead of evaporating in one revision round.

A source behind every claim. Every factual statement in a draft is tied to a persisted primary source and listed in a claims manifest that travels with the draft. A statistic with no source does not reach a page.

A gate before anything ships. Deterministic checks reject stock phrasing and unsourced numbers, and any self-praise our own record does not support. A second reviewer, with no memory of writing the piece, then re-reads it against the voice rules and re-checks every claim against its source. A page that states a price, or a number a buyer can check, needs two independent approvals before it goes live.

Those three inputs, and the gate that stands over them, decide what a competitor can take from you. A rival can rebuild your page structure, and a content tool can flood your category with pages about it. Neither can produce your readings, your experts’ corrections, or the sources standing behind them. That is what we mean by original.

Stage 6. CorroborationThis is the stage most programs never reach, and it is the one that separates being cited from being recommended.

This is the stage most programs never reach, and it is the one that separates being cited from being recommended.

Our own data makes the case against ourselves. Of 975 third-party pages the three engines cited in our category over 30 days, 4 mention LoudFace. In our own sample of 120 recent AI answers, 40 on each engine, LoudFace was never named unless one of our own pages was in the sources. A brand that is only ever named from its own pages has a ceiling.

Stage 6 targets the specific pages each engine already retrieves for your buyer prompts, and works to be evaluated for inclusion in them. We open by telling the publisher how the engines treat their own page: how often each engine cites that URL, given in full and hedged to the sample it came from, with the full per-engine report for that page free and with no strings. Where we genuinely rate a page, we offer to link to it from ours, and that offer stands whether or not our own placement lands. We never make the link conditional. Our own lists stay independent, and we disclose our placement on them.

Third-party pages the three engines cited, 30 days

4 of 975cited third-party pages that mention LoudFace

A brand that is only ever named from its own pages has a ceiling.

Stage 7. Selection over volumeCorroboration only counts when the page doing it is one an engine already uses.

Corroboration only counts when the page doing it is one an engine already uses. Buying hundreds of backlinks fails that test, and so does placement on a site the engines never fetch. A link no answer engine reads is a line in a report.

The bar is how many citations a page actually earns across ChatGPT, Perplexity and Google AI Overviews. We rank the candidate pages by that count and work from the top of the ranking down. On the target list for our own category, the top third-party page was cited 523 times in 30 days. Those are the pages worth being on.

The standard we select against is a placement we expect to move share of answer by several points on the prompts it touches, on its own. One page like that is worth more than a hundred ordinary links. We are not claiming a week-one result, because we have not measured one. What we do is record the per-engine baseline before a placement lands, read it again in the weeks after, and report the number either way.

That standard means we pursue few placements, and we lose some of them. We would rather show you one page that moved the number than a list of fifty that did not.

Stage 8. Report, per engine, through to revenueEvery reporting cycle reads as a chain, in this order.

Every reporting cycle reads as a chain, in this order.

  1. Engine signals, per engine. Share of answers, citations of your URLs, position when cited and sentiment, on ChatGPT, Perplexity and Google AI Overviews separately. Never one blended figure. Between June and August 2026 our own ChatGPT share rose from 6.2% to 15.9% while our Google AI Overviews share fell from 12.3% to 8.0%. The blend moved from 9.4% to 12.4% and showed neither.
  2. Search demand. Clicks and impressions from your own Search Console property, so the classic-search side of the same corpus sits next to the answer-engine side.
  3. AI-referred visits. How many people arrived on your site from an AI assistant, by first touch.
  4. Signups, booked demos and any other lead capture. The commercial events your site actually collects.
  5. Revenue. Those events joined to your CRM, so a booked demo can be followed to what it became.

A rise at step one that never reaches step four is a finding rather than a result, and it changes what we ship next. Where a link in the chain is thin, we report the thinness rather than filling it in.

June to August 2026, our own domain

ChatGPT6.2%15.9%
Google AI Overviews12.3%8.0%
Blended9.4%12.4%

The blend moved from 9.4% to 12.4% and showed neither.

What we measure

Eight readings, each with the question it answers and the source it comes from. Two of them are floors rather than totals, and the table says which.

What LoudFace measures, what each metric answers, and where it comes from
MetricWhat it answersWhere it comes from
Share of answers naming the brandHow often does an engine name you at all, on the prompts your buyers ask?Peec AI, per engine, per prompt
Citations of your URLsWhich of your pages does the engine actually use as a source?Peec AI, url-report, cross-checked against server logs where your hosting gives us access to them
Position when citedWhere in the answer do you sit? First carries more weight than eighth. This is Peec's own unit: position in the answers where one of your URLs is cited.Peec AI
SentimentHow warmly does the engine describe you when it does?Peec AI, per engine
Clicks and impressionsIs the same corpus still earning classic search demand?Google Search Console, your own property
AI-referred visitsFloor, not a totalHow many people arrive on the site from an AI assistant?PostHog, first-touch
Signups, booked demos, other lead captureFloor, not a totalHow many of those visits became a commercial event?Your site's own capture, read in PostHog
RevenueWhat did those events turn into?Your CRM, joined to the captured events
Floor, not a total

Two of these rows are floors rather than totals, and we label them that way every time. AI-referred visits and AI-attributed lead capture both depend on a referrer being present. Our own 28-day figure is 63 AI-referred visitors, 51 of them from ChatGPT, and 2 of 43 booked calls in 90 days carried an AI engine as first touch. Another 11 leads in that window carry no first touch at all, so 2 is a floor rather than a total. We hold no evidenced revenue figure attributable to AI search yet, on our own domain or a client’s, so we report the chain and the floors rather than a revenue number we cannot stand behind.

The engines we track, and the ones we do not

Read
Tracked panelChatGPT, Perplexity, Google AI Overviews
One-time snapshotGemini, Claude, Copilot
Scope
We track ChatGPT, Perplexity and Google AI Overviews. Every number we report is broken out by those three.
We do not run the ongoing, per-prompt tracked panel described above on Gemini, Claude or Copilot.
Cadence
Ongoing, not a point in time
A single point in time
Granularity
Per prompt, per engine, never blended
Broader engine set, lighter-weight read
Baseline
Baseline recorded before any work starts
No per-prompt sampling behind it
Metrics
Share of answers, citations, position, sentiment
No share-of-answer figure reported inside an engagement

Our analytics record AI-referred visits, and they do not attribute every one of those visits to a named engine. There is no per-prompt sampling behind that traffic either. So we report no share-of-answer figure for any of the three inside an engagement.

A one-time snapshot tool can still score a broader set at a point in time; that is a different, lighter-weight read than the tracked panel this page describes, and we label the difference every time we quote a number.

If someone quotes you a single "AI visibility" score across seven engines, ask which seven, how each is sampled, and whether it is a snapshot or a tracked panel.

Proof

Our own domain

12.84%

of AI answers name us, 30 days to 2 September 2026

0.18%April 2026
10.4%June 2026
12.84%30 days to 2 Sep

We ran this method on loudface.co and published the full record. Our share of the AI answers in our category went from 0.18% in April 2026 to 10.4% in June. April was 8 brand mentions across 2,747 monitored answers. June was 1,245 mentions, on a much larger pool of answers. In the 30 days to 2 September 2026, we are named in 12.84% of AI answers on our tracked prompt set, and our average position when cited is 2.8, across a tracked set of 26 agencies.

Read the full record

The category study

128,515

citations read across three engines

We published a 90-day, first-party citation study covering 128,515 citations across ChatGPT, Perplexity and Google AI Overviews. It found loudface.co to be the single most-cited source domain in the category with 6,616 citations. Inside that corpus, over that window, the most-cited source domain and the most-named brand were not the same company. That study is public and the method is in it: Who AI actually cites in the B2B SaaS growth-agency category.

Read the study

A client

97.8%

of AI answers on "best stablecoin payroll providers"

Toku appeared in 97.8% of AI answers on “best stablecoin payroll providers”, the highest of any brand on that prompt. On “best stablecoin payroll solutions for crypto and Web3 companies” the figure was 93.4% at an average position of 2.5, up from 86% in the spring window. Both come from the 30-day read ending 19 August 2026, across 95 tracked prompts. LoudFace was Toku’s growth partner for 18 months, and the 2024 site foundation is part of why the AI work compounded as fast as it did. Those figures are visibility readings, which means how often Toku appears at all. They are not share of voice, and they are not a three-month result.

Read the case study

What we do not promise

The engines decide, they change their minds weekly, and nobody who tells you otherwise can show you the mechanism. What we can do is raise the probability, then show you the number moving, per engine, against a baseline we recorded before we started.

We also do not sell tactics Google has publicly said do not work. Its own documentation is direct:

No guaranteed placements

We cannot promise you a citation.

No sold position

Position is not ours to sell either.

There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary
Google Search Central
Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add
Google Search Central
and of llms.txt-style files,Google Search ignores them
Google Search Central

We corrected three of our own published articles on 31 August 2026 for overstating exactly these levers. We would rather fix our own copy than sell you a trick.

from$5,000a month

What it costs

Engagements start from $5,000 a month. Pricing depends on tier, scope and complexity, and every engagement starts with an intro call where we scope it. A fixed scope runs inside a retainer with a three-month minimum. For the right partnership we tie part of the fee to results, case by case. The full breakdown is on the pricing page. Our SEO and AEO program and our GEO program both run on this method.

Minimum
Three months, fixed scope inside a retainer
Scoping
Every engagement starts with an intro call
Performance
Part of the fee tied to results, case by case

Where to start

Run the free AI visibility audit. It is the one-time snapshot version of the baseline stage above: an AI search presence score for your brand across ChatGPT, Claude, Gemini and Perplexity, a side-by-side competitor comparison, one fix you can implement within a week, and a personal Loom from Arnel on the AEO gaps costing you pipeline visibility. It checks a broader set of engines than the tracked panel above, at a single point in time rather than on an ongoing per-prompt basis.

What comes back

  • An AI search presence score across ChatGPT, Claude, Gemini and Perplexity
  • A side-by-side competitor comparison
  • One fix you can implement within a week
  • A personal Loom from Arnel on the AEO gaps costing you pipeline visibility

Nine questions buyers actually ask

Every answer here carries the same readings as the page above, and the numbers that are floors rather than totals say so.

How long until we get cited in AI answers?
Three different clocks. A well-structured page on a brand with existing authority can be cited within a day on a prompt with no entrenched winner. Holding a slot in the cited-source set takes weeks of re-evaluation. Winning a competitive prompt cluster takes months. Most agencies sell the fast clock and bill for the slow one.
What is the difference between a citation and a mention in answer engines?
A citation is the engine listing your URL as a source. A mention is the engine naming your brand in the answer text a buyer reads. They move independently. Over 30 days our own mentions went from 968 to 1,905 while citations of our URLs went from 4,075 to 4,183. Buyers act on mentions.
How is your content different from thin programmatic pages?
Every page is built from material only you and we hold: your per-engine measurement, your experts’ own corrections proposed as knowledge base entries that you approve before they are written in, and a primary source behind every factual claim. A gate then blocks unsourced numbers and stock phrasing. Volume is cheap. Material nobody else holds is what earns citations.
Do you use schema markup, llms.txt or word-count tricks?
No, and we say so because Google says so. Its documentation states that structured data is not required for generative AI search, that there is no special schema.org markup to add, and that llms.txt-style files are ignored. We use schema where it helps normal search. We do not sell it as an AI-citation lever.
Which AI engines do you track?
ChatGPT, Perplexity and Google AI Overviews, measured separately on every prompt. We do not run continuous prompt-level tracking on Gemini, Claude or Copilot. Our analytics record AI-referred visits without attributing every one to a named engine, and no per-prompt sampling sits behind that traffic, so we report no share-of-answer figure for any of the three. We would rather report three engines honestly than seven loosely.
Why report per engine instead of one AI visibility score?
Because the engines move in opposite directions and a blend hides it. Between June and August 2026 our ChatGPT share rose from 6.2% to 15.9% while our Google AI Overviews share fell from 12.3% to 8.0%. The blended number moved from 9.4% to 12.4% and told you nothing about either.
Do you report revenue or just visibility?
Both, in that order, as far as your data reaches. We report per-engine share of answers, citations and position, then Search Console clicks and impressions, then AI-referred visits, then signups, booked demos and other lead capture joined to your CRM. We hold no evidenced revenue figure attributable to AI search yet, so thin attribution is labelled a floor.
Can you guarantee we will be named in ChatGPT?
No. The engines decide, and they change their selections week to week. Anyone guaranteeing a placement is either not measuring or not telling you. We commit to a recorded baseline, a documented method, per-engine reporting, and honest labels on numbers that are floors rather than totals.
What does an engagement cost?
Engagements start from $5,000 a month. The figure depends on tier, scope and complexity, and we scope it on an intro call. A fixed scope runs inside a retainer with a three-month minimum. For the right partnership we tie part of the fee to results, case by case.