The stage_type column is the primary distinguishing field. Values like private_rooms, open_stage, mixed define the category. Hubs on /karaoke/private-rooms/{city}/ and /karaoke/open-stage/{city}/ each rank for their own intent.

Store catalog_languages as a JSON array. A list mapping renders each language as a badge on the bar page, and per-language hubs pick up the bar because it is in the array. Multi-language bars (English plus Korean, say) appear in both hubs.

Yes. Both live as columns. Selector mappings render them as stats on the bar page. A second column for max_room_capacity helps group bookings find rooms big enough for the party.

Add a byob boolean and a corkage_fee column. Selector mappings render each as a badge so guests check before arriving. BYOB-friendly hubs can surface that subset for the queries that explicitly want it.

Yes, if you track it. A catalog_size column drives a stat like "40,000 songs in catalog". Some publications publish exact counts; others publish only languages and let the song count be discovered on arrival.

Add an open_stage_nights JSON array column with day-of-week values. A list mapping renders the schedule on the bar page. Bars with open stage only on specific nights get the right messaging instead of a misleading always-open badge.

Yes. SleekRank uses an existing WordPress page as the template, so Bricks, Elementor, Gutenberg, Oxygen, and classic themes all work. The directory inherits whatever the site already looks like.

Yes. Each row carries a reservation_url column pointing to Resy, Tock, SevenRooms, or in-house. A selector mapping injects it into the CTA. Walk-in only bars omit the URL and the CTA hides on those pages.