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

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

Yes. Lazy-load HOA bylaws PDFs and budget documents on the base page. The HTML still ships with the HOA name, dues, and rules summary in real text, so the page indexes well before the documents mount.

Map fields to a JSON-LD RealEstateListing block via a meta mapping. Address, price, bedrooms, bathrooms, and floor area fill in the schema per row. Validate one page with Google's Rich Results Test, then trust the template across the corpus.

Yes. The status column drives a badge on the unit page via a selector mapping. When the MLS feed flips a unit to pending or sold, the page reflects the new state on the next cache refresh, usually within an hour.

Both. Point SleekRank at the MLS REST endpoint with the appropriate auth, at a nightly CSV export, or at a Google Sheet maintained by the brokerage admin. The same mappings apply regardless of where the rows originated.

Each unit page has a unique address, floor plan, price, HOA detail, and gallery, even within the same building. 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 /townhouses/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 studying recent neighborhood pricing before they bid.