Yes. Run a second page group with /houseboats/{marina}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where marina matches the slug and renders active vessels for that lake. One sheet, two URL patterns, no duplicate maintenance.

Use a status column with values like active, sold, and withdrawn. Filter the data source to active rows for the live pattern and route sold rows to a /houseboats/sold/{slug}/ pattern if you want them archived as comps. SleekRank rebuilds both corpora on the next cache refresh.

Yes. Lazy-load YouTube or Vimeo embeds on the base page. The HTML still ships with the vessel name, length, and marina in real text, so the page indexes well before the video player mounts.

Map fields to a JSON-LD Product or Vehicle block via a meta mapping. Vessel name, year, length, and price fill in the schema per row. Validate one page with Google's Rich Results Test, then trust the template across the corpus.

Yes. Add a sale_pending boolean column and render a status badge via a selector mapping. When the broker updates the row, the page reflects the new status on the next cache refresh, well before the deal closes.

Yes. Point SleekRank at a REST endpoint exposed by the CRM, a CSV exported nightly, or a Google Sheet that an Apps Script populates from the CRM. The same mappings apply regardless of where the rows originated.

Each vessel page has a unique slug, year, length, sleeps, marina, condition notes, and photo gallery. Use per-row metaDescription, H1, and lead paragraph fields to ensure variety beyond the boilerplate. SleekRank surfaces every field per row, which is what keeps duplicate detection at bay.

Yes. Route rows where status is sold to a /houseboats/sold/{slug}/ pattern via a second page group. The active corpus stays clean and the comp archive becomes a long-tail SEO asset for buyers researching market value before they sign.