If the API returns JSON, yes. The rest_api source pulls on a schedule, caches the response for the duration you configure, and re-renders pages on cache miss. ParkMobile, FlashParking, and most modern operators expose a roster endpoint that maps cleanly to row columns including rate and availability.

Use a short cache duration on the data source. SleekRank does not poll continuously, but a five-minute cache keeps availability counts close to live without hammering the upstream API. For truly live counts, embed the operator's availability widget on the base template and let SleekRank render the lot context around it.

Yes. Filter the sheet by rate type into two page groups, each with a different URL pattern, sharing the same underlying data. /parking/monthly/{slug}/ and /parking/hourly/{slug}/ each render the matching subset, and a single lot can appear in both if it offers both rate types.

Map the photo URL column into an img tag via the selector mapping. SleekRank handles the swap; image hosting stays wherever it already lives, whether the operator's CDN, Cloudinary, or the WordPress media library. For multiple photos, use a list mapping against a comma-separated photo URL column.

Every generated URL goes into the WordPress sitemap automatically. The base template page is automatically noindexed so only per-lot pages compete in search. New lots enter the sitemap on the next cache refresh, and Google picks them up on its next crawl of the sitemap.

Yes. The reservation widget keeps living on the base template page, and SleekRank just swaps in the lot-specific text and metadata around it. ParkWhiz, SpotHero, and operator-direct widgets all keep their original integration; the page becomes a per-lot landing surface that links into the widget.

Yes. Add an events sheet keyed by lot slug with date and event name columns, and a selector mapping injects an event banner on the matching nights. /parking/{slug}/ shows arena-night pricing on game days and standard rates the rest of the week, all from one source.

Add a heightLimit column with a value in feet or meters and inject it into a clearance-height line through a tag mapping. For a more useful experience, add a vehicleType filter column and create page groups for /parking/oversized/ that exclude lots below a certain clearance.