← Back to projects
Sales · Ticketing · Automation· 2025 — now● LIVE SIGNAL· CH-03

POPULAR POET

Sellable proof: two-domain sales system with own box office and Gemini publishing bot — AI organic converted to ticket sales in 2 weeks.

popularpoet.pl ↗populartickets.pl ↗

2

connected sites (vitrine + ticketing)

4

events/week (automated publishing)

3

content languages (PL/UA/RU)

2 wks

AI organic → ticket sales post-launch

CH-03 — popularpoet.pl● ON AIR
https://popularpoet.pl
OPEN ↗
Screenshot of popularpoet.pl
popularpoet.pl
● LIVE
Screenshot of popularpoet.pl

popularpoet.pl

loading…

Built for a theatre studio selling to emigrants: course vitrine + proprietary ticketing, admin, check-in, PL/UA/RU i18n. Gemini bot automates ~4 events/week (photo+text → pages → Bing ping). Result: AI search traffic → ticket sales within 2 weeks of launch.

● If your situation is similar

CH-03 / ACTION

Send the current site, idea or blocker. I will tell you whether DIY, audit/rescue or a full build makes more sense.

Order build →Read free guides →

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

  1. 01Instagram-only presence / course demand from emigrant audience
  2. 02popularpoet.pl — course vitrine and enrollment funnel
  3. 03~4 events/week — manual entry was slow; need automation for weekly show publishing
  4. 04Photo + text dump → Gemini (free tier) parses structured events
  5. 05Ready event pages published → Bing IndexNow / search-engine ping
  6. 06Ticket need → populartickets.pl (own box office, no commission)
  7. 07Supabase + Resend + check-in + admin panel
  8. 08Google / AI visibility → organic traffic → ticket sales

automation-first · PL / UA / EN

● Project screenshots

POPULAR POET screenshot 1

● Related module

Gemini bot for automated event publishing — a module inside the same infrastructure.

Open Event Bot →

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. For populartickets.pl, GSC already shows an early search base over 3 months: 25 clicks, 223 impressions, 11.2% CTR and 4.3 average position. PageSpeed/Lighthouse from 23 June 2026: popularpoet.pl — mobile 94, desktop 100; populartickets.pl — mobile 90, desktop 98; Accessibility, Best Practices and SEO are 100; Agent view is 3/3. 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
  • Prepare a safe GSC screenshot for populartickets.pl: 25 clicks, 223 impressions, 11.2% CTR and 4.3 average position.
  • Strengthen pages for queries with impressions but no clicks yet: “мероприятия в варшаве”, “warszawa wydarzenia dzisiaj”, “выходные в польше”.
  • Add conversion analytics: which search visits become ticket purchases.
  • Prepare safe PageSpeed proof screenshots for both domains

● Metrics

Source tags show where each number comes from. Yellow badge = estimated, not verified.

2

connected sites (vitrine + ticketing)

operations
4

events/week (automated publishing)

operations
3

content languages (PL/UA/RU)

operations
2 wks

AI organic → ticket sales post-launch

analytics
own

box office (no commission)

operations
live

on-site ticket check-in

operations
25

populartickets 3-month clicks

Google Search Console
223

populartickets 3-month impressions

Google Search Console
11.2%

populartickets CTR

Google Search Console
4.3

populartickets average position

Google Search Console
94

popularpoet mobile performance

Lighthouse
100

popularpoet desktop performance

Lighthouse
90

populartickets mobile performance

Lighthouse
98

populartickets desktop performance

Lighthouse
100

Accessibility / Best Practices / SEO

Lighthouse
3/3

agent view checks

Lighthouse

My role / internals

  • 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.

Operations loop

  • 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.

Stack

Next.jsTypeScriptSupabaseVercelResendi18n (PL / UA / RU)Admin panelCheck-in systemGemini API (free tier)Event parsing botBing IndexNow / pingTailwind CSS

Integrations

  • 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

Search visibility

  • 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.
  • 3-month GSC for populartickets.pl: 25 clicks, 223 impressions, 11.2% CTR and 4.3 average position — low volume, but strong early quality.
  • PageSpeed/Lighthouse proof: popularpoet.pl mobile 94 / desktop 100, populartickets.pl mobile 90 / desktop 98, SEO 100 on both domains.

AI visibility

  • 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.

Structured data

Schema.org types implemented with rich-result eligibility.

LocalBusinessCourseEventOfferFAQPageBreadcrumbList

● NEXT CHANNEL

alesyatakun.by
● LIVE
Screenshot of alesyatakun.by

alesyatakun.by

loading…

LIVEalesyatakun.by

ALESYA TAKUN

Psychologist site with 3-D Secure payments and flexible booking flow.

PaymentsMedicalBrandNext.js
View case →
Order build →Read free guides →