Yes. Use the CSV data source for a flat export or the REST data source for a live endpoint. Configure auth (bearer token, API key, or none) and a JSON path if the response wraps the listings array. The plugin caches the response per your cacheDuration and renders one page per UTV in the array.

Add an accessories JSON array column listing roof, doors, winch, plow, light bar, audio, and other installed packages. Render via a list mapping into a chip-row block on the base page. Buyers searching for a Ranger with HVAC plus a winch see exactly those chips highlighted rather than scrolling through a free-text blob.

When the row drops from the feed, the URL returns 404 on the next cache refresh and the sitemap entry is removed. To redirect to a similar in-stock UTV or to a sold archive, configure a wildcard 301 in WordPress before removing the row, which preserves any inbound links from owner Facebook groups and outfitter referrals.

Every page is substantively different: year, make, model, trim, hours, accessory package, photos, condition, price. Add a condition_notes column for genuine dealer commentary per UTV. Duplicate-content risk lives in templates that swap only a city; SleekRank swaps every field per row, which is what keeps duplicate detection at bay.

Yes. Build the calculator block once into the base page and every generated UTV inherits it automatically. Pass the per-row price into the calculator via a selector mapping on a hidden data-price attribute so the default monthly payment displays correctly without manual entry per UTV in the corpus.

Yes. Map fields to a JSON-LD selector in the page head: vehicleModelDate, brand, model, vehicleEngine, hours-as-mileageFromOdometer, and price. SleekRank performs the replacement on every URL, so each UTV carries its own structured data for Google rich card eligibility across the entire corpus.

Add a rebate_amount and rebate_end_date column to the feed. Render conditionally via a selector mapping that displays a Current Rebate badge only when rebate_end_date is in the future. Quarterly rebate cycles flow through the feed without manual page-by-page updates across thousands of UTVs.

Yes. Run secondary page groups for /utv-brands/{brand}/ and /utv-segments/{segment}/ (sport, work, recreation) sourced from brand and segment sheets. Use list mappings to filter the main feed. One inventory file produces individual UTV URLs plus brand and segment landing pages, all refreshed on the same cache cycle.