Website Content for Contractors: A Decision Tree for Turning Every Finished Job Into the Next Lead

Your crew already produces more website content for contractors than any copywriter could. Every slab leak traced, every panel swapped, every hail-beaten roof torn off and re-decked is a finished, dated, location-specific story. The trouble is that it lives in a technician's camera roll and dies there. This article doesn't ask you to start a blog. It gives you a repeatable way to decide, job by job, what that work should turn into on your website, so you stop either posting nothing or posting everything.

The device here is a decision tree. Every completed job goes through the same two gates and lands in one of four places. Once the office knows the gates, the tree runs without you, and that's the point.

Which completed jobs should become website content for contractors?

Not all of them. That surprises owners who've been told "post more." A site with 300 near-identical "AC tune-up in Round Rock" pages isn't richer than a site with 30 strong project pages. It's thinner, and Google's systems are built to notice. The jobs worth publishing do at least one of three things:

• Prove a service you want more of. If you're pushing heat-pump conversions or whole-home repipes, every one you finish is evidence.
• Prove a place you want more work in. Your first three jobs in Leander matter more for Leander searches than your fortieth in Cedar Park.
• Prove you can handle the hard version. The attic water heater with no drain pan, the 1960s Federal Pacific panel, the low-slope roof the last company refused. Hard jobs are what homeowners search when they're scared, and those searchers call.

A routine job that does none of those three still has value as raw material. It just doesn't get its own page.

Curious what a site like this costs you in missed leads? See real builds for businesses like yours.

Gate 1: Can this job go on your website at all?

Run this gate first, because a yes at Gate 2 means nothing if the job fails here. Answer four questions in order. Any "no" sends the job to the archive (keep the photos, publish nothing).

1. Do you have permission? Add one line to your work order or invoice: the customer agrees you may photograph the work and publish images without their name or address. Most homeowners sign without blinking. Commercial and property-management jobs often need the client's written OK. If you'd be uncomfortable showing them the page, the answer is no.
2. Is the location safe to show? Publish the neighborhood or ZIP, never the street address. Crop out house numbers, plates, mail, family photos on the wall, and alarm keypads. A finished-garage photo that shows the gun safe and the keypad is a gift to the wrong person.
3. Would the photos survive a stranger's scrutiny? A tarp left on the lawn, an open junction box with no cover, a ladder footed on a cooler: if an inspector or a competitor would screenshot it, don't publish it.
4. Are there at least two usable photos? One blurry after-shot isn't a project. You need a before or problem shot and a clean after, minimum.

One compliance note for Texas trades. The Texas Department of Licensing and Regulation requires licensed A/C and electrical contractors to show their license number in advertising, and a project page is advertising. Put the license number in the page template once, so every project page carries it automatically and nobody has to remember.

Gate 2: What does this job prove that your website doesn't already show?

This is the gate that keeps the site from bloating. Before the office builds anything, they check the job against what's already published, using three branches:

• New service or new hard problem? If the site has no page showing this type of work, or no example of this complication, it gets a full project page.
• New city or neighborhood, familiar service? If you have project pages for this service but none in this town, it gets a full project page focused on the local details: soil, housing age, HOA rules, the utility, the permit office.
• Neither, just a clean example of routine work? It gets added to the gallery on the matching service page, with a one-sentence caption. It may also go out as a Google Business Profile update.

If the job passed Gate 1 but the photos are weak and the story is ordinary, it's a GBP-only post or nothing. That's fine. Restraint is part of the system.

The routing table: where each job ends up

Print this and tape it next to whoever handles the office. It's the whole tree on one sheet.

Thirty minutes per project page is realistic when the facts arrive already captured (next section). It's not realistic when the office has to chase the tech for details three weeks later. So the capture step makes or breaks the whole thing.

How do crews capture website content without slowing down?

Your technicians are not writers, and you shouldn't ask them to be. Ask for four photos and three facts, captured before the truck leaves the driveway.

