If your DMS exposes a JSON, CSV, or REST endpoint, yes. SleekRank supports json_url, csv_url, REST API, and Google Sheets out of the box. For closed systems, schedule a nightly CSV export and point SleekRank at the file. The plugin reads from configured sources only and never writes back to the DMS.

Remove the row from the feed. On the next cache cycle the page returns a 404 and drops out of the sitemap automatically. If you want sold units to retain link equity, set a server-level redirect that points removed slugs to a sold archive or back to the matching brand collection page.

Yes. Add a comma-separated attachments column and use the list mapping to render a feature list. Loader, mower deck, backhoe, snow blower, all rendered consistently. For implements with their own SKUs and pricing, run a separate page group for /implements/{slug}/ that reads its own data source.

Create a second page group for /tractors/{brand}/ with its own brands data source listing the brands you carry, then use a list mapping to render the matching tractors from the main inventory feed. Add a third group for /tractors/{class}/ keyed on compact, utility, and row-crop. Each grouping needs its own page group.

Add an estimated monthly column to the feed if your DMS calculates it, or link out to your finance partner via an applyUrl column injected into a button with a selector mapping. SleekRank does not run finance math itself, it injects whatever the column contains.

Data is fetched on a schedule and cached. Page renders use the cached row, so request time is similar to a normal WordPress page render. For large inventories, lengthen the cache duration so refreshes only run on a schedule rather than per request.

Yes. Map an hours column with a tag mapping for the headline hours figure, and a warrantyStatus column with another tag mapping for an in-warranty or out-of-warranty badge. Both render directly from the feed without manual editing on the post.

Add a location column to the feed and include it in the slug like /tractors/austin-2020-jd-5075e/. Run separate page groups per lot if you want fully isolated URL trees, or keep one group and use the column in the template to render lot-specific contact info and address.