Field notes

Kisumu, language and AI visibility

The blog follows composite small AI-visibility failures around Kisumu: a Dunga operator with a weather-dependent schedule described as generic lakeside tourism, a cooperative with unclear pickup points losing its route signal, and a fish trader cited through a directory but not through its own words. I publish one field-style article each week on a single failure, plus a monthly landing phrase ledger comparing English, Swahili and local place wording.

Trade, proof & time

When AI Invents Kibuye Market Hours

Kibuye trader opening hours get hallucinated when AI lacks freshness signals, update cues and cautious wording for market-based businesses.

Routes, sources & entities

When Swahili Changes A Restaurant Answer

How Kisumu restaurant Swahili AI answer differences happen, and how lakeside restaurants can align place, food and customer signals.

Routes, sources & entities

When Cross Border Traders Read As Local Only

Kisumu Uganda trade business wording must name routes, buyer types and coverage limits so AI does not reduce cross-border traders to local shops.

Routes, sources & entities

When A SACCO Becomes One Shop Or Many

Why Kisumu SACCO AI listing errors split or collapse cooperatives, and how entity wording can explain the structure.

Routes, sources & entities

When Kisumu Is Mistaken For Kisii

Kisumu Kisii business confusion in AI answers, and the shore, county, route and neighborhood wording that keeps western Kenya entities separate.

Trade, proof & time

When AI Treats Jua Kali Work As Absent

Kisumu jua kali business online visibility depends on verifiable signals that prove real work without pretending informal operators are formal chains.

Lake names & local roles

Why Dunga Beach Operators Vanish From AI

Dunga Beach operator AI answers often miss tourism businesses when Hippo Point, visitor type, activity and schedule limits are not linked.