Yes. Use a genres array column with a list mapping so one URL covers all genres, or duplicate the row per genre so each gets its own URL through urlPattern. Row duplication wins when each genre deserves its own intro and meta description for genre-plus-city queries.

Not directly. SleekRank reads JSON, CSV, Google Sheets, Notion, or a REST API on the configured cacheDuration. If your inventory system exposes a JSON feed, point a data source at it and set a short cache to keep the directory close to live stock changes.

Yes. SleekRank renders through one base WordPress page, so whichever builder or theme styles that page is what every generated shop URL inherits. Bricks, Elementor, Gutenberg, and custom themes all work without further configuration.

Yes. Add an image URL column and configure a meta mapping for og:image targeting it. For dynamic cards combining genre, city, and shop name, pair SleekRank with SleekPixel and reference the generated image URL through the same meta mapping path.

Remove the row from the source and clear the SleekRank cache. The URL returns a 404 on the next render and drops from the sitemap automatically. If the shop reopens, restore the row and the URL comes back live with the slug history intact.

Update the specialty or genres column and clear the cache. The slug stays the same so accumulated backlinks and sitemap inclusion survive the pivot, and the page reflects the new focus on the next render. For larger pivots also update title and meta description.

Each row drives unique hero, genre list, hours, and shop notes. Pages share only the chrome that any consistent theme shares. Google treats the URLs as distinct as long as the per-row content is genuinely different, which it is when the data is real.

Yes. Add a neighborhood column and change urlPattern to /record-shops/{neighborhood}/{slug}/ or run a parallel page group keyed on neighborhood. Tokyo Shinjuku and Tokyo Shimokitazawa then become separately rankable URL paths without duplicating shop data.