Everyone repeats the same line about websites for heating companies: people only search when the furnace dies, so all the site needs is a phone number. That’s half right, and the wrong half costs agencies clients. A local specialist offering furnace maintenance Castle Rock CO has to serve a homeowner shivering at 6 a.m. and a homeowner who is simply planning ahead, and one page layout rarely serves both.
Below we take apart five myths: the emergency-only visitor, the slider that signals polish, the service-area page with a town name pasted in, the contact form that “works,” and the site that’s finished at launch. If you build or maintain sites for trades businesses, every one of these turns up in client calls, usually right after a slow month.
Myth: Furnace owners only search when something breaks
Reality: Plenty of homeowners look up maintenance and replacement long before anything fails, and a site that treats every visitor as an emergency loses them.
The myth survives because the loudest calls are emergencies. A no-heat call is memorable. The quiet visitor who reads about a tune-up in September, or compares replacement options on a Sunday evening, never phones to tell you they were there.
We inherit this site a lot: one long “Services” page with heating, cooling and ductless work stacked in a single scroll, no clear place to click, and a footer that says “and more.” Nobody planning a visit can tell whether the company does the job they need, so they leave and try the next result.
The fix is dull and it works. Give each kind of work its own page with its own job:
- Repair and maintenance on one page, replacement and installation on another, and cooling or ductless work on their own pages.
- A booking path for planned visits that is separate from the urgent call path.
- A plain description of what a visit involves, written by the technicians instead of lifted from a template.
No-bull verdict: Keep one page per kind of work and a separate booking path for planned visits; delete the all-services wall of text.
Myth: A slider and a hero video make a trade site look professional
Reality: A heating company’s site gets opened on phones, often on weak signal, and the first thing it owes a visitor is a number they can tap.
The myth survives because sliders demo well. In a sales meeting on a fast office connection, a rotating banner looks like money well spent. Then a homeowner in a cold house opens it on one bar of signal and waits for a pile of scripts to finish before the phone number shows up.
Count the plugins on a typical inherited build: a slider, a popup, an animation add-on, a chat widget, a social feed. That’s five plugins, each loading its own scripts, and not one of them helps anyone book a visit. We aren’t saying every add-on is the enemy. We’re saying each one should name the visitor goal it serves, and “looks modern” isn’t a goal.
Build the top of the page in this order: a real tap-to-call link (a tel: link in the HTML, not an image of a number), the services in plain words, then one compressed photo of actual work. Test it on a phone, on cellular data, with wifi switched off.
One safety note for this trade. Furnaces run on gas and electricity, so the site should never coach anyone through troubleshooting. If it has a safety page, that page should tell people to leave the building and call the gas utility or an emergency number if they smell gas, and to leave repairs to licensed technicians.
No-bull verdict: Keep the tap-to-call link and one compressed photo; delete the slider, the popup and anything that loads before the phone number.
Myth: A service-area page with the town name swapped in is enough
Reality: Location pages only work when each one says something true about that place and that work.
The myth survives because it’s cheap. Copy a page for every neighboring town, swap the name, publish. Visitors notice the copy within a paragraph, and search engines have a long record of discounting pages like that. Neither is impressed.
Take a city with cold winters, like Castle Rock. A page for it should say which kinds of work the company does there, how booking works, what a homeowner should have ready before the visit and where the service area ends. Only list the places the company actually covers. Ask the owner; don’t guess from a map.
If the business serves one city, one good page beats ten thin ones. Write it for the people who live there. Cold snaps put furnaces under pressure, and the mild weeks on either side of winter are when planned work fits in. That’s local detail you can state without inventing a thing.
No-bull verdict: Keep one honest page per place the company serves; delete the clones with swapped town names.
Myth: The contact form works because your test email arrived
Reality: Forms fail silently, and a missed message in heating season is a missed job.
The myth survives because the test passes. Somebody submits the form on launch day, an email lands in an inbox, and nobody checks again. Then the host changes how outgoing mail is handled, or the owner’s mailbox starts filing notifications under spam, and the form keeps saying “Thanks, we’ll be in touch” to people nobody will ever contact.
We’ve inherited sites where the form had been dead for a long stretch and the owner blamed a mild winter. The site couldn’t be the problem, the owner figured, because the site looked fine. That’s the nasty thing about a broken form. It looks fine.
What to do instead
- Send site email through an authenticated mail service rather than the web server’s default hand-off, so notifications carry proper sender records.
- Store every submission in the database as well as emailing it, so a lost email isn’t a lost lead.
- Send notifications to two addresses, and make sure one belongs to a person who checks it.
- Submit a test entry on a schedule, and look for it in the inbox and the spam folder.
- Put the phone number in plain text right under the form, for the day it breaks anyway.
No-bull verdict: Keep the stored entries and the scheduled test; delete any form that emails once and trusts luck.
Myth: The site is finished the day it launches
Reality: A website needs maintenance on a calendar, the same as the furnace it advertises.
The irony writes itself. A good heating company tells homeowners to get the furnace checked before the cold arrives, and its own site runs on the “fix it when it breaks” plan. Updates, backups, PHP versions, expiring security certificates and plugin conflicts don’t wait for a quiet week. They land in the middle of the rush.
The sensible schedule mirrors the business. Do the heavy updates on a staging copy (a private duplicate of the site where you can break things safely) in late summer, before heating season, and again in spring, before cooling work picks up. Never do them in the middle of a cold snap, when a bad update takes the phone link down with it.
Go back to the plugin count while you’re at it. Every plugin is one more thing that can clash on update day. Fewer plugins means a shorter checklist, and a shorter checklist is the one that actually gets run. Write it down: the backup restores, the form test passes, the phone link dials, the certificate dates are fine.
No-bull verdict: Keep a written pre-season checklist and a tested backup; delete the “we’ll look when it breaks” retainer.
Where we land
Most of these myths come from treating a trades website like a brochure. It’s a tool that has to work for a worried homeowner on a bad connection and for a planner on a quiet Sunday. This week, open a client’s site on a phone, on cellular data, and try to call, book and submit the form. Fix whatever fails first, because everything else is decoration.
Test the phone link before you test the font.