Butler County, Ohio approves a data-center moratorium, and it isn't in the curated feed yet

What changed: Butler County, Ohio — the Cincinnati–Dayton-corridor county of roughly 390,000 people — has approved a moratorium on data centers. The signal surfaced in SitePath's raw news layer this week and has not yet been promoted into the curated SitePath's data-center dataset feed, where the national moratorium count still reads 22.

Why it matters: Butler County sits inside the PJM / AEP-Ohio load zone — the same grid region driving the data-center buildout pressure that SitePath tracks most closely in Virginia and the broader Mid-Atlantic. When a county at the edge of a major data-center growth corridor pauses new development, it is a leading indicator of the same local-control backlash that has already produced moratoria across Ohio townships and that Virginia's HB 711/SB 347 preemption (effective July 1, 2026) was written to contain on the solar/BESS side. A data-center pause is a distinct lever: data centers are the demand that makes solar and storage siting urgent, so a moratorium on the load can reshape the economics of nearby generation siting just as much as a generation ban does.

What SitePath data actually says

The trigger is a single row in SitePath's news index (record 713f790ab919605e):

• County / FIPS: Butler County, OH / 39017
• Headline: "Butler County Approves Data Center Moratorium"
• Publisher: WYSO (NPR member station, southwest Ohio)
• Article date: 2026-06-18
• Source URL: https://www.wyso.org/2026-06-17/butler-county-approves-data-center-moratorium
• Sentiment: −0.312 (negative) · Confidence: 0.70
• Ingested: 2026-06-21 · Last refreshed: 2026-06-25

That is the full extent of what is verifiable from SitePath data today. The headline asserts the moratorium was approved (not merely proposed), in Butler County, Ohio, around mid-June 2026.

What the curated layer says (and the gap)

The curated SitePath's data-center dataset feed — the one that powers SitePath's data-center pages — was regenerated twice on 2026-06-25 (syncs #167 and #168). Across that regeneration its totals.moratoriumActive stayed at 22, townshipMoratorium at 10, and banEnacted at 1. In other words, the Butler County moratorium has not been triaged into the curated dataset. It exists only in the raw news index at 0.70 confidence.

That gap is the operational point of this alert: a real, on-the-record county action is sitting in the staging layer and needs a human to verify it and promote it to a sourced curated record before it shows up — or fails to show up — on the Butler County page.

For context, the same sync expanded the curated data-center inventory sharply (totalProjects 8,123 → 8,414; announced 34 → 247; underConstruction 70 → 108), so the pipeline is actively ingesting data-center growth — which makes the missing restriction record stand out more, not less.

Recommended next steps

• Hand to evidence-researcher / meeting-researcher to capture the resolution + minutes deep links and confirm scope/duration/vote.
• On verification, mint a curated SitePath's data-center dataset moratorium record (URS-conformant: source_url, source_type, confidence_score, last_verified_at) and increment moratoriumActive.
• Cross-link to the Ohio township-moratorium cluster already tracked (10 township moratoria) and to the Guernsey County, OH data-center proposal (woub.org, 2026-06-23) flagged in the same daily scan — Ohio's local data-center friction is building and may warrant a standalone state explainer.