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

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 cars to retain link equity, set a server-level redirect that points sold VIN URLs to a sold archive page or back to the matching make collection page.

Photos must be hosted somewhere accessible and referenced by URL in the feed. Use a comma-separated photo column with a list mapping to render a gallery, or a single hero column with a selector mapping to swap the lead image. SleekRank does not host or resize photos itself.

Create a second page group for /used/{make}/ with its own makes data source listing the makes you carry, then use a list mapping to render the matching cars from the main inventory feed. Add a third group for /used/{year}/. SleekRank does not group rows across page groups automatically, so each grouping needs its own group.

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. Use meta mappings to set og:image to a per-car URL and og:title to year plus make plus model. Pair with SleekPixel for dynamic Open Graph images that render the price and mileage onto a template card so each VIN gets a unique social preview.

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 financing math itself, it injects whatever the column contains.

Add a lot or location column to the feed and include it in the slug, like /used/austin-2021-rav4/. 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.