Most counties export a polling-site file from their election management system every cycle. SleekRank reads the CSV directly, and editors typically maintain a parallel sheet for fields the EMS does not carry, like parking and language support.

Each row carries an array of precinct numbers assigned to that site. A list mapping renders the array as a section of the page with one row per precinct, and each item links to the corresponding /precincts/{slug}/ page if that page group is also active.

Yes. Each row carries two hour fields, earlyVotingHours and electionDayHours. The template renders both, and a small banner switches based on the current date so the active window is highlighted to anyone visiting during the cycle.

Standard fields cover entrance ramps, parking, restrooms, voting-aid devices, language support, and curbside voting. The template renders an Accessibility section per page so a voter or advocate can see at a glance what the venue provides.

If a venue stops serving as a polling site for one cycle but returns later, keep the URL published with a notice for the inactive cycle. If a venue permanently retires, 301 redirect to the replacement site or to a county-level polling-place index.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page so only venue URLs get crawled. New sites added before each cycle appear in the sitemap on the next cache refresh.

Some counties contract with a vendor that runs many sites under similar names (Vote Center 12, Vote Center 13). Use the venue address as the dominant signal in the slug and the H1, with the vendor's internal ID as a secondary line on the page.

Yes. The address field geocodes once during the cache refresh, and the template embeds a Google Maps or Leaflet view centered on the venue with the parking lot marked. Surrounding amenities like transit stops can be layered in from a separate source if useful.