Yes. Run additional page groups with /storage-auctions/facility/{slug}/ and /storage-auctions/city/{slug}/ as URL patterns, sourced from the same sheet. List mappings filter rows by facility or city. One dataset, three URL patterns, no duplicate maintenance.

Use a status column with values like upcoming, live, sold, redeemed, canceled. Route closed units to /storage-auctions/past/{slug}/ via a second page group while removing them from the live one. The history persists for buyers tracking patterns, the live listings stay clean.

Yes. Store image URLs as a JSON array column with one to five photos per unit. A list mapping renders them into the gallery block on the base WordPress page, whether slider, grid, or lightbox.

Map sale_date, sale_time, facility address, and starting bid into a JSON-LD Event with a Place node via a meta mapping. Validate one unit with Google's Rich Results Test, then trust the template across the corpus.

Lien notice rules differ by state. Keep the notice text as a column or as a per-facility template fragment and render it through a selector mapping into the page. The data layer mirrors what the facility's legal counsel signs off on; SleekRank renders it consistently.

If the software exposes a CSV export or a REST endpoint for lien sales, SleekRank can pull from either. The management software keeps owning rent, billing, and lien workflows; SleekRank owns the public marketing and SEO.

Each city hub lists different facilities, different unit sizes, and different sale dates. Give each hub a unique intro paragraph driven by the city row, and the corpus reads as a real local directory rather than a templated swap.

Yes. Drop your existing bidding or registration widget onto the base WordPress page and inject the unit ID via a selector mapping into a hidden field. Registrations and bids route to the right unit in the auction backend automatically.