Yes. SleekRank reads JSON, CSV, Google Sheets, Notion, or a REST API and renders whatever is in the source on each cache cycle. For daily menu refreshes, set cacheDuration to a few hours and update the sheet column when the kitchen rotates dishes. The next render reflects the new menu across every URL touching the venue.

Store dietary flags like gluten-free, soy-free, raw, and oil-free as a comma-separated column or a JSON array. A list mapping renders them as visible badges on every venue page. The same column can drive filtered hub pages so searchers find raw-only or gluten-free vegan venues without digging through the directory.

Yes. Either map an image URL column per row, or use SleekPixel to render dynamic cards combining cuisine, venue name, and city. Configure a meta mapping for og:image pointing at whichever URL field your workflow produces and Open Graph cards will differ per venue.

Append rows for the new area to the source sheet. SleekRank picks them up on the next cache cycle and adds the URLs to the sitemap. Run wp rewrite flush once after the first new-city batch so WordPress recognises the slugs. Subsequent additions in that city need no further flush.

Set a status column to closed and either filter the page group to exclude closed venues or render a closed banner. Filtering removes the slug from the sitemap and returns 404, while a banner preserves the URL for archival or redirect purposes. Choose based on whether you want the slug to keep accruing links.

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

Yes. Add a seasonalMenu column with current availability and map it to a selector or list. Off-season items drop from the page automatically when you clear that column at the end of the season. Many guides keep a Q1, Q2, Q3, Q4 column structure so the rotation is editable in advance.

Map a lastReviewedDate column to a meta tag or schema property so each venue page surfaces a clear updated-on date. Pair with WordPress's native modified timestamp by editing the base page when bulk updates happen. Both signals help Google understand the directory is actively maintained.