Yes. REST API is one of the supported source types alongside JSON, CSV, Google Sheets, and Notion. Configure the endpoint, set the auth header (bearer token, basic auth, or API key in query string), and SleekRank caches the response per the configured duration. Most enterprise dealer systems expose a JSON endpoint of the dealer roster — that's the input.

Place the JSON-LD template on the base page with placeholder fields and use mappings to inject row data (name, address, phone, hours, geo coordinates, openingHoursSpecification) into the schema fields. SleekRank treats schema as just another set of selector targets, so per-dealer LocalBusiness markup is automatic across the whole network without per-page editing.

SleekRank doesn't generate maps. Inject coordinates from the row into a static-map URL (Google Static Maps, Mapbox Static, OpenStreetMap) for crawlable image-based maps, plus an interactive map iframe (Google Maps embed, Leaflet) for user interaction via selector mappings. Most sites use both — static for SEO, interactive for usability.

Set a cacheDuration on the data source — 3600 for hourly, 86400 for daily, 604800 for weekly. The feed re-pulls automatically at that interval, or you can flush the SleekRank items cache manually for ad-hoc refreshes (new dealer onboarding, urgent hours change). On prod, the WP-CLI command is wp db query "DELETE FROM wp_NNN_sleek_rank_items".

Add a status column (active, closed, temporarily-closed) and use a meta mapping to set robots=noindex when the value indicates closed. Alternatively, filter closed dealers out of the source query so they never become URLs at all. Either approach keeps the sitemap clean. For temporarily-closed dealers, noindex preserves the URL for direct visitors with a closure notice but removes it from search.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page so only dealer URLs get crawled. New dealers added to the feed appear in the sitemap on the next cache refresh — important when a major manufacturer onboards a new regional dealer and wants the page indexed before launch.

Yes. Add columns or array fields for certifications (master-tech, EV-certified, factory-trained), specialties (RV-only, marine-only), and badges, then use list mappings to render them as chips on each dealer page. Manufacturers often need to surface these for warranty work; per-dealer pages let you target queries like "EV-certified Honda dealer Portland".

Either store brands as an array column on the dealer row and render them via a list mapping, or split into separate page groups per brand if each brand has its own URL structure (/honda/dealers/{slug}/ vs /yamaha/dealers/{slug}/). The array approach keeps multi-brand dealers on one page; the per-brand page-group approach gives each brand its own SEO surface for the same location.