Yes. Run additional page groups with /tax-liens/state/{slug}/, /tax-liens/county/{slug}/, and /tax-liens/sale/{date}/ as URL patterns, sourced from the same data. List mappings filter rows by state, county, or sale_date. One dataset, four URL patterns, no duplicate maintenance.

Use a status column with values like upcoming, sold, redeemed, expired, withdrawn. Route closed certificates to /tax-liens/past/{slug}/ via a second page group while removing them from the live one. The history persists as comparable data, the live listings stay clean.

Yes. Map only the public-safe fields into the rendered page. Premium fields like full owner contact, lender data, or interior photos stay in the paywalled tool. The data layer decides what is public; SleekRank only renders what the source supplies.

Map sale_date, sale type, face amount, interest rate, and county location into JSON-LD Event, Offer, and PriceSpecification nodes via a meta mapping. Validate one certificate with Google's Rich Results Test, then trust the template across the dataset.

Use a sale_type column with values like lien or deed and render the appropriate explainer block via a selector mapping. Florida lien sales, Texas deed sales, and Maryland hybrid sales all live in the same corpus with the right framing per page.

Yes. SleekRank reads from the same API or sheet that feeds your portal. The portal keeps the bidding, tracking, and document workflows; SleekRank owns the public marketing and SEO surface.

Each state hub lists different counties, different statutory rates, and different sale calendars. Give each state hub a unique intro paragraph driven by the state row, and the corpus reads as a real research directory rather than a templated swap.

Yes. Build the alert signup once into the hub template and inject the state or county slug via a selector mapping into a hidden field. Signups route to the correct alert list in the email tool automatically.