LLMs Bureau[1]
LLMs Bureau / AI visibility for UK businesses

Be the name
the assistants give.

Someone asks an AI assistant such as ChatGPT, Claude or Perplexity for a solicitor, a clinic or a tradesperson. LLMs Bureau gets your website read and cited in that answer, then shows you each answer as it is served. We built the method on our own two companies. The readings are below.

LLMs Bureau is a UK answer engine optimisation service for small and medium businesses and professional practices: it gets a website read and cited by AI assistants such as ChatGPT, Claude and Perplexity, then shows the owner every answer the site was used in, with the log line to prove it.

No cookies for visitorsNothing to install to startMonday numbers by email
The bench / readings / source: our server logs Last reading 14 Oct 2026 09:30
0255075100
98%
of the site read by Google in its first nine days
Investigation Bureau / server logs against the sitemap / 5 to 14 Oct 2026
Share of the site each index has read
Google98%
Anthropic94%
OpenAI91%
Amazon Alexa91%
Apple85%
Bing1%

ChatGPT answers from live fetches so far: it read 12 different pages in week one, and one answer drew on five of them. Bing has barely started, which is the gap we are closing.

Answers served by day5 Oct to 13 Oct 2026
5678910111213
ChatGPT read 12 different pages in the first week; one answer on 8 Oct drew on five of them.| first click-through from ChatGPT
051015202530
--
answers served
Your site / no readings yet
Put your site on the bench

No readings yet. We will read your site the way ChatGPT does: the home page as a browser and as the named AI crawlers, plus robots.txt, llms.txt and the sitemap. A score out of 100 and the findings come back on one page.

Reading your site as a browser, as ChatGPT-User, as GPTBot, as ClaudeBot and as PerplexityBot. Ten seconds or so.

Free. No sign-up to see the score. Five checks an hour per visitor. We fetch from our server with each reader's user agent set; rules that check a crawler's address may treat the real reader differently.

036912
10x
answers served a day, once ChatGPT indexed the site
Our address-tracing site / server logs / answers a day, 29 Sep to 9 Oct against 10 to 13 Oct 2026
Share of the site each index has read
Amazon Alexa100%
Meta AI97%
Bing84%
Apple69%
Google43%
OpenAI35%

Pages in the sitemap fetched by each index's crawler, to 14 Oct 2026. Answering people with our pages: ChatGPT, DuckDuckGo AI and Perplexity. Not yet: Claude, Gemini, Copilot.

Answers served by day29 Sept to 13 Oct 2026
293012345678910111213
Answers served a day rose 10x after the crawl; week two was up 300% on week one. ChatGPT sent its first visitors on 14 Oct.| ChatGPT's search crawler took the site in by 10 Oct
Index builders hold the page. Live fetchers read it for a person. We report both and never mix them.The raw figures are in the case files

Two new sites. No backlinks. No paid links. Read by ChatGPT inside a fortnight.

We launched a UK address-tracing service on 29 September 2026. Once ChatGPT's search crawler had taken it in, the answers it served a day rose 10x, and on 14 October ChatGPT started sending visitors, one of them straight to the instruction form. Investigation Bureau went live on 5 October; within nine days Google had read 98% of its pages, Anthropic 94% and OpenAI 91%. A London investigation firm that we show unnamed saw the visitors ChatGPT sent it rise 207% from August to September 2026, in its own analytics, and one of those visits became a £3,300 instruction.

File 01
The fortnight
10x
answers served a day, once ChatGPT indexed the site
Our address-tracing site / server logs / answers a day, 29 Sep to 9 Oct against 10 to 13 Oct 2026
File 02
Five pages, one answer
98%
of the site read by Google in nine days; Anthropic 94%, OpenAI 91%
Investigation Bureau / server logs against the sitemap / 5 to 14 Oct 2026
File 03
The £3,300 answer
+207%
visitors sent by ChatGPT, August to September; one became a £3,300 instruction
A London investigation firm, redacted / its own analytics / Aug to Sep 2026

