Yes. A pattern like /spanish-restaurants/{region}/{city}/ produces /spanish-restaurants/basque/san-francisco/ 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 format as a column with values for pintxos, tapas, raciones, mariscos, sit_down. A page group filtered on format produces dedicated hubs for each service style. Pintxos and tapas in particular drive separate search intents that benefit from separate URLs.

Edit the sheet and flush the SleekRank cache. The pages re-render with the new values on the next request. Seasonal tapas rotations are the most common drift source for Spanish directories; one-cell edits in a signature_dishes column propagate everywhere.

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. Store wine_program and sherry_list as JSON arrays. List mappings render each bottle category or sherry style on the venue page. Pair with a /spanish-restaurants/sherry-bar/{city}/ hub to rank for sherry-led queries that a generic wine-bar hub misses.

Yes. SleekRank uses your existing WordPress page as the template, so any theme or page builder works. The mapping engine targets rendered HTML, not builder-specific markup, which makes it builder-agnostic.

Store hours as a structured field per weekday with optional siesta windows. A selector mapping renders the schedule and a conditional mapping shows a "closed today" badge when the current day matches a closed entry. Diners see accurate availability without per-page edits.

Add a cuisine_authenticity column (traditional, modern, fusion). The editorial line between an old-school Catalan tavern and a modern Spanish-Asian fusion spot stays in the data. Region hubs filter on traditional or modern to preserve cuisine integrity.