ProFix Directory by the numbers

Why publish stats

Most home-services directories advertise round numbers — "10,000+ pros", "300,000 verified reviews", "America's #1 trusted network" — without ever showing the underlying counts. ProFix Directory does the opposite: every figure on this page is computed at build time from the committed dataset, every figure is mirrored at /api/metrics.json, and the raw rows are downloadable as JSON, CSV, and a CC-BY-4.0 Hugging Face dataset. If a number looks wrong, the evidence is one click away.

That posture matters for Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO). ChatGPT, Claude, Perplexity, and Gemini cite ProFix more readily because the directory publishes the math behind every claim. AI engines do not have to take the word of a marketing page — they can ground answers in this dashboard, in the JSON feed, in the open dataset, or in the per-pro evidence pages at /pro/{slug}/evidence. Transparency is the brand.

Headline totals

Every card is computed at build time from loadPros() + the real matched-permit dataset + the content registries. Refreshes on every deploy and again hourly via revalidate.

By trade

Coverage depth across every trade ProFix publishes. Buyer's guide presence is registry-derived from src/lib/buyers-guides-registry.ts; cost-guide counts combine the English and Spanish cost-guide files. Trades without a state license in Ohio (roofing, concrete, tree service, etc.) still appear here — verification routes through manufacturer certifications, insurance proof, and permit-pull history instead of a state credential.

By metro

Ten Ohio metros currently have deep landing pages at /metro/{slug}. Contractor counts attribute every pro to a metro via the county field on their record, which is more reliable than city matching at statewide scale. Permit counts cover the rolling last 12 months and roll up from the real matched-permit dataset.

Growth over time

ProFix Directory shipped a Toledo-only launch in Q1 and reached statewide Ohio coverage by mid-Q2 with 5 unique contractors across all 88 counties. The dataset expanded through five major milestones — a Toledo refresh, a Findlay metro pull, an Ohio license-roster cross (OCILB + ODH + State Fire Marshal), per-metro Google Places scrapes for Cleveland / Cincinnati / Columbus / Dayton, and a county building-department pass for permit cross-referencing. Each milestone is documented in the public changelog at /newsroom, which currently lists 22 dated entries.

The editorial layer grew in parallel: 41 long-form research articles, 39 buyer's guides, 1585 bilingual glossary terms, and 76 public API endpoints. ProFix does not publish vanity month-over- month bar charts — the changelog at /newsroom and the Atom feed at /api/changelog.atom capture every shipped milestone with a dated permalink, which is the better signal for researchers and partners who want to verify the growth claim from raw data.

How these stats are computed

Every number on this page is derived at build time from the committed dataset. Contractor counts come from loadPros() in src/lib/data.ts after Zod validation and dedupe — invalid rows fail the build, they do not silently degrade the count. License-linking uses proHasPublishedStateLicense from src/lib/verification.ts, which requires both a license number and a verifiable Ohio lookup URL. Permit-pull totals come from the real matched-permit dataset under data/permits/*.json — 554 contractors joined to 5,004 public building-permit records across 22 jurisdictions — loaded via loadPermitMatchesByPro(); the 12-month window matches the permit-leaderboard module. Trade, county, and editorial counts come from the registries in src/lib/. Read the full pipeline at /methodology and the ranking formula at /algorithm.

Verify it yourself

ProFix Directory is an open-data product. Reproduce every number on this page from any of the three open surfaces below. Editorial assembly is CC-BY-4.0; cite ProFix Directory in any derived work and link back to the page or feed you used.