The four photos

1. The problem. The corroded flare fitting, the scorched breaker, the granule loss on the shingles. Close up, in focus, lit with a flashlight if needed.
2. The context. A wider shot that shows where it is: the attic platform, the mechanical closet, the roof plane.
3. Mid-job. Something a homeowner never sees: the trench, the open wall, the deck after tear-off. This is the photo that builds the most trust, because it shows work hidden once the job is done.
4. The finished work. Clean, straight on, tools picked up.

If your crews already use CompanyCam, or the photo features in ServiceTitan, Housecall Pro, or Jobber, the photos are tagged to the job automatically. You already have the capture tool. What's missing is a habit and a rule for what to shoot.

The three facts

A 60-second voice memo or three lines typed into the job notes:

• What was actually wrong, in the words the customer used when they called ("water coming through the ceiling," not "secondary drain line obstruction").
• What you did, and the one decision that took judgment ("rerouted overhead instead of jackhammering the slab").
• Anything specific to this house or area ("1978 build, original galvanized lines," "HOA required matching shingle color," "Oncor had to pull the meter").

The first fact is the most valuable one in the system. Homeowners search in their own words, and AI assistants answer in those words too. A page built around "water coming through the ceiling under the upstairs bathroom" matches what people really type, which is why we cover this in how to get cited by AI assistants. If the question of who turns those notes into finished copy keeps stalling you, who writes the content for your website works through that bottleneck directly.

What goes on a project page for contractors?

A good project page reads like a short job report written for the next customer. Keep the structure consistent and the details unique. Repeating the skeleton is fine. Repeating the words isn't.

• A headline that names the problem and the place. "Slab Leak Reroute in a 1980s Pflugerville Home," not "Project #47."
• The symptom, in the customer's words. One or two sentences.
• What you found. The diagnosis, with the problem photo.
• The choice you made and why. This is where expertise shows. Why a reroute instead of a spot repair. Why a heat pump made sense in this house and wouldn't in another. Why you replaced decking instead of laying over.
• The local detail. Expansive clay that shifts foundations in Williamson and Travis counties, the permit office you dealt with, the age of the neighborhood's housing stock.
• The finished photo and how long the job took. Duration sets expectations and filters out tire-kickers.
• A link to the matching service page and a phone number. The project page proves it, the service page explains it, the phone number closes it.

Name images descriptively (pflugerville-slab-leak-reroute-attic.jpg rather than IMG_4471.jpg) and write real alt text describing what's in the photo. Google's image SEO guidelines are explicit that filenames, alt text, and the text around an image are how it understands the picture. Geotagging the photo file is not. That signal is a widely repeated myth, and platforms strip most of that metadata anyway. The location that counts is the one written on the page.

One job, run through the tree

Here's a hypothetical you'll recognize if you do plumbing anywhere in Central Texas. A homeowner in a 1984 Hutto subdivision calls about a hot spot on the living room floor and a water bill that doubled. Your tech confirms a hot-side slab leak. Instead of breaking the slab, the crew reroutes the hot line through the attic with PEX and insulates it.

Gate 1. The work order includes the photo-permission line, and the homeowner signed. The photos are clean: thermal camera image of the hot spot, the attic run mid-install, the capped lines at the manifold. House number and street are cropped out. Pass.

Gate 2. The site already has a slab leak service page and two reroute projects, both in Round Rock. It has nothing in Hutto. New town, familiar service: full project page.

The page. Headline: "Hot-Side Slab Leak Rerouted Through the Attic in Hutto." Symptom: "warm spot on the living room tile and a water bill that jumped." Decision: why a reroute beat a slab repair in a house this age, where a second leak on the same line is likely. Local detail: the expansive clay under much of eastern Williamson County that stresses old copper under slabs. Link to the slab leak service page. License number in the footer, phone number in the header.