Sources: our server logs (live fetchers such as ChatGPT-User, and index crawlers such as GPTBot and Googlebot read against each site's sitemap) and the firm's own analytics, never mixed. Every percentage names the periods it compares; the raw figures are in the case files.

The day after ChatGPT's search crawler took the site in, the run started.

Answers served a day rose 10x once ChatGPT had indexed our address-tracing site, week two was up 300% on week one, and 89% of everything ChatGPT has answered from the site came after the crawl. The home page carries 75% of those answers, which means people are asking for the brand or the category by name. On 14 October the first visitors arrived from ChatGPT, one of them straight to the instruction form.

Answers served by day29 Sept to 13 Oct 2026
293012345678910111213
Our address-tracing site / server logs / each column is one full day| ChatGPT's search crawler took the site in by 10 Oct
Share of ChatGPT's answers, by page
home75%
pricing7%
trace-a-debtor4%
reconnect-with-someone + about4%
solicitors4%
developers4%
how-it-works4%

DuckDuckGo AI cited /guides/finding-missing-beneficiaries and /how-it-works; Perplexity cited the home page.

Questions shown as likely are inferred from the page fetched; the question text itself is only visible in Bing Webmaster and Search Console AI reports. Open case file 01.

Each assistant reads a different index, and none of them runs JavaScript.

Google's AI reads Google. Copilot reads Bing. ChatGPT mixes Bing, its own index and live fetches. Claude reads Brave. Perplexity runs its own crawler. No AI crawler we have logged runs JavaScript, so a site that draws its text with code is a blank page to every one of them.

The patch boardShare of our address-tracing site read, 14 Oct 2026
ChatGPTCopilotGoogle AIClaudePerplexityBing 84% readGoogle 43% readBraveOpenAI index 35% readChatGPT search 22%, OpenAI crawler 35%Perplexity crawler 10% readPerplexityLive fetchChatGPT-User, while answeringAssistantReads from

Also reading it: Amazon Alexa 100%, Meta AI 97%, Apple 69%, Anthropic 17%. The share of the sitemap each index's crawler has fetched, from our logs; a log shows fetches, not index membership.

Investigation Bureau, first nine days
Google98%
Anthropic94%
OpenAI91%
Amazon Alexa91%
Apple85%
Meta AI48%

ChatGPT search: not yet; ChatGPT answers come from live fetches   Bing: 1% of the site

Showing our own gaps is the point.

Two views of one page
As a browser
As ChatGPT
Empty until JavaScript runs. Assistants never run it.

A page built this way scores under 30 in the free check. Server-render or pre-render the pages and the right-hand view fills in.

We do not need the keys to your site. One script line and a Monday email.

Start with nothing installed: we ask the assistants the questions your buyers ask and record who gets named. Add one line of script and we see the visitors the assistants send and what they enquire about, without a single cookie. Add a small snippet at your edge and we see every answer served, per assistant, per page, as on the Bench above. Then we write the exact changes, as numbered change orders your developer applies in an afternoon. On the top plan we apply them ourselves.

Needs: Nothing from you

The Monitor

We put the questions your buyers ask to ChatGPT, Claude, Perplexity and Gemini and record who gets named, in what position, and who is named instead of you.

Named or not, per question, per assistant, with history from day one.

Needs: One line of script

The Tag

A script served from our domain, no cookies, no browser storage. It sees the visitors an assistant sends, the pages they read, phone taps and form sends.

Visitors from assistants, and enquiries attributed to the assistant that sent them.

Needs: A Cloudflare Worker or Node middleware

The Edge Tag

Crawlers do not run scripts, so a page tag never sees them. A small snippet at your edge reports each crawler hit as user agent, path and status, never an IP.

Answers served per assistant per page, and which index crawlers have fetched which pages. WordPress plugin and PHP middleware: coming.

Needs: A developer's afternoon

Change orders

We read your site the way an assistant does, score it, and write each fix as a numbered copy-paste block: the exact paragraph, the exact schema, the exact robots lines, the whole llms.txt.

Applied, verified or pending, with the reading each order was meant to move and whether it moved.

The Monday brief / 08:00 / one email, two phone screens longSpecimen from our address-tracing site's readings
Subject: Readings to 14 Oct 2026: answers served up 300% week on week

READINGS        answers served a day up 10x since ChatGPT indexed the site
PAGES CITED     home page 75% of answers; pricing, trace a debtor, reconnect with someone, for solicitors, developers, how it works
COVERAGE        Amazon Alexa 100%, Meta AI 97%, Bing 84% of the site read
CLICK-THROUGHS  the first from ChatGPT on 14 Oct, one to the instruction form
NEXT            one change order, with the exact text to paste

Every figure in the brief is the client's own, with its date range. Inferred questions are marked likely. How it works in full.

Type your domain. We read it the way ChatGPT does.

We fetch your robots.txt, llms.txt, sitemap.xml and home page live, as a browser, as ChatGPT-User and as GPTBot, and we check whether ClaudeBot and PerplexityBot are let in. If your edge blocks a crawler, it shows. You get a score out of 100 and the findings in plain words. No sign-up to see the score. Five checks an hour per visitor; results stay at a link you can send to your developer.

Reading your site as a browser, as ChatGPT-User, as GPTBot, as ClaudeBot and as PerplexityBot. Ten seconds or so.

We fetch from our server with the reader's user agent set; rules that check a crawler's address may treat the real crawler differently. Rate limits are per visitor address, hashed daily. More about the check.

Three plans. Pounds, monthly, cancel when you like.

Watch shows you every answer served and whether you are named. Fix also writes the changes. Run applies them and writes one piece a week. The Audit is a one-off at the price of a month of Fix, credited in full against your first month of Fix or Run if you join within 30 days. We never promise a position. We show you the readings.

Watch
£49a month

A business that wants to see every answer its site is used in, and to know whether the assistants name it and who they name instead.

  • The Edge Tag: a Cloudflare Worker or Node middleware (WordPress plugin and PHP middleware coming) that reports crawler hits as user agent, path and status, never an IP, so you see answers served per assistant per page, and which index crawlers have fetched which pages
  • The Tag: one script line, no cookies, showing visitors sent by each assistant, the pages they read, phone taps and enquiries attributed to the assistant that sent them
  • The Monitor: up to 20 of your buyers' questions put to ChatGPT, Claude, Perplexity and Gemini every week
Start on Watch
Run
£599a month

A business or practice that wants the bench run for it, including the writing. One site of up to 50 pages; larger sites by quote.

  • Everything in Fix, with 100 questions twice a week and 5 competitors tracked
  • We apply the change orders ourselves through a named editor login on your CMS or as pull requests to your repository; you approve each change before it publishes and every change is listed in the dashboard
  • One dated, answer-first article a week, written for your approval, published with FAQ schema and a Markdown twin
Talk to us about Run
The Audit / £149 once

The site read the way the assistants read it (no JavaScript, as a browser, as ChatGPT-User and as GPTBot, up to 25 pages), scored out of 100 across Reachable, Readable and Declared, with numbered change orders a developer can apply in an afternoon, delivered within five working days as a dated web page with a 30-minute call; credited in full against the first month of Fix or Run started within 30 days.

Book the Audit
Prices in pounds a month. No minimum term. No VAT charged at present.Compare everything

The questions people ask the assistants about this. Answered first, dated, quotable.

Every guide opens with the answer and carries the date it was written. That is how we write for clients and it is how we write for ourselves.

2026-10-13

What is answer engine optimisation, and how is it different from SEO?

SEO wins a position on a results page; answer engine optimisation wins a mention inside the answer, where there is often no link to click at all.

2026-10-13

Why does ChatGPT not mention my business?

ChatGPT leaves a business out because it cannot read the site, because the site does not answer the question asked, or because nobody else on the web mentions it.

2026-10-13

Do AI assistants read JavaScript websites?

An AI assistant reads the HTML your server sends and nothing more: if your words only appear after JavaScript runs, to the assistant your page is blank.

2026-10-13

How do I know if ChatGPT has read my website?

Your analytics tool cannot see ChatGPT reading your website; the only record is a single line in the server access log, written at the moment a person asked a question.

2026-10-13

How long does it take to get cited by an AI assistant?

Both of our new sites were fetched by an AI assistant to answer a real question inside a fortnight of going live (server logs, September and October 2026).

2026-10-13

Which AI crawlers should I allow in robots.txt?

A robots.txt that blocks GPTBot but allows OAI-SearchBot keeps you eligible for ChatGPT's search results today and out of the model's memory tomorrow.

2026-10-13

What is llms.txt and does it help?

llms.txt is a free, harmless map of which page answers which question; publish one, but do not expect it to get you cited on its own.

All guides. Also served as Markdown twins and in llms-full.txt.

Put your site on the bench.

Run the free check, or start on Watch at £49 a month. Readings arrive every Monday. Cancel whenever you like.

Last reading 14 Oct 2026 09:30

Agencies: ask us about running Fix for your clients, [email protected].