OCPI is a standardized REST API for charger location data, designed for roaming between networks. SleekRank reads REST endpoints with auth headers, so an OCPI feed is supported as a source. Configure the locations endpoint, set the bearer token, and SleekRank caches the response per the configured duration. Most major networks expose OCPI for partners; if you're reading your own network's roster, OCPI is usually the cleanest path.

Store connectors as an array per row with type, count, and power and use a list mapping to render them as repeated cards on each station page. Stations often mix connector types, like a site with two CCS stalls at 350 kW and four CCS+NACS stalls at 250 kW. List mappings handle nested connector groups cleanly. For interactive availability widgets, embed a separate live-status component that calls the OCPI session endpoint.

SleekRank renders cached source data, not real-time stall status. For live availability, embed a separate widget on the base page that calls the OCPI sessions endpoint or the network's status API. The widget loads on the rendered SleekRank page and updates independently. Most drivers want both: cached station metadata for SEO landing plus a live availability peek before they head to the station.

Pricing varies by network, time of day, membership tier, and connector type. Store the pricing structure as a JSON column or array per row and use a list mapping or table component to render it on each station page. For dynamic pricing that changes hourly, embed a live widget instead. Static pricing for membership tiers works well as cached content; surge or peak pricing needs the live layer.

Some destination chargers host multiple networks at one location, like a hotel with both Tesla Destination chargers and a J1772 wall unit, or a service plaza with Electrify America and EVgo at adjacent islands. Model these as one row with a networks array or as separate rows per network sharing a parent venue ID. The first approach gives one URL covering all networks; the second gives network-specific URLs. Pick based on how drivers search.

Add a status column with values like operational, partial, and offline, then use selector mappings to swap copy when stations are degraded. For long-running outages like Electrify America's well-known reliability issues, the page can stay live with a clear status notice rather than disappearing. Inbound links and SEO equity preserve while drivers get accurate expectations before they route to the station.

Yes. OpenChargeMap has roughly five hundred thousand stations globally and SleekRank's caching layer handles catalogs of that size without issue. The bottleneck on global EV catalogs is usually crawl budget and editorial focus, so the practical move is to filter to operational fast chargers in target geographies and noindex slow Level 1 home-style chargers that don't draw search traffic.

Yes. Use additional page groups at /ev-networks/{slug}/ to list every station in a network, and at /ev-routes/{slug}/ to list chargers along major corridors like I-5 or the German autobahn. Both source from the same charger dataset filtered appropriately. Per-route pages capture high-intent road-trip search demand that per-station pages alone can't cover.