Add a status column with values like open, closed_for_season, permanently_closed. A selector mapping renders a banner per status. Closed-for-season pages stay indexable but show next-opening dates pulled from a season_start column, which is what searchers want when they hit the page out of season.

Yes. Store happy hour as a JSON column with day-of-week keys and time ranges. A list mapping renders the schedule on every rooftop page. Updating happy hour for one venue is a one-cell edit.

Yes. Each row carries a reservation_url column pointing to OpenTable, Resy, SevenRooms, Tock, or in-house. A selector mapping injects it into the CTA button. Reservations without a service simply use a tel: link from the phone column.

Yes. Add an editorial_score or rating column and sort the list mapping on the city hub by that column. The per-rooftop pages still target their specific names, while the city hub ranks for "best rooftop bars in [city]".

Add a hotel column and a hotel_url column. The rooftop page links to the hotel; a list mapping on the hotel's own page can render its rooftop bar. Both sides of the relationship come from one row.

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. A second page group on /rooftop-bars/{city}/{neighborhood}/ produces URLs like /rooftop-bars/new-york/midtown/. Use a neighborhood column on each row; the page lists every rooftop tagged to that neighborhood.

Store image URLs in a hero_image column per row, served from your CDN or media library. Pair SleekRank with SleekPixel for a per-rooftop OG image so social shares carry the venue name and floor number on a templated background.