The 200-Word Homepage: Why So Many Contractor Sites Say Almost Nothing

Open a contractor's homepage, scroll once, and you have often seen everything there is to see: a hero image, a headline, a phone number, maybe three service icons. No paragraph explains what the business actually does. No sentence says where it works. The page looks finished. It just does not say much.

We measure this directly. Across the 37 small-business contractor and service sites we have audited, 7, or 19%, had a homepage with fewer than 200 visible words of body content. That is not a large share of the businesses we looked at, which is itself worth sitting with. But where it shows up, it tends to show up completely: a homepage that a visitor and a search engine can both read in about fifteen seconds and come away knowing almost nothing.

What we measured, and why 200 words

We use 200 visible words as a floor, not a target. It is roughly the minimum needed to say what a business does, where it operates, and why someone should trust it with a job. Below that line, a homepage is usually leaning entirely on images and a headline to do work that actually requires sentences.

Nineteen percent is not the largest finding in our audit corpus, not close. Logo usability problems showed up in 76% of the sites we looked at, and 35% had no click-to-call link at all. Thin homepage content is a smaller, sharper problem: rarer, but unmistakable once you see it.

What a thin homepage usually looks like

The pattern is consistent enough to describe without naming any specific site. A large hero image fills the top of the screen, often stock photography of a truck or a tool rather than the business's own work. A short headline sits over it, something like "Quality Service You Can Trust." Below that, three or four icons represent service categories, each with a two- or three-word label and nothing else. Then the footer.

Nowhere in that layout is there a paragraph. Nothing says how long the business has operated, what specifically it repairs or installs, which towns it actually serves, or what separates it from the three competitors a visitor is also considering. The page is visually clean and informationally empty at the same time, which is an easy trap to fall into when a homepage is built around a template's design rather than around the business's own answers.

What thin content actually costs you

Two different audiences read a homepage, and both come away shortchanged by one with too little on it.

A visitor comparing three or four local businesses is trying to gauge depth: does this company do exactly what I need, and does it sound like it knows what it is doing? A page with no real description gives them nothing to judge, so the decision falls back to price or whichever competitor said more. A search engine reads the same page looking for the same signal in a different form. It has almost no text to associate with your services or your service area, which makes it harder for the page to surface for the searches that actually matter to your business. We have not measured search rankings across our audit corpus, so we will not put a number on that effect, but the mechanism is well understood: pages need real text about a topic to be found for that topic.

What to put there instead

This is not a call to pad the page with filler. It is a call to actually say what the business does, in plain sentences, the way you would explain it to a new customer on the phone.

A homepage worth reading usually covers a short, specific list of things: the services offered, described with enough detail that a visitor can tell them apart from a competitor's; the towns and neighborhoods actually served, named plainly rather than implied; how long the business has operated and any licensing or certification that matters in the trade; and a clear next step, a phone number that dials and a form that works. None of that needs to be long. It needs to be there, in sentences a person and a search engine can both read.

If your own homepage reads more like a business card than a business, that is the fix, and it is one of the cheaper problems on this list to solve. In most cases it is a content and structure fix, not a full rebuild.