Case study Updated

Our sample site’s first 7 days: 333 visitors from ChatGPT

Short answer

An AI-powered consumer web app we launched from zero on 21 September 2026 got 333 real visitors from ChatGPT in its first 7 days, 5.3 times as many as from search engines, while Bing had indexed none of its pages (the site’s own analytics, human sessions only). Most arrived on two pages written for a customer’s situation; Perplexity, Copilot and generic “best X” questions sent nobody.

About this case study

  • Whose site: an AI-powered consumer web app that we built and launched on 21 September 2026. It’s our own product (the company that runs katman.pro), not a client. We don’t name it or its category on purpose.
  • Source: the site’s own analytics database (Cloudflare D1), read-only queries, 21 September 00:00 to 28 September 00:00 UTC.
  • Only humans: 528 of 1,546 sessions passed our human filter (the rule is below). The filter is cautious: about three in ten real sessions fail it.
  • Also used: server-side bot counts, Search Console, and ChatGPT answers we recorded by hand.

The same numbers are in chapters 2, 10, 11 and 17 of our book.

The result in one table

Measure Value
Real visitors from ChatGPT 333 (63% of all human traffic)
From search engines (Google, Yandex, Brave) 63, of which 52 from Google. ChatGPT sent 5.3 times as many
From Bing 0: Bing hadn’t indexed a single page that week
First ChatGPT visitor About 1.5 days after launch (22 September, 23:01 UTC)
Accounts whose first visit came from ChatGPT 72 of 102 (71%)
Paying customers whose first visit came from ChatGPT 11 of 17 (65%)
ChatGPT visitors who landed on two situation pages 59%
Brought by one situation page alone 31 accounts and 8 paying customers

Day by day

Date ChatGPT visitors What we did What happened
21 Sep 0 Launch. All text in plain HTML; AI bots allowed in robots.txt; sitemap, llms.txt and llms-full.txt; JSON-LD, FAQ and canonical on every page. Search Console verified by DNS, sitemap submitted GPTBot made 313 requests on day one
22 Sep 4 A two-word distinctive name and a “we’re not X” line; separate robots.txt groups for 22 AI bots; date and author on every page; FAQs built from data on 34 category pages; 76 single-question pages from Google autocomplete; list guides that name competitors; Bing verified; 6 pages sent to Brave; two PDF books published OAI-SearchBot read 37 pages; a PDF link checker created fake sessions; first ChatGPT visitor at 23:01
23 Sep 43 Fixed a form error that stopped new users before the checkout screen Bing still had 0 pages
24 Sep 40 Indexing diagnosis and fix; an 86-word written section on the JavaScript quiz page; honest lastmod dates; IndexNow for changed URLs only; a file drop box on the two pages ChatGPT linked to most; 5 new pages Perplexity measured: named in 0 of 12 questions
25 Sep 80 25–27 Sep: new situation pages, an honest comparison with a big competitor, three free tools, YouTube videos on the pages, Bing’s URL Submission API in the deploy script, 6 languages with their own URLs and hreflang First recommendation in situation questions
26 Sep 76 (continued)
27 Sep 90 (continued)

On 28 September, a technical SEO pass took the home page’s mobile Lighthouse performance score from 59 to 89, and after the 29 September audit to 98 (lab measurement).

Where the visitors came from

528 human sessions, 21–27 September 2026.

Channel Sessions Quiz Sign-up Checkout screen Purchase
ChatGPT 333 63 15 60 5
Direct (typed address, bookmark) 109 13 4 22 4
Search engines 63 12 1 7 1
Social media 12 0 0 1 1
Other sites 7 0 0 0 0
TikTok 2 0 0 0 0

“Purchase” here means a purchase in the same session; the 72 of 102 accounts and 11 of 17 payers above are counted by the channel of the account’s first visit. Much of “Direct” is probably ChatGPT too: 79% of ChatGPT visitors sent no referrer, and we only recognised them by the utm_source=chatgpt.com tag in the link.

Who they were: visitors from 59 countries, led by the US, France, India, Germany, Nigeria, Spain and Brazil; 71% on mobile. ChatGPT visitors viewed 2.45 pages on average, scrolled through 57% of the pages they opened and stayed 198 seconds. Visitors from search engines viewed 2.33 pages and stayed 258 seconds.

Where they landed

Page ChatGPT visitors
Situation page A 127
Home page 84
Situation page B 68
List guide A (“which tools are there for X?”) 13
List guide B 11
Other pages 30

The two situation pages took 195 of 333 visitors (59%). The two honest list guides, which name competitors and don’t put us first, took 24.

Questions asked in ChatGPT with web search on, 26–28 September 2026 (own measurement). We describe the question types and don’t give the real texts, so the site stays anonymous:

Question type Result
A long question describing the situation: what the user has, what they can’t do, what they want First, described as probably the most direct match. Second in another session, which ended by suggesting trying [Brand] first
Another situation question: what they want done with the file they have First. Third in another account
A short tool question: “Which AI tool does [the job]?” Not named: two big brands
A how-to question: “How do I do [this] with AI?” Not named
“Best [category] 2026” Not named: four big brands

The same question can get a different answer in a different session; one run is a sample, not a rank. Perplexity didn’t name the site for any of these questions.

ChatGPT also used our own words. The site’s one sentence stood in the first paragraph, the meta description and llms.txt, in four parts: what the user brings, what the site does in measurable words, what they get back, and the promise that removes the fear. In two separate sessions on 28 September, the answers repeated all four parts, almost in our own words. An invented sentence with the same shape: “Upload your invoice. We move the line items into your accounting software in 30 seconds and flag the ones that don’t match. Your document is never stored.”

What the bots did

Counted on the server, 21–27 September 2026. Bots don’t run analytics scripts, so browser analytics can’t see them.

Bot Whose, what for Requests Distinct pages
Googlebot Google search 778 305
YandexBot Yandex 773 341
ClaudeBot Anthropic, training 578 379
GPTBot OpenAI, training 362 98
OAI-SearchBot OpenAI, ChatGPT search index 205 176
ChatGPT-User OpenAI, pages opened in a chat 191 19
Claude-User Anthropic, pages opened in a chat 122 64
Bingbot Microsoft, Copilot 17 10
PerplexityBot Perplexity 8 6

Turning visitors into customers

People from ChatGPT arrived with the situation they had already described, usually holding a file they wanted to work on. What we changed:

  • A file drop box on the two pages ChatGPT linked to most. 52 of the first 68 generations used the visitor’s own file.
  • No repeat questions: the start quiz lost about 40% of people at its first question, so visitors from ChatGPT now skip it.
  • The right plan: four people who arrived with a file bought a plan that didn’t accept files, and two cancelled within an hour. Checkout now opens on the plan that matches the visitor’s intent.
  • The right payment method: with 71% of visitors on mobile, 7 checkout pages opened on 23 September and 1 was paid. Google Pay was switched on that night.

What didn’t work

  • Perplexity: named in 0 of 12 buyer questions; PerplexityBot made 8 requests. It also filed the site as a “template and education site”, because about 110 template pages outnumbered about 10 product pages.
  • “Best X” questions: ChatGPT listed big brands every time.
  • Bing and Copilot: 0 pages indexed on 24 September despite every submission, and 0 Copilot citations.
  • Claude: Claude-User opened pages 122 times, and claude.ai sent 0 clicks. Being read isn’t being clicked.
  • PDF books: the first ChatGPT visitor came about 8 hours after the PDFs went up, but that’s a sequence, not a cause; ChatGPT linked the feature pages, not the PDFs.
  • Google organic: Search Console’s 28-day view on 28 September showed 32 clicks and 306 impressions, almost all for the brand name.

Limits of this evidence

This is one consumer AI app in one category over one week, and the site was built for the method from day one. It’s our own product, so we have an interest in the result; that’s why the numbers come with their source and filter. AI answers change between sessions, and the human filter undercounts. Read it as a worked example of the Katman method, not as a forecast for your site.

What to copy

  1. One page per customer situation, with the answer in the first sentence.
  2. One sentence in four parts, identical in the first paragraph, the meta description and llms.txt.
  3. Text in plain HTML and AI bots allowed, from day one.
  4. ChatGPT counted by utm_source=chatgpt.com, not only by referrer, and bots filtered out.

If you want your AI coding tool to do this with checks at each step, see Katman. The background is in What is GEO?.

Frequently asked questions

Which site is this?

An AI-powered consumer web app we launched on 21 September 2026. It’s our own product (the company that runs katman.pro), not a client, and we don’t name it or its category on purpose.

How do you know the visitors came from ChatGPT?

From a chatgpt.com referrer or the utm_source=chatgpt.com tag in the link. 79% of the ChatGPT visitors had only the tag and no referrer.

Were these real people?

We counted only sessions that passed a human filter: the visitor scrolled, saw more than 2 pages, finished the quiz, signed up, paid or came from an in-app browser. 528 of 1,546 sessions passed.

Why didn’t Bing matter?

Because ChatGPT searches its own index. Bing had 0 of the site’s pages on 24 September 2026, the day ChatGPT sent it 40 visitors.

Can I expect the same results?

Nobody can promise that. This is one site in one category over one week, built for the method from day one; read it as a worked example.

What made the biggest difference?

Situation pages with the answer in the first sentence. 59% of ChatGPT visitors landed on two of them, and one brought 8 of the 17 paying customers.