A house with radiators needs to see in one glance that you touch boilers
Owners of hydronic systems have been turned away enough times that they scan for the word before they read anything else.
Brick two-flats and four-families across the City of St. Louis were built for boilers and radiators. The people who own them know that many contractors will not touch that equipment, so they look for confirmation immediately.
Put it in the navigation and in the first screen, not buried on an inside page. Boiler service, radiator systems, steam. Naming the equipment does more work than any headline about comfort.
If you do not service boilers, say that too. An honest exclusion saves you a call that would have wasted twenty minutes and annoyed somebody.
The same logic applies to older gravity furnaces, converted systems and any equipment class where availability is the real question. Availability beats persuasion for that reader.
Two neighboring streets, two municipalities, so the form needs more than a city name
A dispatcher cannot act on a form that says St. Louis, because half the metro types that regardless of where they live.
The City of St. Louis is an independent city, separate from St. Louis County, and the county holds a long list of small municipalities. Maplewood and Brentwood sit next to each other. Permitting and inspection practice can differ between them, so the intake data has to be specific enough to route and to plan.
Ask for the service address early, or at minimum the ZIP and the municipality. The answer decides whether the job is yours, which crew takes it and what the paperwork looks like.
Keep the rest short. Equipment type, what is happening, the best number, and whether anyone is home. Long forms lose the emergency visitor and teach the replacement visitor nothing useful.
Add one optional field that saves a phone call: a photo upload for the nameplate or the equipment. The people who use it will save your office real time, and nobody is punished for skipping it.
Your best photographs are in the basement, and nobody takes them
Stock imagery of a smiling technician next to a condenser proves nothing to a homeowner in an old brick house.
The photographs that convince someone here are of the work: a new boiler piped cleanly in a Soulard basement, a line set cover run neatly down a brick wall, a furnace swapped in a stairwell that barely fit it.
Real photos do a second job. They tell a homeowner what their own basement might look like afterward, which is the single most common private worry about a replacement.
Ask crews for two photos per job and give them somewhere to put them. Most of what you need already exists on somebody's phone.
Compress properly and size them for a phone. Image weight is the most common reason a contractor site that looks fine in the office crawls in the field.
The morning after a hard freeze is a load test you did not schedule
Your busiest hour of the year is the hour your site is least likely to be fast.
When the metro drops below freezing overnight, thousands of people search the same thing at the same time on mobile networks that are already busy. If the site is heavy, that is the moment it fails.
Cut the obvious weight first. Autoplaying video in a hero, three font families, a chat widget, five tracking scripts and a slider that nobody has ever clicked. Each one costs a fraction of a second, and each fraction costs calls.
Test on a real phone on a cellular connection, standing in a basement if you can, not on office wifi. The basement matters because that is where people are standing when they look at the furnace and then look at their phone.
Make the phone number tappable and visible without scrolling on every page. It sounds obvious. It is missing from a surprising number of contractor sites.
Publish what a diagnostic visit costs before somebody has to ask
You cannot publish a system price, but you can publish the part of your pricing that never changes.
Nobody expects a furnace price on a website, because the number depends on the house. Everybody wants to know what it costs to get somebody to the door, whether the fee applies to the repair and what happens after hours.
Answer all three plainly. Price transparency at the visit level removes the most common reason a caller hesitates, and it saves your office from having the same conversation forty times a week.
Then explain the estimate process for replacements: who comes out, how long it takes, what they look at, when the proposal arrives, whether financing is available. Process detail reassures a considered buyer more than a discount does.
Avoid publishing utility rebate figures or eligibility rulings. Programs change, and it is generally better to say that incentives may apply and point people to confirm current terms with the utility.
Name equipment in the navigation, not the words heating and cooling
Two menu items called Heating and Cooling force every visitor to guess whether you do their specific thing.
A site menu is a routing tool. When it lists furnaces, boilers, heat pumps, ductless, water heaters and air quality, every visitor self selects in one glance and lands somewhere that speaks to them.
Two generic buckets do the opposite. They push everyone onto one page that has to serve a repair emergency and a major purchase decision in the same paragraph, and it serves neither.
Give commercial or multifamily work its own path if you do it. A landlord with several brick buildings in Tower Grove reads a completely different page than a homeowner in Webster Groves, and mixing them costs you both.
Keep a clearly labeled service area page and be specific on it. City, county municipalities you actually cover, St. Charles County if you go there, and the Metro East only if you are licensed to work in Illinois, which is generally worth confirming before you publish it.
Questions we actually get
- Do we need a whole new site or can we fix what we have?
- Start with a measurement pass on a real phone over cellular data. Often the biggest gains are removing weight, fixing the form fields and rewriting the first screen, all of which are edits rather than a rebuild. A rebuild is warranted when the platform itself makes those changes impossible or when the structure has no room for equipment level pages.
- Should we put prices on the site?
- Publish what does not vary: the diagnostic or trip fee, whether it applies to the repair, and after hours terms. Leave system pricing off, because it depends on the house, and explain instead how the estimate works and what a visit involves. Buyers generally accept the absence of a price when the process is clear.
- How many fields should the inquiry form have?
- Enough to dispatch, and no more. Service address or municipality, equipment type, what is happening, phone number and whether someone is home usually covers it. An optional photo upload for the equipment nameplate is the one extra field that consistently earns its place.
- Do we need a separate page for every municipality we serve?
- For the site's structure, what matters more is a clear service area page and equipment pages that convert. Municipality pages are worth building only where you can write something true and specific about working there. Empty location pages add navigation clutter without helping anyone decide.
- Does the platform we build on affect speed?
- Less than what gets loaded onto it. Most slow contractor sites are slow because of uncompressed photos, video backgrounds, multiple tracking scripts and page builder bloat, not because of the underlying platform. Fix the payload first, then judge whether the platform is still the constraint.