Electrician-readiness checks: make your license and rev...

I keep auditing the same business: a licensed electrical contractor with a decade of work behind them, dozens of five-star Google reviews, a state license, and registrations in three or four towns, whose website carries almost none of it. The reputation is real. It is just invisible to the two things that now decide who gets the call: the Google map pack and the AI answer engines.

So I added an electrician-readiness layer to the Mega Analyzer. It runs only when a page looks like a licensed electrical contractor (an Electrician schema type, an "electrical contractor" or "Master Electrician" signal, panel-upgrade / generator / EV-charger / rewiring services, or "licensed / free estimate / service area" copy). Here is what it checks, and why each one quietly costs an electrician calls.

The one thing most electricians get right, then ship half-built

Schema.org has a dedicated Electrician type. It is a subtype of LocalBusiness, and using it instead of a generic Organization (or no schema at all) sharpens how the map pack and "electrician near me" reconcile your business. A surprising number of electricians do reach for it. Then they ship it on the home page only, with the wrong context, and missing the fields that make it useful.

The checks:

The Electrician type itself. Present is a pass. A generic Organization (or nothing) is a finding, with the exact node to emit.
@context hygiene. The canonical context is https://schema.org. I see a lot of http://www.schema.org and http://schema.org. The non-canonical form is the kind of thing some parsers quietly reject, and when they do, your entire business node disappears from their view. One wrong string, whole entity gone.
The node on one page only. A LocalBusiness node referenced by @id on every page is how engines build a stable entity. If it lives on the home page and nowhere else, your service pages are anonymous.

Make the NAP machine-readable, not just visible

A phone number a human can see is not the same as a phone number a machine can use. The layer flags:

telephone on the node itself (in E.164 form like +1XXXXXXXXXX), not buried inside a contactPoint. Click-to-call and the map pack read the top-level field.
areaServed. If you serve five towns, say so in the schema. Otherwise the surrounding-city searches never match you.
geo coordinates, openingHoursSpecification (including by-appointment days), and priceRange.
sameAs. Link your Google Business Profile, Facebook, Yelp, BBB, HomeAdvisor, and Nextdoor profiles. An established electrician usually already has most of these. Listing them in sameAs is how engines confirm that the business on your site, the listing on Google, and the profile on HomeAdvisor are all one company.

The two open lanes almost nobody in the trade has taken

When I run the same extraction across a metro's worth of electrician sites, two findings come back nearly every time, and they are the two biggest opportunities.

Review schema. Across a typical local peer set, the number of competitors shipping machine-readable AggregateRating / Review is usually zero. Meanwhile the businesses themselves have plenty of reviews sitting on Google and HomeAdvisor. Surfacing your real, current rating as schema is the single biggest trust-and-click signal you can add, and you would likely be the first in your market to do it. The one rule: the number must be the genuine, current platform total. Under the FTC consumer-review rule (16 CFR Part 465) a machine-readable rating carries the same liability as a visible claim, so confirm the real count first and never seed or inflate it.

Your license number. Electrical work is a state-licensed trade. The license number is one of the strongest trust signals you can show, and many jurisdictions expect it on advertising anyway. Most electrician sites say "licensed" and stop there. If you hold the license, display the state number and your local registrations in the footer and on the About and Contact pages, and put it in the schema as an identifier or hasCredential. It is free credibility you already earned.

The rest of the checklist

Per-service Service schema. One Service node per thing you sell (panel upgrades, generator installation, EV-charger install, rewiring, commercial), each with provider pointing back at your business @id. This is how an AI answer maps "who does panel upgrades in my town" to you.
A Person node for the owner. For an owner-operated trade, the licensed Master Electrician is the brand. Name them, with jobTitle and a real photo.
BreadcrumbList on inner pages, which most competitors already ship.
FAQPage on a real FAQ page answering the questions people actually ask before they call: how much a panel upgrade costs, whether they need a permit, what size generator they need, whether you are licensed, whether you serve their area.
A Google Business Profile link, the single biggest lead source for the trade.
The EV-charger opportunity. EV-charger and Level 2 / Tesla Wall Connector installation is the fastest-growing residential electrical category and a high-intent search. If you do this work and your site never says so, that is a missed page. If you do not, it is worth a look.
A permit / code signal. Stating that you pull the permit and the work passes inspection and is built to the National Electrical Code (NEC) is a correctness and trust signal, and it matches what AI answers cite for licensed trades.
Plus the universal local-business basics: a real sitemap.xml referenced in robots.txt, a real 404 for unknown URLs (not a homepage served at every path), self-canonicals that match the served URL, Open Graph tags, and alt text on every image (WCAG 1.1.1).

Why this matters more every quarter

Search is moving from ten blue links to one answer. When someone asks an assistant for an electrician in their town, the engine assembles that answer from structured data, the map pack, and citation-consistent profiles. An electrician with twelve years of work and a wall of five-star reviews, whose site has none of it in a form a machine can read, simply does not make the answer. A newer competitor with a clean Electrician graph and a few reviews marked up correctly does.

None of these fixes cost much. They are JSON-LD, a few content additions, and a Google Business Profile you probably already have. The point of the readiness layer is to turn what you already earned in the real world into something search and AI can actually see.

If you are building or rebuilding a local-service site and want the whole pattern in one place, the playbook in The $97 Launch walks through the schema, the profiles, and the review habit end to end.

Run your own site through the Mega Analyzer, then generate the exact JSON-LD with the Schema Fix Bundle and validate it with the Schema Validator.

Fact-check notes and sources

Electrician schema type is a defined subtype of LocalBusiness in the schema.org vocabulary (https://schema.org/Electrician).
Canonical JSON-LD context is https://schema.org; Google's structured-data guidance and the schema.org docs use the HTTPS form (https://developers.google.com/search/docs/appearance/structured-data/local-business).
FTC consumer-review rule, 16 CFR Part 465, prohibits fake or materially misleading consumer reviews and testimonials; a machine-readable rating is an advertising claim (https://www.ftc.gov/legal-library/browse/rules/rule-consumer-reviews-testimonials).
Electrical licensing is state-regulated; states license electricians and electrical contractors through a state electrical board, and most electrical work requires a local permit and inspection under the adopted National Electrical Code (NFPA 70). Confirm your state and municipal rules.
WCAG 1.1.1 Non-text Content requires text alternatives for images (https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html).

Electrician websites are leaving their best asset invisible: the Mega Analyzer's electrician-readiness checks