About CountyPulse

What This Is

CountyPulse is a free, independent reference site. Every U.S. county gets a profile page assembled from federal public-domain datasets — Census, BLS, BEA, CDC, HUD, FEMA, NOAA, EPA, SSA, IRS, and about a dozen others. Every displayed number links back to the agency that produced it, with the data year labeled.

Why It Exists

Federal data about U.S. counties is abundant, high-quality, and free — but it lives across dozens of portals, uses inconsistent geographies, lags by different amounts, and is rarely presented in a way a non-specialist can read. CountyPulse is an attempt to gather the most useful pieces into one place, county by county, without editorializing and without inventing anything that isn't in the source data.

Editorial Stance

• Accuracy over coverage. A missing value is better than a wrong one. If a metric can't be published with confidence for a given county, it's omitted.
• Every number is cited. Source agency, data year, and a link to the upstream dataset appear next to every figure.
• No runtime AI. Page contents are built from the merged dataset at compile time. The site does not call any model at render time or fabricate values.
• Published caveats. Where an upstream figure is accurate but needs context (HMDA denial rates in low-volume counties, FDIC deposits in bank-HQ counties, NOAA readings from a single station), the caveat is shown inline and linked to known issues.

Who Runs It

CountyPulse is built and maintained by CB Daniels as an independent, non-commercial project. There are no investors, no ads, no trackers, no newsletters, and no paid placements. Questions, corrections, and feedback are welcome at [email protected].

Not a Government Resource

CountyPulse is not affiliated with, endorsed by, or operated by any federal, state, or local government agency. The site aggregates publicly available federal data but is not an official government source. For authoritative answers, consult the source agency linked on each figure.

How It's Made

A data pipeline fetches each source, normalizes every record to a 5-digit county FIPS code, reconciles overlapping fields, and writes one JSON file per county. The site is a static build — one HTML page per county, generated from those JSON files. See methodology for the full pipeline and a complete list of data sources.