Emergency traffic and replacement traffic need separate front doors
Two different people arrive at an HVAC site and they are not looking for the same thing.
One visitor has no heat tonight and wants a phone number and an arrival window. The other is comparing systems and wants specifications, financing terms and a sense of whether your crew is competent. A single home page written to please both usually serves neither.
Give each a clear path from the top of the page. A prominent call route for the urgent visitor, and a distinct path into equipment and replacement content for the researcher. Do not bury the second one under a scrolling gallery.
The urgent path should be short: tap to call, a visible arrival expectation, and a fallback form for people who will not call. The replacement path can be long, because that reader will read.
Commercial and light commercial deserve their own entry as well if you take that work. A property manager will not dig through residential content to find out whether you handle rooftop units.
Put coverage and an arrival window above the fold, not a hero video
In a metro defined by drive time, the first thing a visitor needs to know is whether you come to them.
Name places, not regions. A visitor in Dunwoody reads the phrase greater Atlanta area and learns nothing. A short list of the suburbs and counties you dispatch to answers the question in two seconds and screens out inquiries you would have declined anyway.
Be honest about the shape of your coverage. If you run inside the Perimeter all day but only reach the far Gwinnett corridor in the morning, say something to that effect. Vague coverage claims buy late arrivals and bad reviews.
Set an arrival expectation instead of a promise. Language like same day where the schedule allows, with a call back to confirm, is both true and more persuasive than a guarantee nobody believes.
Credentials belong here too: license number, insurance, how long you have been operating, whether the person arriving is an employee. Those facts do more for trust than any photograph.
Ask for the address early, because access under old oaks decides the visit
An HVAC inquiry form should collect what a dispatcher needs to route a truck, and nothing else.
The single most useful field is the service address, because it determines the zone, the drive time and whether the job can be run today. Ask for it before the email address.
Then ask about the equipment: heating or cooling, what the system is doing or not doing, roughly how old it is if they know, and where the equipment sits. Crawlspace, attic, closet, side yard. Access is a real variable here, where mature tree canopy, narrow older lots and tight side yards all affect how a crew shows up prepared.
Keep the field count low and make everything optional except address and phone. Every additional required field costs completions, and a dispatcher can fill the gaps on the callback.
Add a photo upload and let people use it. A picture of the unit and the model plate saves a phone conversation and helps the tech arrive with the right part.
A Decatur ranch and a Johns Creek two story are not the same job page
The housing stock across this metro varies enough that one generic service page cannot speak to both halves of it.
Older intown and inner suburb houses bring crawlspaces, ductwork in unconditioned space, equipment added to houses that predate central air, and red clay soil that keeps those crawlspaces damp. The problems people describe are humidity, smells and rooms that never match the thermostat.
Newer construction outside the Perimeter brings attic ductwork, second floor rooms that will not cool, zoning questions, and whole subdivisions where builder equipment reaches end of life at the same time.
Write pages that recognize the difference. A visitor who reads a paragraph describing their exact house believes the rest of the page more, and the page ranks better for the same reason.
Use your own job photographs. A picture of a crawlspace or an attic run from a job you actually did carries more weight than any stock image of a smiling technician, and it costs nothing to produce.
Build the page for a weak signal in a shaded driveway
Site speed is a business metric for a trade whose customers are often outdoors, on a phone, in a hurry.
The site that feels instant on office wifi can be slow on a phone with a weak signal in a neighborhood under heavy canopy. Test it that way, on a real device on cellular data, before signing off on a design.
Photographs of equipment and vans are usually what makes a contractor site heavy. Compress them properly, serve modern formats, size them for the space they occupy, and never load a full resolution image into a thumbnail.
Third party scripts do the rest of the damage. Chat widgets, review carousels, tracking tags and font loaders each cost time. Keep the ones that earn their place, and load nothing that blocks the first paint.
The number to watch is how long until the visitor can tap the phone number. Everything else on the page can arrive afterward.
One page has to sell heating and cooling in the same breath
A two-season market changes what a maintenance plan page needs to argue.
A plan built for a cooling-only market visits once a year. Here the honest version is two visits, one before the cooling season and one before heating, and the page has to justify both without sounding like a subscription upsell.
Explain what each visit actually includes in plain terms. Homeowners who have been sold vague memberships are skeptical, and specificity is the antidote.
Show what the plan does for the customer beyond a discount: priority scheduling during a heat wave or a freeze, a documented history of the equipment, an early warning before a failure. Those are the reasons people actually renew.
Make signing up possible on the page. A plan that requires a phone call to join will lose the person who was ready at 10pm.
Questions we actually get
- How many fields should our inquiry form have?
- Fewer than you think, with only the service address and phone number required. Everything else, system type, symptom, equipment location, age, photo upload, should be optional and easy to skip. The goal is not a complete record, it is enough information for the callback to be about scheduling rather than discovery.
- Do we need a separate mobile site?
- No, but the site should be designed mobile first, because most HVAC traffic is on a phone and often in a hurry. That means a tap-to-call element that is always reachable, forms that work with one thumb, text sized to be read outdoors, and a page that loads on cellular data rather than only on wifi.
- Should we publish our pricing?
- Publishing a diagnostic or trip fee is usually a net positive because it filters out people shopping purely on price and builds trust with everyone else. Full replacement pricing is harder, since the number depends on the house, and publishing a figure you cannot honor creates a worse conversation later. A price range with clear conditions is generally safer than a single number.
- What should we not put on the site?
- Anything you cannot substantiate. No invented review counts, no results you did not produce, no claims about permits or code requirements for a jurisdiction you have not checked, and no promises about what an insurer will cover. Where a question touches code, permitting or insurance, say that practice varies and point the reader to the local building department, their insurer or their own counsel.
- How fast does the site actually need to be?
- Fast enough that someone standing outside on a weak signal can tap your phone number almost immediately. Rather than chasing a specific score, test on a real phone on cellular in a neighborhood with heavy tree cover. If the number is tappable before the images finish loading, the page is doing its job.
