Yes, either via CSV export download and re-upload on a weekly schedule, or via the OpenChargeMap REST API as a data source. The API returns JSON which SleekRank reads on the configured cacheDuration. Per-station fields like connector type, max power, and operator map cleanly to columns in the page group, and re-fetching weekly keeps the directory current.

Networks upgrade stations from 50 kW to 150 kW or 350 kW periodically, and the API or CSV export reflects the change. SleekRank picks it up on the next cache refresh. Set cacheDuration to a week for stable feeds, or to a day during active buildout periods when networks announce upgrades. Manual cache flushes work for urgent updates.

Each station has unique connector mix, max power, network, hours, address, and price-per-kWh, which is enough variation for Google to treat each page as distinct. The lead paragraph can pull station-specific notes from a column rather than templated copy. SleekRank surfaces every field per row, so variation comes from the data itself.

Remove the row from the feed and the URL returns 404 on the next cache refresh, also dropping from the sitemap automatically. If a station is temporarily down for upgrades, add a status column and render a maintenance banner via selector mapping rather than removing the row, preserving accumulated backlinks for when service resumes.

SleekRank renders into a base WordPress page, inheriting the theme exactly as a normal page would. Gutenberg, Bricks, Elementor, Oxygen, and classic themes all work because SleekRank performs HTML substitution at render time rather than replacing the theme layer. The base page is a regular WordPress page.

If the charging network exposes an availability API, pull it into the feed and render an availability pill via tag mapping with short cacheDuration. ChargePoint, EVgo, and Electrify America each expose some availability data through their APIs. Without API access, SleekRank serves cached data; real-time availability requires the network endpoint to be in the feed pipeline.

Yes. Store lat/lng in a column and on a /charging/map/ landing page, pass the filtered array to a Leaflet or Mapbox block rendering all stations as pins colored by network or power level. Per-city pages can render a city-scoped map by filtering the same data on the city column.

Yes. Run /charging/{slug}/ for per-station URLs, /charging/{city}/ for per-city collections, and /charging/network/{network}/ for per-network directories like /charging/network/electrify-america/. All three groups read the same feed filtered at the data source level by the appropriate column, so one source covers multiple URL patterns.