Yes. Run a second page group with /tiny-homes/{type}/ as the URL pattern, sourced from the same sheet. A list mapping filters rows where buildType matches the slug and renders matching units. One sheet, multiple URL patterns, no duplicate maintenance.

Use a status column with values like available, in-build, and sold. Filter the data source to available rows for the live pattern and route sold rows to /tiny-homes/sold/{slug}/ via a second page group if you want them archived as social proof. SleekRank rebuilds both corpora on the next cache refresh.

Yes. Map a floorPlanUrl column into a lazy-loaded viewer on the base page. The HTML still ships with square footage, sleeping capacity, and bath count in real text, so the page indexes even before the viewer mounts.

Map fields to a JSON-LD Product block via a meta mapping. Square footage, build type, price, and builder 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 (square footage, build type, region, base price) into public HTML and gate the full options-loaded pricing behind a quote form. Google indexes the summary; qualified buyers receive the configured quote after submitting contact info.

Yes. Point SleekRank at a CSV export from the CRM or a REST endpoint that mirrors active inventory. The same mappings apply regardless of where the rows originated.

Each unit page has unique square footage, build type, foundation, sleeping capacity, bath count, lead time, and a short positioning blurb. That is far more substance than most marketplace listings. Avoid templated rewriting and let the data variation carry the page.

Yes. Route rows where status is sold to a /tiny-homes/sold/{slug}/ pattern via a second page group. The active corpus stays clean and the sold archive becomes a long-tail SEO asset and a social-proof gallery for new buyers researching the builder.