Case study · October 23, 2026

Three weeks of Answers on our own site

On October 7, 2026 we turned Proxylang Answers on for proxylang.dev. It writes answer-first articles on answers.proxylang.dev and asks five AI assistants our customers' questions every week. Here is what happened, including the weeks where nothing moved.

What we published

28 articles went live on answers.proxylang.dev between October 6 and October 18: 21 in English, 5 in Korean and 2 in Japanese. Each one is written in its own language, not translated. 2 more failed our fact check and wait for a person to look at them.

Who came to read them

AI and search crawlers found the articles within days. From October 7 to 23 they visited answers.proxylang.dev 427 times:

CrawlerRun byVisits
ClaudeBotAnthropic331
GPTBotOpenAI49
BingbotMicrosoft23
OAI-SearchBotOpenAI (ChatGPT search)20
PerplexityBotPerplexity4

Did AI start naming us?

Every week we ask ChatGPT, Claude, Gemini, Grok and Perplexity the same questions, one answer each. Some questions already say "Proxylang". Most don't: they are what a buyer types before they have heard of us.

Weekly checkAsked by name: named usGeneral question: named us
October 810 of 100 of 39
October 1510 of 100 of 40
October 2215 of 152 of 85

Asked by name, every AI knew us from the start. Asked a general question, none named us in the first two weeks. On October 22, for the first time, two did: asked "Is there a no-code translation service that supports 77 languages?", Perplexity and Gemini named Proxylang; Gemini also linked to proxylang.dev. That week we also doubled the questions we track to 20, adding Korean and Japanese ones, which is why the counts jump.

What we take from it

  • Getting read is fast. The crawlers came in the first week.
  • Getting named for general questions is slow. Two answers out of 85 is a start, not a result.
  • We keep publishing and checking every week. The newest numbers are on the Answers page.