Yes. Run a second page group with /private-islands/{region}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where region matches the slug and renders active islands for that region. One sheet, multiple URL patterns, no duplicate maintenance.

Use a status column with values like active, under-contract, and sold. Filter the data source to active rows for the live pattern and route sold rows to /private-islands/sold/{slug}/ via a second page group if you want them archived. SleekRank rebuilds both corpora on the next cache refresh.

Yes. Map a videoUrl column into a lazy-loaded embed on the base page. The HTML still ships with acres, region, and ownership type in real text, so the page indexes even before the video mounts.

Map fields to a JSON-LD Place or Product block via a meta mapping. Acres, region, country, and asking price fill in the schema per row. Validate one page with Google's Rich Results Test, then trust the template across the corpus.

Yes. Render summary fields (acres, region, ownership type, access mode) into public HTML and gate the full survey, title report, and infrastructure packet behind an NDA flow. Google indexes the summary; qualified buyers receive the packet after signing.

Yes. Run parallel page groups for each language with localized URL prefixes and source sheets per language. /private-islands/ for English, /isole-private/ for Italian, /islas-privadas/ for Spanish. The mappings are the same; only the slug and content language differ.

Each island page has unique acres, region, country, ownership type, access mode, structures, and a short positioning blurb. That is far more substance than most aggregator listings. Avoid templated rewriting and let the data variation carry the page.

Yes. Route rows where status is sold to a /private-islands/sold/{slug}/ pattern via a second page group. The active corpus stays clean and the sold archive becomes a long-tail SEO asset for buyers researching comparable transactions over multi-year cycles.