Most states publish a directory of county clerks and recorders through the secretary of state's office. The National Association of Counties (NACo) maintains a national county directory. Commercial title-data providers like First American, Stewart, and DataTree license normalized recorder data. SleekRank reads CSV, JSON, REST, or Sheets, so any combination of sources works once you've normalized them into a single table.

Update the fee columns and flush the cache. The pages reflect the new fees on the next cache cycle. For counties with complex fee schedules (per-document, per-page, indexing surcharges), store the full schedule as a JSON array in a single column and render through a list mapping. Fee changes typically follow fiscal-year boundaries, so most title operations refresh the full catalog quarterly and after any state-level legislative changes.

Yes. Add a portal URL column and map it to a primary CTA button on the page. For counties with multiple portals (one for searching, one for e-recording, one for plats), use separate columns and render all three. Vendor migrations are common in this space (counties move between Tyler, Tritech, ACS, in-house systems), so the URL column needs occasional auditing to catch dead links before users hit them.

Store fees as a structured array with document type, base fee, per-page surcharge, and any special handling charges. Render through a list mapping so each document type gets its own row in a fee table on the page. This matches how recorders publish their own fee schedules and matches how title examiners think about fees during closings.

Yes. Add columns for the e-recording vendor (Simplifile, CSC, ePN, EagleX), submission requirements, and processing timeframes. Render through tag and list mappings on the page. E-recording adoption varies widely (some states are 95% e-recorded, others under 30%), and the vendor relationship affects how title companies route submissions, so this data has real workflow value.

Per-county plat indexes are usually too large to embed directly, but linking to the county's online plat search from each recorder page is a high-value cross-link. Add a plat-search URL column and render it as a secondary CTA. For sites that license parcel data, separate page groups for popular counties can surface parcel-level information with per-parcel pages of their own.

Maintain a portal-availability column. For paper-only counties, surface the mailing address, courier address, accepted formats, and required attachments prominently. A selector mapping swaps the page layout to emphasize physical workflow over digital. Roughly 15 to 25% of US counties still operate paper-primary recording, mostly in rural states, so this pattern remains important.

Yes. Build separate page groups at /recorders/state/{slug}/ and /recorders/metro/{slug}/ from filtered views of the directory. State indexes capture broad inbound search; metro indexes serve title workflows where a deal spans multiple counties. Both patterns coexist on the same site, sourced from the same canonical directory with no data duplication.