Yes. A pattern like /french-restaurants/{style}/{city}/ produces /french-restaurants/bistro/boston/ from the data. Each combination becomes a unique URL with its own H1 and the relevant venues listed via list mapping, which is what ranks for combination queries.

Store michelin_status as a column (none, bib_gourmand, one_star, two_star, three_star). When the new Michelin list drops, edit the cells for affected venues and flush the SleekRank cache. The badge, the schema, and any Michelin-tier hub all update from one source.

Edit the sheet and flush the SleekRank cache. The pages re-render with the new values on the next request. Most directories run a 24-hour cache so daily updates propagate within the next business day; manual cache flush via WP-CLI pushes immediately.

Each URL is a real WordPress page with full HTML and is included in the sitemap. The base template page is auto-noindexed so it never competes with the generated children. New venues typically index within a few crawls of the sitemap update.

Yes. Add a dining_style column with values for bistro, brasserie, bistronomy, fine_dining, wine_bar, creperie. A page group filtered on dining_style produces dedicated hubs for each format and ranks for style-specific city queries without manual builds.

Use the region column for Provencal, Lyonnaise, Alsatian, Bretonne, Parisian, and so on. The roster sheet stays canonical and the editorial line between regional traditions is preserved in the data. Region hubs surface every venue per regional cuisine.

Store sommelier_credentials and natural_wine as columns. A list mapping renders the sommelier's certifications on the venue page, and a natural_wine boolean drives a dedicated hub for natural-wine bistros and bars per city.

Yes. Add columns for reservation_url and tasting_menu_url. Selector mappings wire each URL to its own button on the template page. Tasting-menu bookings often use a different platform than standard reservations, and per-column mapping preserves that split.