Yes. Use a specialties array on the row with a list mapping for one URL covering all eras, or duplicate the row per era so the urlPattern emits a separate URL per era-shop combination. Row duplication is better when each era deserves its own title, meta description, and intro copy, which usually wins on long-tail era-plus-city queries.

Not directly. SleekRank reads JSON, CSV, Google Sheets, Notion, or a REST API on the configured cacheDuration and renders whatever is in the source. If you have a real-time inventory system that exposes a JSON feed, point a data source at it and set a short cache. There is no direct integration with specific antique inventory platforms.

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

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

Add a status column with values like permanent, pop-up, and closed. Filter on it in the base page template so pop-ups render with a closing-date block, and configure the urlPattern to keep the slug alive for SEO continuity even when a pop-up ends. Re-renaming the slug breaks accumulated links.

No. The bios live in your data source. SleekRank simply injects whatever copy you provide into the mapped slots. Dealer-supplied bios usually outperform AI-generated ones on collector trust, but if you do generate copy with an AI workflow, do that upstream in the sheet and let SleekRank render the result.

Yes. Add a neighborhood column and change urlPattern to /antique-shops/{neighborhood}/{slug}/, or run a parallel page group keyed on neighborhood. London Mayfair and London Spitalfields then become separately rankable URL paths without duplicating shop data, since both groups read the same sheet.

Update the specialty column on the row when the pivot happens, then clear the SleekRank cache. The URL slug stays the same so accumulated backlinks and sitemap inclusion survive the pivot, and the page content reflects the new focus on the next render. For larger pivots, also update the title and meta-description fields.