Yes. Provide a file path for the CSV data source or a REST endpoint plus an optional auth method (bearer token, API key header, or none). Set a JSON path to the listings array if the response wraps the data. The plugin caches the response according to your configured cacheDuration and renders one page per row.

Map an array field of image URLs to a list mapping that renders into your slider, masonry, or lightbox block on the base page. If the source carries a comma-separated string instead, split it in the mapping. The base page owns the gallery design; the data only supplies the URLs and alt text.

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 sold archive or to a similar in-stock bike, configure a wildcard 301 in WordPress before deleting the row, which preserves any inbound links from social cross-posts.

Every page is genuinely different - make, model, year, hours, photos, schema, price, condition notes. Add a per-row description field and feed it into the lead paragraph mapping so buyers and crawlers see substantive copy beyond the spec table. The duplicate-content risk lives in templates that swap only a city; SleekRank swaps every field per row.

Yes. Drop the calculator block onto the base page once and every generated listing 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.

Yes. Map fields to a JSON-LD selector in the page head: vehicleModelDate, brand, model, vehicleEngine, and price. SleekRank performs the replacement on every generated URL, so each bike carries its own structured data. Validate once with the Rich Results Test, then trust the template across the corpus.

Promo pricing flows from the feed - update the CSV, hit the cache refresh, and every affected page picks up the new price on the next cycle. To surface the drop visually, add a previous_price column and conditionally render a strikethrough via a selector mapping. Buyers return to pages they bookmarked when they see the visible reduction.

Yes. Run a second page group with /mx-bikes/{brand}/ as the URL pattern, sourced from a brands sheet. Use a list mapping to filter the main feed by brand and render the matching bikes on each archive. One inventory file, two URL patterns - dealer landing pages and individual bike pages - both fresh on the same cache cycle.