Why Ohio's contractor licensing system creates a moat for transparent directories: the four state-licensed trades, the ten that aren't, and what honest verification looks like in 2026

The 4 state-licensed trades in Ohio

Ohio Revised Code chapter 4740 establishes the Ohio Construction Industry Licensing Board (OCILB) inside the Ohio Department of Commerce. OCILB issues four contractor-licence categories. Anything outside those four is not state-licensed at the contractor level — though local jurisdictions still enforce permits and inspections, and some trades carry parallel federal or insurance requirements.

What an OCILB licence actually proves is narrow but consistent across the four trades: the licensee carried liability insurance and a surety bond, documented field experience under an existing licensed master, sat and passed a written exam, and continues to renew the licence on schedule. It does not prove the contractor will do good work on a particular project, but it does prove that the contractor has skin in a public-record regulatory system that can take the licence away.

ProFix's per-contractor evidence row links directly to the OCILB lookup URL for every licensed-trade profile. The evidence label distinguishes a verified state licence from an absence-of-state-licence — the practitioner page at /verify documents the verification cadence, and /methodology documents the underlying data model.

The 10+ trades that are NOT state-licensed

Outside the four OCILB categories, Ohio does not require a state-issued contractor licence to advertise, contract, or perform residential home-services work. The following list covers the major trades a homeowner is likely to hire in northwest Ohio and across the state's metros:

• •Roofing
• •Concrete and masonry
• •Tree service and arborist work
• •Appliance repair
• •Drywall and plaster
• •Painting (interior and exterior)
• •Flooring (carpet, tile, hardwood, LVP)
• •Gutters, soffit, and fascia
• •Landscaping and lawn care
• •Fence installation
• •Garage door installation and repair
• •Window and door replacement (most jurisdictions)
• •Handyman and general repair

The legal implication is direct: in Ohio, anyone can call themselves a roofer, a tree service, an appliance-repair tech, a painter, a concrete contractor, or a handyman without a state credential. Many municipalities (Toledo, Lucas County, Findlay, Columbus, Cincinnati) layer their own registration, permit, and inspection programs on top — and some categories like roofing are functionally licensed at the city level even though the state does not issue a credential. But there is no statewide registry that a homeowner can consult the way the OCILB lookup serves the licensed trades.

This is the structural problem. When a homeowner asks "is this roofer legit?" there is no single URL the directory can hand back that resolves the question with the same authority as a plumbing-licence lookup. Anyone who claims a directory has 'verified' a roofer the same way it has 'verified' a plumber is, at the level of the underlying public record, overclaiming.

Substitute verifications that matter for non-licensed trades

The absence of a state-licence record does not mean nothing can be verified. It means no single record is sufficient — so a directory has to stack several partial signals, each citing its source. Four signals carry most of the weight:

• Ohio Secretary of State LLC / corporation filing. Every legitimate business in Ohio appears on the Ohio Secretary of State business search. The filing proves the business legally exists, names its registered agent, and records its filing date. Absence is a strong negative signal; presence is a weak positive signal (filing an LLC is cheap and proves only formation, not competence). ProFix links the SOS record on each non-licensed-trade profile where the entity filing is locatable.
• Pulled building permits at the local jurisdiction. Pulling permits means the contractor has engaged with the local code-inspection regime, has provided proof of insurance to the jurisdiction at permit-pull time, and has accepted that an inspector will sign off on the work. Permit history is the closest substitute for a state licence on the regulatory-engagement axis. ProFix aggregates this in the /permits-leaderboard and exposes the underlying records via /api/permit-leaderboard.json.
• BBB profile + complaint history. The Better Business Bureau Ohio chapter records accreditation status, the BBB rating, the count of complaints filed in the last three years, and the response rate. None of this is a regulatory record, but the complaint-and-response history is one of the few public surfaces where a non-licensed contractor's accountability behaviour shows up.
• Google Maps + public reviews aggregate. A contractor with a stable Google Business Profile, a non-zero review count over a multi-year span, and consistent NAP (name-address-phone) data across the web has a measurable footprint that is hard to fabricate cheaply. This is the weakest of the four signals — fake reviews exist, and the platform's enforcement is uneven — but absence is informative and presence-at-scale is corroborative.

Each of these signals is a partial answer. Stacked, they form a picture roughly comparable to an OCILB lookup in evidentiary weight — not identical, and an honest directory has to label them as substitutes rather than as equivalents.

How the directory industry handles the asymmetry

