Yes. Use a specialties array column with a list mapping so one URL covers all lines, or duplicate the row per line so each line gets its own URL through the urlPattern. Row duplication wins when each line deserves its own meta description and intro copy for long-tail queries.

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

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 configuration changes.

Yes. Add an image URL column and configure a meta mapping for og:image targeting it. For dynamic cards combining species, 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 later, restore the row and the URL comes back live with full history intact.

Update the specialty column and clear the cache. The slug stays the same so accumulated backlinks survive the pivot, and the page reflects the new focus on the next render. For major pivots also update the title, meta description, and intro copy fields.

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

Yes. SleekRank supports seven source types: Google Sheets, CSV file, CSV URL, JSON file, JSON URL, Notion, and REST API. Use one source per page group, or run parallel groups against different sources for member shops, regional partners, and editor picks.