Your actual SKUs, mapped
You asked what /items/0-100 teaches us. Crawled all 101 URLs. 20 real items, 81 fallback shells. The catalog is more legible than zucity.org's main nav makes it look. Three real bugs to fix and one strong wedge already shipping.
Three real bugs to fix this week
Items /items/12 (Osaka Art Residency), /13, /14, /15 (Elelfa Moshiri House Studio/Music/Workshop), and /16 (Traditional Family Estate) all emit "price":"50000000","priceCurrency":"USD" in their JSON-LD. The actual description on /items/12 says "$80 per night, sleeps two." This looks like a unit-mismatch entry (maybe yen as USD, or an extra three zeros).
What this breaks: Google Rich Results and AI overviews ingest the JSON-LD price. ChatGPT and Perplexity have been seen to quote schema-stated prices verbatim. Right now a query like "Osaka Art Residency price" could return "$50,000,000" from your own structured data.
/items/8 (ZuCity Artist & Builder Residency): 17 words. /items/16 (Traditional Family Estate): 29 words. /items/18 (Long Sleeve): zero JSON-LD description. /items/19 (Concierge Agent Credits): zero JSON-LD description.
The bedroom items 5-11 average 200 words of evocative copy. These 4 break that pattern and will under-convert. /items/19 is the most painful because it's the AI offering, which should be your most explained product. /items/8 is the headline residency program with the thinnest description.
Items 5, 6, 7, 9, 10, 11, 16 (the ZuCity bedrooms and the Traditional Family Estate room) have no price in JSON-LD. The descriptions don't reliably surface a per-night rate either. Visitors land, read 200 words of beautiful copy, then have to guess what booking means and how much it costs.
This is a buying-friction issue, not a tech issue. Some founders deliberately gate price to drive inquiry. If that's the model, say so on the page: "Book by inquiry" plus a clear CTA. If not, surface a starting price.
The pricing ladder, shipped today
Real prices stated on the items, not the $50M bug rows. Sorted by tier so you can see the structure your buyers see.
Two gaps worth thinking about. Between $500 and $25,000 there's nothing. A $2,500-5,000 mid-tier annual membership or a $1,500 themed-week pass would fill that. And below $80, the only items are merch and agent credits. The $80 daily access is a strong floor for the real product.
What this teaches us
Real centers of gravity
Five named locations across the catalog: Komoro (Yoramachi property, Nagano - 4 items reference it), Osaka (Abeno ward, Kita-Kagaya art district - 1 item), Elelfa Moshiri House (3 rooms, location not stated but appears separate from Komoro), Traditional Family Estate (Kiba's childhood home renovated - 1 item, 6 bedrooms total per description), Karuizawa (mentioned in copy but no dedicated item). Komoro is the densest mention. The other properties are stub-stocked.
Voice and positioning
The copy is unusually strong. Specific, anti-marketing, lyrical. "Door code and a day. What happens inside is what happens for residents - which is the point." That voice is a real asset. The 4 thin items break the pattern visibly; visitors who land on them after reading one of the long ones will feel the drop.
The AI wedge is already shipping
/items/19 Concierge Agent Credits at $8 is the AI offering. It's live but undescribed. ops-modules.html in this orb proposes 7 AI ops for Zucity surfaces. You're already validating the wedge by selling it. Adding a 200-word description that explains what the credits buy, who it's for, and how it interacts with residents would 5-10x the conversion on this SKU alone.
Real-product distribution vs the wedge map
The 20 items roughly map to 4 of the 15 wedges from wedge-offers.html: coliving accommodation (10 of 20), curated event passes (3 of 20), artist/builder residencies (2 of 20), and one AI wedge (1 of 20). Merch is the 2 other items. That's a leaner catalog than the wedge map suggests, which is fine. The wedge map is options, not a SKU plan.
Catalog completeness
20 SKUs at 6 categories is enough density to feel like a real product line and small enough to maintain. The bedrooms (5-11) being identical-template-different-room is the right pattern; the gap is in pricing surfaced and category-page navigation. Right now the catalog only exists as /items/0-19. There's no /membership, /residencies, /komoro category landing. That's the next site-structure move.
Full catalog (extracted from JSON-LD)
| ID | Name | Category | Price | Words | Verdict |
|---|---|---|---|---|---|
| 0 | ZuCity Japan VIP Membership | Membership | $25,000 | 205 | Strong |
| 1 | ZuCity Japan Daily Access | Membership | $80 | 225 | Strong |
| 2 | Japan Global Membership | Membership | $200 | 215 | Strong |
| 3 | The Grocery Store | Event venue | $500 | 151 | Strong |
| 4 | Nakamandem | Event venue | $500 | 226 | Strong |
| 5 | ZuCity Master Bedroom | Accommodation | - | 256 | No price |
| 6 | ZuCity Office Bedroom (Mountain) | Accommodation | - | 201 | No price |
| 7 | ZuCity Tatami Bedroom | Accommodation | - | 174 | No price |
| 8 | Artist & Builder Residency | Residency | - | 17 | Thin copy |
| 9 | ZuCity Balcony Bedroom #1 | Accommodation | - | 172 | No price |
| 10 | ZuCity Balcony Bedroom #2 | Accommodation | - | 169 | No price |
| 11 | ZuCity Secluded Backyard Flat | Accommodation | - | 185 | No price |
| 12 | Osaka Art Residency | Residency | $80/night* | 230 | Schema $50M bug |
| 13 | Elelfa Moshiri House Studio | Accommodation | -* | 190 | Schema $50M bug |
| 14 | Elelfa Moshiri House Music Room | Accommodation | -* | 187 | Schema $50M bug |
| 15 | Elelfa Moshiri House Workshop | Accommodation | -* | 188 | Schema $50M bug |
| 16 | Traditional Family Estate Room #1 | Accommodation | -* | 29 | Thin + $50M bug |
| 17 | Deluxe Sticker Pack | Merchandise | $10 | 22 | Acceptable |
| 18 | ZuCity Japan Long Sleeve | Merchandise | $80 | 0 | No JSON-LD desc |
| 19 | Concierge Agent Credits | AI | $8 | 0 | No desc - hero AI wedge |
What I would do this week, in order
- Fix the $50M schema price on items 12-16 (10 minutes). Bug #1 above. This is leaking into AI overviews already.
- Write 200 words for /items/19 Concierge Agent Credits (30 minutes). Your AI wedge has no public explanation. The voice you used on /items/12 Osaka is the target tone.
- Write 200 words each for /items/8 (Artist & Builder Residency) and /items/16 (Traditional Family Estate) (90 minutes total). Both are flagship-eligible products with throw-away copy.
- Add prices or clear "Book by inquiry" labels on the 7 accommodations without price (30 minutes). Decision first, then admin edits.
- Add a 150-word description to /items/18 Long Sleeve (10 minutes). Small but ships.
- Stand up a /komoro category landing page linking the 4 Komoro items (1-2 hours). Removes the "items/0-19 with no index" friction.
About 4 hours of focused work. All of this also feeds the AI-visibility audit in the orb. Every fix above improves what ChatGPT, Perplexity, Claude, and Google AI Mode see when they crawl your site for the queries in ai-visibility.html.
Connection map
- cro.html for the 4 funnel teardowns (membership, event reg, accommodation, Lu.ma). The bugs found here are 4 new entries for that page when you revisit.
- wedge-offers.html for the 15-wedge map. /items/19 confirms the AI wedge is already live.
- ai-visibility.html for which AI platforms cite Zucity for which queries. Schema fixes here improve those numbers.
- ops-modules.html for the 7 proposed AI ops that could plug into the Concierge Agent product.
- site-crawl.html for the 145-page on-page crawl. /items/0-19 are 20 of those pages.
Crawl source: 101 URLs at https://zucity.org/en/items/0 through /items/100, Next.js JSON-LD extraction. 20 real items, 81 fallback shells. Inventory JSON archived at agency-deliverables/kiba-zucity/lead-audit/items/items_inventory.json. Run date: 2026-05-30.