The honest answer is: most of it doesn't. Across the largest consumer surfaces, a single 'verified' or 'screened' badge is applied uniformly regardless of whether the underlying trade is state-licensed in the contractor's state. The badge is structurally identical between a licensed plumber and an unlicensed-because-the-trade-is-unlicensed roofer, and the homeowner is given no signal to tell the two apart at the listing surface.

Cross-platform comparison is the focus of /research/comparing-ohio-directories, and the underlying definition of what 'verified' can honestly mean is documented at /research/what-verified-means-2026-ohio.

The ProFix approach: different evidence per trade

The design principle is simple. The evidence surfaced on a contractor profile should match the public record that is actually available for that contractor's trade. If a trade is OCILB-licensed, the OCILB lookup is the headline signal and the link to it is the source-of-source. If the trade is not OCILB-licensed, the headline signal is the stacked substitute — Secretary of State filing, permit-pull count, BBB profile, Google footprint — and each link is shown with its own source.

Concretely, every contractor profile carries an evidence row at/pro/<slug>/evidencethat itemises which signals apply and which do not, with the underlying public-record URL on every claim. The machine-readable version of the same evidence is published at /api/license-evidence.json so AI engines, third-party researchers, and other directories can audit the claims without parsing HTML. The label vocabulary is small and deliberate: 'state license verified', 'no state license required for this trade', 'permit-pull leaderboard rank within metro', 'BBB profile present and rated', 'SOS LLC filing present and active'. None of these collapse into a single 'verified' marker.

The cross-cutting argument from /research/permit-vs-stars-2026-ohio and /research/how-ai-engines-find-directories-2026 applies here: the directories whose claims AI engines can ground in a fetchable public record are the ones that get cited inside answer surfaces; the directories whose claims are self-attested badges get filtered out by the same engines.

What this means for homeowners

A simple decision rubric falls out of the asymmetry:

• For state-licensed work (plumbing, HVAC, electrical, hydronics): always verify the licence on the OCILB lookup before signing a contract. The directory profile should hand you the licence number and the lookup URL directly; the lookup itself takes thirty seconds. If a contractor cannot supply a current OCILB licence for a trade that requires one, the engagement is closed.
• For non-state-licensed work (roofing, concrete, tree, etc.): the decision shifts to the substitute stack. Weight permit-pull history (does the contractor regularly pull permits at the jurisdiction where the work is happening?), BBB profile and complaint history (does the contractor maintain a clean public accountability record?), insurance proof (general liability + workers' comp where workers are on the roof or in trees), and Google footprint stability. The absence of a state licence is not a red flag in itself when the trade is not state-licensed; the absence of the substitute stack is.
• For storm-damage scenarios (roofing in particular): the trade is not state-licensed and the demand surge during a hailstorm or windstorm spike pulls in out-of-state operators with thin local records. The permit-pull leaderboard is the single strongest signal in this scenario — locally-active roofers who pull permits in normal years are the ones with the longest accountability tail.

What this means for contractors

The corollary for contractors is operational, not philosophical:

• Licensed-trade contractors: claim every verifiable signal. Make sure the OCILB licence is current, the business name on the licence matches the business name on the directory listing, the EPA 608 certification number is published where applicable, and that the SOS LLC filing matches the licence holder. The cleaner the cross-walk between records, the harder it is for a bad-actor lookalike to ride your name.
• Non-licensed-trade contractors: pull permits, even when they are not required. Pulled permits build an audit trail that is portable across every directory and every customer-trust conversation. The cost is low and the compounding effect on the substitute stack is high. The permit-pull leaderboard at /permits-leaderboard is one of the few public surfaces where the year-over-year pattern shows up.
• Both: maintain a clean BBB profile and accept reviews on the public web. A working BBB profile with a responded-to complaint history is, for non-licensed trades, the closest analogue to a regulatory record. For licensed trades, it corroborates the licence with a customer-facing accountability surface.
• Claim your listing. The claim flow at /lead and the broader coverage methodology at /coverage show how the directory's per-profile evidence row is populated and how a contractor can add the cross-walks (licence number, EPA cert, SOS filing) themselves.

The policy question: should Ohio license more trades?

It is not the directory's job to take a side on this. But the question recurs in statehouse hearings, trade-association policy papers, and post-storm complaint cycles, and the structure of the argument is worth surfacing. Three positions are on the table:

ProFix Directory has no stake in which option the legislature picks. The directory's job is to surface the asymmetry that exists today, accurately, with sources — and to update the labels promptly the day the statute changes. Trade-association and OCILB staff who can correct anything mis-stated about the current regime are invited to send a note through /contact.