POPULAR POET
Two-domain sales system: vitrine + own box office, admin, check-in, PL/UA/RU i18n — plus Gemini bot for auto-publishing (~4 posts/week). AI organic → sales in 2 weeks.
2
connected sites (vitrine + ticketing)
4
events/week (automated publishing)
3
content languages (PL/UA/RU)
2 wks
AI organic → ticket sales post-launch
THEATER
Warsaw · PL / UA / RU
▶ popularpoet.pl
▶ populartickets.pl
Popular Poet is a Ukrainian/Russian-speaking theatre studio for emigrants in Poland. Before launch, their only internet presence was Instagram. I built popularpoet.pl as a course showcase and populartickets.pl as a proprietary box office — avoiding commission-heavy ticketing platforms that don't generate traffic for this niche audience. Stack: Next.js, Supabase, Vercel, Resend, trilingual PL/UA/RU, admin panel and on-site check-in. Google Business Profile setup included. Weekly ops meant ~4 events to publish — manual CMS entry was slow, so I added a Gemini-powered bot (free tier): drop photos + text, get structured events, ready pages, and Bing/indexing pings. Within 2 weeks of launch, organic traffic from AI search converted to ticket sales.
Before / After
Was
- Instagram-only presence — no owned website or search footprint
- Commission ticketing platforms that take a cut and bring no niche emigrant traffic
- No course vitrine, no owned sales funnel, no on-site ticket verification
- ~4 events/week entered manually — slow, repetitive CMS work every week
Became
- Two sites: popularpoet.pl (course vitrine) + populartickets.pl (own box office)
- Supabase backend, admin panel, Resend notifications and check-in at the door
- Gemini event bot: photo + text dump → structured events → live pages → Bing ping
- Google Business Profile, trilingual PL/UA/RU, AI organic traffic → ticket sales in 2 weeks
● REC — SYSTEM FLOW
Digital infrastructure flow
- 01Instagram-only presence / course demand from emigrant audience
- 02popularpoet.pl — course vitrine and enrollment funnel
- 03~4 events/week — manual entry was slow; need automation for weekly show publishing
- 04Photo + text dump → Gemini (free tier) parses structured events
- 05Ready event pages published → Bing IndexNow / search-engine ping
- 06Ticket need → populartickets.pl (own box office, no commission)
- 07Supabase + Resend + check-in + admin panel
- 08Google / AI visibility → organic traffic → ticket sales
automation-first · PL / UA / EN
● Project screenshots
● Related module
Gemini bot for automated event publishing — a module inside the same infrastructure.
What was wrong
Popular Poet is a theatre studio for Ukrainian/Russian-speaking emigrants in Poland. Their entire internet presence was Instagram — no owned site, no search indexing, no sales infrastructure. Commission ticketing platforms charge fees and don't drive traffic to a niche emigrant theatre audience. They needed a course vitrine, their own ticket office, and visibility in Google and AI search — not another social-only funnel. On top of that, ~4 events per week had to be created manually — tedious data entry that ate hours every week.
What I built
Built popularpoet.pl as a trilingual course showcase (PL/UA/RU) and populartickets.pl as a proprietary box office on Next.js + Supabase + Vercel. Implemented admin panel for events and courses, Resend for transactional email, on-site check-in for ticket verification, and structured data for local + multilingual SEO. Set up Google Business Profile. To kill weekly publishing friction, built a Gemini-powered event bot on the free tier: drop photos and raw text, the bot parses structured events, outputs ready pages, and pings Bing (and similar indexing) about new URLs. The system replaces commission platforms with owned infrastructure that can be found, cited, and kept fresh by AI search — without manual event entry.
Outcome
Two live domains — popularpoet.pl and populartickets.pl — with full operational stack: admin, check-in, Resend, trilingual content and GBP. Event publishing automated for ~4 shows/week: photo/text → Gemini → pages → Bing ping — hours saved on weekly ops. Real outcome: within 2 weeks of launch, organic traffic from AI search converted to ticket sales. Not a brochure site — a digital infrastructure layer for emigrant theatre with automation-first weekly publishing.
Next improvements
- Screenshot: Instagram-only before vs popularpoet.pl course vitrine
- Screenshot: populartickets.pl checkout and ticket confirmation (Resend email)
- Screenshot: admin panel — events, courses, ticket inventory
- Screenshot: Gemini event bot — photo + text input → parsed event preview
- Screenshot: published event page + Bing/indexing ping confirmation
- Screenshot: on-site check-in / ticket verification flow
- Screenshot: trilingual PL / UA / RU pages and language routing
- Screenshot: Google Business Profile and local search presence
- Screenshot: AI search / GSC evidence of organic traffic post-launch
- Add detailed GSC and conversion metrics (placeholder until export)
- Run and publish Lighthouse scores for both domains
● CASE STUDY DATA
connected sites (vitrine + ticketing)
operationsevents/week (automated publishing)
operationscontent languages (PL/UA/RU)
operationsAI organic → ticket sales post-launch
analyticsbox office (no commission)
operationson-site ticket check-in
operationsLighthouse performance
LighthouseМоя роль / внутрянка
- Architected two-site digital infrastructure: popularpoet.pl (courses) + populartickets.pl (ticketing).
- Built Next.js + Supabase + Vercel stack with admin panel and on-site check-in.
- Designed Gemini event parsing bot for ~4 weekly shows — photo + text → structured events → pages.
- Implemented trilingual PL/UA/RU content and language routing for emigrant audiences.
- Integrated Resend for transactional email and ticket delivery.
- Wired Bing IndexNow / search-engine ping after automated event publishing.
- Set up Google Business Profile and structured data for local + AI search visibility.
Операционный цикл
- Course vitrine with enrollment funnel — improv, acting and PLAYBACK programs.
- Own box office on populartickets.pl — no commission to third-party ticketing platforms.
- ~4 events/week published via Gemini bot instead of manual CMS entry — saves hours weekly.
- Admin panel: events, courses, capacity limits and ticket inventory.
- On-site check-in system for door verification at performances.
- Trilingual ops for PL / UA / RU emigrant community in Poland.
Стек
Интеграции
- Supabase (database, auth, realtime ticket data)
- Resend (transactional email, ticket confirmations)
- Gemini API (free tier) — photo + text → structured event parsing
- Event parsing bot → CMS publish pipeline
- Bing IndexNow / search-engine ping on new event pages
- Vercel (deployment and edge delivery)
- Google Business Profile (local discovery)
- Cross-domain architecture popularpoet.pl / populartickets.pl
Поисковая выдача
- LocalBusiness + Course + Event schema for rich results and entity recognition.
- Multilingual PL/UA/RU content with hreflang for emigrant audience queries.
- FAQ schema answering high-intent theatre and course questions.
- Google Business Profile wired into local search footprint.
- Automated event pages + Bing ping for faster indexing of weekly show listings.
AI-выдача
- Course / Event / LocalBusiness schema — machine-readable offering for AI answers.
- Gemini (free tier) parses unstructured photo + text into structured events for the site.
- Structured multilingual content indexed for AI search citations.
- Real result: AI organic traffic converted to ticket sales within 2 weeks of launch.
- Owned infrastructure replaces commission platforms that AI can't recommend as primary source.
Структурированные данные
Внедрённые типы Schema.org с правом на rich results.