Yes. Both publish CSV exports per dealer. Point SleekRank at the file path or a scheduled REST endpoint, set the cache duration to match the feed cadence, and SleekRank reconciles rows on each refresh. New units create pages, sold units expire URLs.

The row leaves the feed on the next refresh, SleekRank removes that slug from its item table, and the URL returns a 410 Gone status. The sitemap rebuilds without it, so Google deindexes the page on its next crawl rather than holding stale results.

Use the stock number or VIN as part of the slug. The instructions recommend a pattern like brand-model-stock-{number} so the slug stays unique across years and locations. The CSV needs a stable identifier column for the slug to be deterministic.

Yes. The base page in WordPress carries the financing calculator and trade-in form as normal blocks. If a row has a special promotion field, you can map it to a selector that swaps the default copy out, so a JD financing offer shows on Deere rows only.

Yes if the feed carries the required Product fields. Map slug, name, brand, condition, and price into a meta mapping that emits JSON-LD. The Google Search Console rich results report flags any rows missing required properties so you can patch the feed.

The pages exist within one cache refresh, so 30 minutes to 24 hours depending on the configured duration. Indexing is a Google decision, but the sitemap ping fires on each new URL and most dealer yards see new pages crawled within 48 hours.

Yes. The base WordPress page is one template. Each dealer gets a separate page group config with its own data source and URL prefix like /dealer-a/tractor-implement-listings/{slug}/. Layout updates ship to both dealers at once.

Most DMS platforms expose at minimum an FTP drop of nightly inventory. SleekRank reads CSV from a path or URL. If the export is dirty, a small WordPress filter on the page group can clean column names and types before SleekRank stores the row.