The Bulletin Trades

No. 036

Licensing and insurance: how to show trust on your site

A license number sitting quietly in a footer does less work than it could. Most states let anyone verify it in seconds, and that's the fact worth building the page around.

Most states let anyone verify a contractor's license in a few seconds, for free, with no account needed. That fact is more useful to put on your website than the license number alone, because it turns a claim into something a visitor can actually check.

Why this matters more than it looks like it should

Hiring an unlicensed or improperly insured contractor carries real consequences for a homeowner: a voided permit, invalidated insurance, and little legal recourse if the work goes wrong. Customers who know this (and increasingly, they do) are actively looking for proof, not just a claim.

What to actually show

How license verification actually works

Nearly every state maintains a public database where anyone can search by license number, business name, or contractor name to check whether a license is active, see its type and expiration, and in some states see any disciplinary history or bonding issues. There's typically no fee and no account required. A few examples of what these look like in practice: California's Contractors State License Board, Washington's Department of Labor & Industries verification tool, and Louisiana's State Licensing Board for Contractors all offer free public lookups. Trade-specific boards exist too; pest control, for instance, is regulated separately from general contracting in most states, with its own licensing board and lookup tool.

Turn the claim into an invitation

Instead of just stating a license number, invite the check directly: "License #12345, verifiable at [your state board's site]." That one sentence does two things a bare number doesn't. It signals you have nothing to hide, and it removes the effort of the visitor having to go find the lookup tool themselves if they do want to check.

Insurance is a separate claim from licensing

A license proves you've met a state's competency and legal requirements. Insurance proves that if something goes wrong on the job, there's coverage behind it rather than the homeowner absorbing the cost. State the type of coverage you carry (general liability at minimum, workers' compensation if you have employees) rather than a vague "fully insured," which tells a careful reader nothing about what's actually covered.

What to do if licensing requirements are genuinely confusing

Some states make this harder than others. A handful, New York and Illinois among them, leave contractor licensing to individual cities and counties rather than a single state board, so "licensed in New York" isn't a complete claim on its own; it matters which city issued it. If your state works this way, name the specific issuing authority rather than a vague state-level claim, since a careful customer checking your claim against the wrong database will come away more suspicious, not less.

Insurance certificates, on request

Some businesses go a step further than stating coverage and offer to provide a certificate of insurance on request, which a customer's own insurer sometimes asks for on larger jobs. You don't need to publish the certificate itself on the site, but mentioning that one's available if needed is one more small, concrete signal that the coverage is real rather than a line copied from a template.

Where this belongs on the site

Questions

What if my state doesn't require a license for my trade?

Say that plainly instead of implying a license that doesn't exist. Lead with your insurance coverage and any voluntary certifications instead.

Should I show my insurance policy number?

No, that's not necessary or advisable to publish. Stating the type and level of coverage is what matters to a visitor; the policy number is your carrier's business, not the public's.

Does showing my license number expose me to anything?

License numbers are public record by design, searchable by anyone regardless of whether you publish them yourself. There's no meaningful downside to stating it plainly on your own site.

Sources

Want a site that launches with answers already written?

Start a project