Say which side of the county line you cross before you say anything else
A visitor in this metro is asking a jurisdiction question first, and a homepage that answers it in the first screen keeps people who would otherwise bounce.
The City of St. Louis is an independent city, separate from St. Louis County. Locals do not treat them as one place, and a plumbing site that says St. Louis and nothing more reads as either an out of town lead broker or a shop that has not thought about it.
Name the places. City neighborhoods you cover, the county municipalities you dispatch to, whether you go west into St. Charles County, whether you cross the Mississippi into the Metro East. Put it in the first screen in plain text, not on a service area page three clicks down.
A coverage map graphic is not a substitute. Half your visitors are on a phone in a poorly lit basement and will not pinch and zoom to find out if you come to Florissant.
The honesty cuts both ways. Naming where you do not go is worth as much as naming where you do, because every refused call costs a dispatcher time and sometimes costs you a review.
A 1920s brick two family and a Chesterfield subdivision need separate pages
The housing stock here splits sharply, and one generic services page speaks convincingly to neither owner.
Brick construction is unusually consistent across this metro, and older brick homes come with their own plumbing reality: cast iron stacks, galvanized supply, laterals that run under sidewalks, basements that were never meant to be finished.
Newer construction to the west is a different conversation entirely, with different fixtures, different access and different expectations about how quickly work happens.
Give each its own page and write it for someone who likes their house. An owner of an old brick place in Tower Grove or Dogtown does not want to be told their home is a problem. They want to know you have worked on twenty like it.
Freeze-thaw belongs in that content too, because it shapes what fails and when: exterior hose bibs, lines running through unheated crawl spaces, sump discharge, basement floor drains during a thaw. Describe the conditions, and stop short of telling a stranger what is wrong with their specific house.
Ask for the year built, the shutoff location and whether the basement is finished
A plumbing inquiry form should collect what changes the dispatch decision, and nothing else.
Most forms on plumbing sites ask for name, email, phone and a message box. The message box produces a paragraph of panic and the office calls back to ask the same four questions anyway.
Ask instead for the things that change the truck. Address or at least the municipality. Whether the water is shut off. Where the shutoff is, if they know. Approximate year built. Whether the basement is finished, which changes both access and the damage conversation.
Keep it short enough to finish one handed. Four or five fields answered honestly beat nine fields abandoned at the third.
Then confirm in writing immediately, by text if you can. Someone who has just submitted a form while standing in water needs to know a person has it, and the confirmation screen is where that promise starts.
Every widget you bolt on costs a call from a basement with one bar
Speed is not a technical scorecard item on a plumbing site, it is whether the page opens where the problem is.
Plumbing emergencies happen in the least connected parts of a house. Basements, crawl spaces, utility rooms, the back of a garage. Signal is poor and patience is shorter than usual.
The usual culprits are predictable: an oversized hero image, a background video nobody watches, a chat widget, several tracking scripts and a review carousel that loads from somewhere else. Each one is defensible on its own and collectively they are why the page takes too long.
Test the way your customer arrives. A phone on a weak signal, not a desktop on office internet. If the phone number is not tappable within a couple of seconds, nothing else on the page matters.
The cheapest wins are almost always the same. Compress and correctly size the hero image, defer or remove third party scripts, and put the phone number in the markup rather than inside an image or a script that has to load first.
Show the trench, the crawl space and the patched brick, not a model in clean coveralls
Photographs of your own work in recognizable local settings do more for trust than any badge row.
Stock photography reads as stock photography, and homeowners here are used to being marketed at by companies that do not work in their zip code.
Photograph your own jobs. A trench in a narrow yard. A camera feed from a lateral. A crawl space with new supply lines. Patched brick and restored ground after a dig. The alley behind a city two family.
Credentials matter and belong on the page in plain language: that you are licensed and insured as required where you work, and that a certificate is available on request. Keep it factual and avoid stating requirements that vary by state and municipality.
For commercial and property management visitors, put the paperwork path in an obvious place. That reader is screening vendors, not shopping, and they will leave rather than hunt for it.
An emergency visitor and an estimate shopper cannot share one call to action
Two very different people arrive at a plumbing site, and one page trying to serve both usually serves the cheaper one.
The emergency visitor wants a phone number, an honest answer about tonight, and nothing in the way. The replacement shopper wants detail, a sense of process, and a way to start a conversation that does not commit them to anything.
Give them separate paths from the first screen. A call action for right now, and a quieter secondary path toward the sewer lateral, water service and repipe pages where the reading happens.
Those bigger pages should be written like documents, not brochures. What the inspection involves, how access works, what the site looks like during and after, what varies by municipality and why the homeowner should confirm current requirements with their local building department.
After hours, the site is doing the work of a person. Say plainly what happens when someone calls at midnight, whether it rings a human or a service, and what a realistic response looks like. Vagueness there costs more calls than an ugly template ever will.
Questions we actually get
- How much of a plumbing website actually matters?
- The first screen on a phone, the phone number, the service pages for your highest value work, and the inquiry form. Everything else is secondary. Most redesigns spend their budget on the parts a customer never reaches, and skip the four things that decide whether a call happens.
- Should the form ask for a photo?
- Optional, never required. A photo helps enormously with drains, water heaters and visible leaks, and requiring it will lose you the person who is holding a towel against a joint with their other hand. Offer it as a step after submission instead.
- Is a chat widget worth it for a plumbing company?
- Only if a real person answers it during the hours it is visible. An unanswered chat bubble costs load time and creates an expectation you then break. For most plumbing shops a fast tappable phone number and a short form outperform it.
- Do I need separate pages for each suburb?
- For the places you actually dispatch to and can say something specific about, yes. Kirkwood, Webster Groves, Maplewood and Chesterfield are real distinctions to a local reader. Duplicated pages with a swapped town name do the opposite of what they are meant to do.
- Can my website say what a repair will cost?
- You can publish ranges, a trip or diagnostic fee, and how pricing is structured, and doing so filters out a lot of unproductive calls. What the site should avoid is pricing a specific unseen job or implying an insurance outcome. Anything code or permit related is generally worth pointing back to the local building department.