Total office time: about half an hour, because the tech's voice memo already held the three facts. That page now answers a Hutto homeowner searching for the exact symptom they're standing on.

When should project pages roll up into city pages on your website?

This is the branch where contractors get into the most trouble. The common move is to spin up 40 "[service] in [suburb]" pages that differ only by the town name. Google's spam policies name exactly that pattern, doorway pages, as a violation, and it can drag down the whole site, not just the copied pages.

Project pages give you a defensible version. Use this rule:

• Fewer than three published projects in a town: no city page. Link the projects from the service page and let them stand on their own.
• Three or more distinct projects in a town: a city page is now justified, because it has real, unique content. The jobs, the local conditions they revealed, the neighborhoods you've worked. Build it as a hub that links to those projects.
• A town you serve but have never published a job in: leave it to your service-area settings, not a page. We cover that setup in Google Business Profile settings for service area businesses.

A city page that grows from real jobs only ever adds evidence. A city page created from a template is a promise with nothing behind it.

How do you know the system is working?

Give it a quarter before judging. Then check three things:

• Impressions on project pages. In Search Console, filter pages by your projects folder. Rising impressions on long, specific queries ("water heater replacement attic no drain pan") mean it's working. Our walkthrough of what to check in Google Search Console every month shows where to look.
• What callers mention. Ask your CSRs to log whenever a caller says "I saw the one you did in…" That sentence is the clearest signal you'll get.
• Capture rate. Count completed jobs against jobs with four photos and three facts. If the capture rate falls under about half, the problem is crew habit, not the website. Fix it at the morning meeting, not in the content plan.

One quiet note from our side: when we build sites at Turnkey Web, the project page template and the routing rules are part of the build, so the office is publishing in week one instead of guessing. Whoever builds yours, insist on the same thing. The template should make the right page the easy page.

Questions contractors ask about job-based website content

Do I need customer permission to post photos of a job?

Get it in writing every time. A single line on the work order or invoice covers it: the customer allows photos of the work to be published without their name or address. It costs nothing and removes every awkward conversation later.

Should I list the customer's address or name on the project page?

No. Use the city and, at most, the neighborhood or ZIP. Crop out house numbers, plates, and anything personal inside the home. Location helps rankings at the town level. Street-level detail adds risk and no ranking benefit.

How many project pages should we publish a month?

As many as pass both gates, and no more. For a typical residential shop that's often two to six full pages a month, with the rest going to galleries. Steady beats bursty: a few strong pages every month do more than 30 in one week and none after.

Can the techs just post straight to the website from the field?

Let them capture from the field and let the office publish. Techs are good at photos and facts. Someone else should check the gates, crop, write the headline, and link the page. Direct-from-truck posting is how unsafe photos and unfinished jobs end up public.

Does geotagging job photos help us rank in that city?

Not in any way you should rely on. Most platforms strip photo location metadata, and Google's guidance focuses on filenames, alt text, and the page text. Write the city, the neighborhood, and the specific problem into the page itself. That's the location signal that counts.

Frequently asked questions

Do I need customer permission to post photos of a job?

Get it in writing every time. A single line on the work order or invoice covers it: the customer allows photos of the work to be published without their name or address.

Should I list the customer's address or name on the project page?

No. Use the city and, at most, the neighborhood or ZIP. Crop out house numbers, plates, and anything personal inside the home. Street-level detail adds risk and no ranking benefit.

How many project pages should we publish a month?

As many as pass both gates, and no more. For a typical residential shop that's often two to six full pages a month, with the rest going to service-page galleries. Steady beats bursty.

Can the techs just post straight to the website from the field?

Let techs capture photos and facts in the field and let the office publish. Someone needs to check permission and safety, crop, write the headline, and link the page before anything goes public.

Does geotagging job photos help us rank in that city?

Not in any way you should rely on. Most platforms strip photo location metadata. Write the city, neighborhood, and specific problem into the page text, along with descriptive filenames and alt text.