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

Not directly. SleekRank reads JSON, CSV, Google Sheets, Notion, or a REST API on the configured cacheDuration. If your booking platform exposes a JSON feed of trip slots, point a data source at it and set a short cache to keep the directory close to live availability.

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 certification, 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 operator reopens later, restore the row and the URL comes back live with full slug history intact.

Update the certifications column when the change happens and clear the cache. The slug stays the same so accumulated backlinks survive the change, and the page reflects the new program on the next render. For major switches also update title and meta description.

Each row drives unique hero, certification list, trip schedule, hours, and operator notes. 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. Add a specialty column and change urlPattern to /scuba-shops/{specialty}/{slug}/ or run a parallel page group keyed on specialty. Tech diving Bergen and liveaboard Cairns then become separately rankable URL paths without duplicating shop data.