A first-quarter GEO plan for a licensed electrical contractor

Which jobs should an electrical contractor try to be named for?

The ones that pay, and that your crews can take more of next month. Being named for a job can send you calls for it. A call for work you cannot staff helps nobody: the homeowner waits for a slot you do not have, or hears no, and the next answer they read carries someone else's name.

So start from your own books rather than from what people search for. Last year's invoices show what each kind of job earned per crew day, and your schedule shows who does it and how far ahead they are booked. The worksheet puts both on one line per job. The checks are specific to the work; the verdicts are yours to write.

Keep two or three jobs for the quarter, taken from rows where both checks come out well. A job with margin and nobody free to do more of it waits for a hire. A job the crew could take on but that earns little waits for a price change. The other rows do not disappear; they wait for the second quarter, when you will have this quarter's readings to go on. The general version of this planning for any small business is building a GEO strategy in 30 days; this page is the electrical contractor's cut of it.

If nobody answers at 2 a.m., leave the night questions alone

The night call is where the crew test bites hardest. A shop with nobody on call should not try to be named for "emergency electrician open now", because each answer that names it sends a homeowner with the lights out to a phone nobody will pick up. That costs the caller an hour, and it can cost the shop a review written the next morning.

What that shop should publish instead is the plain fact: the hours it answers, and that it does not take calls at night. That is an accurate answer, and an accurate answer about when you are closed does you no harm. The homeowner calls someone who can come tonight, and may call you next week about the panel the outage made them worry about.

A shop that does take night calls has the opposite job, and the page it needs is set out in the article on the emergency page. Either way, the choice is made from the on-call rota, not from the questions people ask.

The license and permit sentences, written once

Write the license sentence once, in the words your licensing board uses, and put that exact sentence on every page that needs it: "[Business name] holds [the license, as the board writes it], number [number], issued by [the board], [state or province]." Do not translate it into another place's terms or shorten it into a title. The board's own wording, with the number and the issuing authority beside it, is the version a reader anywhere can check.

The permit sentence is your practice, not the rule: which jobs you pull a permit for, who books the inspection, and what the homeowner does on the day. "[We pull the permit for (jobs), book the inspection and (what the homeowner does).]" What the rules require is a question for the building department or the licensing board where the job is. The page states only what your shop does.

Put the license sentence on the about page and in the footer. Put the permit sentence on each service page where your shop pulls one: the panel upgrade, EV charger, generator or rewire page, as your own practice sets it. Do not reword either sentence from page to page. Two wordings of one license, a title on one page and a different one on another, are two facts for an answer to choose between.

The same sentence has a home in the markup. On schema.org, the Electrician type takes hasCredential, whose value can be an EducationalOccupationalCredential, schema.org's type for an occupational credential, with credentialCategory for the kind of credential, recognizedBy for the board, validIn for the state or province and identifier for the number, each filled in as the board writes it. We checked those properties on schema.org. They repeat what the page says; they do not replace the sentence in the text.

The publishing order, week by week

The order follows the worksheet: first the facts every page depends on, then one page per chosen job, the best-paying job you can staff first, with a reading on each side of each page. One page at a time is slower than publishing everything in a week. It is also the only way to say afterwards which page did what.

1. Week 1: take the first reading of the panel lines for your chosen jobs, and the two lines that name you. The bracketed panel is in AI visibility for electricians. Run the crawler access check on your robots.txt, and note each service page's figures in Search Console's generative AI performance report.
2. Week 2: the license and permit sentences go on, and the business name, number and hours are made identical everywhere; the overview for electricians lists what has to agree. Nothing else changes this week.
3. Week 3: read the first job's lines again, then publish its page, written from the questions your dispatcher hears about that job. For an EV charger, the page is laid out in the article on the EV charger page.
4. Week 6: read the first job's lines (its after-reading) and the second job's (its before-reading), then publish the second page.
5. Week 9: the same step for the third job: read, then publish.
6. Week 12: read the third job's lines for its after-reading.
7. Week 13: read the whole panel exactly as in week 1, and fill in the ledger.

The weeks in between are for writing the next page, not for publishing it. If a page is ready early, it waits. A page published a week ahead of its slot takes the next job's before-reading with it, and the quarter loses the one comparison that would have shown what that page did.

What a before-and-after reading can show

Each page gets two readings of its own job's lines: one taken before it goes live and one taken three weeks after. Same lines, same assistants and runs, recorded the same way each time. Our method does this with one assistant, Claude, asking each line once per reading. Three weeks is a pacing choice, not a promise about when an assistant will next read the page; it gives each reading one page to answer for. The lines for jobs you did not touch in that window show what moved without you.

Expect the first readings to be thin. In the probe that went with our audit of 9,483 small business websites (40 trades, 90 metros, late August to early September 2026), 14.9% of the 9,240 businesses probed were named on one buyer question for their own trade and metro. That was one question each, on Claude, on one day, across all 40 trades. It is a direction, and it does not say where any one electrician starts.

For Google's AI features there is a second reading to keep beside the panel. Since August 31, 2026, Search Console has had a generative AI performance report that counts impressions of links to your site in AI Overviews and AI Mode, by page, country, date and device. It has no query dimension, so it cannot say which question showed the page. It can say whether the new page's link appeared at all, starting from the week it went live. A property with too few impressions may see nothing in it yet, which is a reading too.

If an after-reading comes back flat, find out whether the page can be read before you rewrite it: run the crawler access check again, and load the page with scripts turned off to see whether its text is in the HTML. Keep the panel lines exactly as they were. A panel that is reworded after a flat month has stopped measuring the page and started measuring the wording.

A ledger with one row per page

Keep the quarter in a ledger, one row per page, filled in as the weeks pass. It is short, and it is the record the second quarter is planned from.

Read the ledger against itself, not against other shops. A page whose after-reading beat its before-reading, on the assistants your buyers use, earned its slot. One that did not goes back to the worksheet with a question attached (the job, the page or the reading) rather than into a rewrite on a hunch. The second quarter starts from the worksheet rows you left for later.