MuckRock maintains an open registry of county and city public-records portals as part of their FOIA Machine project. Some state-press associations also publish per-county PRA contact directories. Most SleekRank setups start from the MuckRock JSON, normalize the state codes and county names, and augment with state-press data where coverage is thin.

Response windows are usually accurate because they are set by state statute (often 5 or 10 business days, sometimes 30 calendar days). Fees vary more and can change mid-year when a county updates its schedule. Most setups refresh the fee field quarterly and add a last-verified timestamp to each county page for transparency on currency.

There are multiple Washington Counties, multiple Madison Counties, and so on. Always normalize the slug as county-name plus state code, like washington-county-or for Oregon and washington-county-ny for New York. SleekRank treats the combined string as the unique key, which keeps the URL space collision-free across all 3,143 US counties.

Louisiana uses parishes instead of counties, Alaska uses boroughs, and Virginia has independent cities that function as county equivalents. Add them all to the dataset with a county_type field marking the local term. The slug pattern stays the same and the page template can render the appropriate label per row using the county_type value.

Some portals (especially MuniCode and GovQA hosted ones) expose iframe-compatible forms, but most counties prefer that the request be filed through their official URL for audit logging. Default to a prominent outbound link with the contact email and a copy-paste request template. Embedding adds compliance risk without much SEO upside in practice.

MuckRock runs the FOIA Machine and tracks individual requests. NextRequest is a SaaS portal that some counties use as their official submission flow. Both are valuable but neither renders a stable per-county landing page with comparable data. SleekRank fills that hub-page layer, then links out to MuckRock or the official portal for the actual request flow.

Run them as a separate page group. State agencies have their own PRA contact, often a centralized office. Generate /public-records/state/{slug}/ as a second corpus keyed by state code, then cross-link from each county page to its state agency page so the navigation works as an indexable PRA-portal directory across both levels.

SleekRank stores each resolved row in wp_sleek_rank_items at roughly 5-10 KB per county. Three thousand rows is a 30 MB MySQL footprint, trivial on any production database. Most teams pair the corpus with cached HTML at the edge so the page render is fast even when the underlying dataset has just refreshed.