Your homepage in January and your homepage in July should not say the same thing
One layout can serve both seasons if the top of the page is built to swap.
In the cold months the visitor landing on your homepage is usually mid problem. Frozen line, no hot water, water spreading across a basement floor. Everything above the fold should answer availability: are you working tonight, how fast, and what do I tap.
In summer the same page draws a different reader. A sewer replacement, a repipe on a two-flat, a bathroom rough in. That reader wants credentials, photos of finished work, and enough detail to build a shortlist.
Build the hero as a swappable block rather than a fixed image with text baked into it. Two or three seasonal variants, changed on a schedule, cost almost nothing after the first build and beat a generic message that fits neither visitor.
Keep the rest of the page stable. Seasonal switching belongs to the first screen and the featured services, not to your information architecture, which should stay put so search engines and repeat visitors are not chasing moving pages.
Publish the after-hours answer, including what the trip charge is
Most plumbing sites promise twenty-four hour service and refuse to explain what that means.
A homeowner at eleven at night wants three facts. Will a person answer, roughly how long is the wait, and what does it cost to get a truck to the house. Withholding those does not protect your pricing, it moves the conversation to the competitor who published them.
Say it plainly. Who answers overnight, what the after-hours rate structure looks like in general terms, and what happens when the call lands during a cold snap with everyone already out. Ranges are fine. Precision is not required, honesty is.
The same page should say what you will not do at midnight. Plenty of shops will handle a burst line at two in the morning and will not start a sewer excavation until daylight. Naming the boundary saves both sides an argument.
Publishing the trip charge also filters. Callers who object to the fee were never going to book, and your dispatcher stops spending winter nights repeating the same number.
The form should ask where the cleanout is and whether every drain runs slow
A plumbing inquiry form asking for a message produces a callback instead of a booking.
The questions that change what happens next are all about the building. Is water still rising. Is more than one fixture backing up, which generally points at the main line rather than a single trap. Is there a cleanout, and can someone reach it. Roughly what year is the building.
Add the access questions this city needs. Whether there is rear alley access, whether the gangway takes equipment, and whether parking will be a fight. A crew arriving with the wrong truck for the space loses an hour before touching a pipe.
Keep the emergency path short. Three or four fields and a phone number, with detail gathered on the call. The long form belongs on planned work pages, where someone requesting a sewer estimate will happily answer eight questions.
Never ask the form to diagnose. Collect facts, not conclusions, and keep language that sounds like an assessment of the property off the page entirely.
The two-flat owner is a landlord and a homeowner in the same phone call
A large share of Chicago plumbing buyers own the building they live in and rent out the rest of it.
The owner of a two-flat in Logan Square or a three-flat in Bridgeport arrives with questions a single family template never anticipates. Who lets the tenant in. Whether the work kills water for the whole building. How a shared stack changes the repair. Whether the invoice can be split for tax purposes.
Give that buyer a page. Not a paragraph inside the services list, a real page about work in small multi-unit buildings, with photos of stacks, risers and basements that look like theirs.
Property managers running courtyard buildings are the same buyer at larger scale. They screen on insurance, on whether you can produce paperwork, and on whether you will speak to tenants directly. Put that where they can find it without calling.
The content pays twice. It converts a buyer worth more than a single job, and it picks up searches the residential pages never touch.
The photos that prove the work are the same photos slowing your page down
Speed and proof pull against each other, and most sites resolve it by deleting the wrong one.
Photographs of your own work sell harder than any paragraph. A basement before and after, the camera feed, the trench in a gangway, a new stack in a greystone. Stripping them out for speed removes the evidence.
Fix the delivery instead. Modern image formats, files sized for the device asking, lazy loading below the fold and a real content delivery network handle most of it. The hero should be the only large file the page loads immediately.
The heavier cost is rarely photography. Chat widgets, review carousels, several analytics tags, a booking script and a font loader can outweigh a gallery, and each one was a decision somebody made without measuring.
Test on the conditions your visitor has. A phone in a basement, on a weak signal, running a browser that has not been closed in a month. Office wifi will tell you the site is fine when it is not.
Let the frozen hose bib book itself and let the flooded basement call
Online booking and a phone number solve different problems and should not be offered as one choice.
Scheduled work is a booking problem. A water heater replacement, a faucet, a hose bib repair in spring: all of it can be picked off a calendar, and a customer who books at ten at night is a customer your competitor did not get.
Emergencies are a conversation. Someone with water on the floor needs a person who can ask whether the shutoff is closed and tell them what to do in the next five minutes. Sending them to a scheduler loses the call.
Design the two paths so they never compete. The urgent path is a tappable phone number at the top of every screen with the after-hours answer beside it. The scheduling path lives on the service pages where planned work is described.
Whatever you show, make sure it matches the real board. A calendar offering slots your dispatcher already filled costs more trust than having no calendar at all.
Questions we actually get
- How fast does a plumbing site actually need to be?
- Fast enough to be usable on a phone with a poor signal in a basement, which is a harder target than a desktop score. Get meaningful content on screen quickly, keep the hero image small and cut third party scripts you are not using. Chasing a perfect score matters less than the site being readable and tappable on the connection your emergency callers really have.
- Should we put pricing on the website?
- Ranges and trip charges, generally yes. Fixed prices for work needing a camera or a site visit, no. Publishing an after-hours fee and a typical range for common work filters out shoppers and saves the phone from repeating it. Be clear that the final number depends on what is found, and keep the language away from anything that sounds like a diagnosis.
- Do we need a separate page for every neighborhood we serve?
- Only for places you would dispatch to and can write about specifically. A page about work in Ravenswood two-flats is useful. Forty near identical pages naming forty suburbs is not, and it makes the site look like every other plumbing site in Chicagoland. Build them slowly and give each one real detail.
- Is a chat widget worth it for a plumbing company?
- It depends on who is answering. A widget staffed by a real person during business hours can catch inquiries that would never have called. An unattended bot promising a reply and delivering one the next morning damages trust and adds weight to every page. Measure it at the booked job, and remove it if it does not earn its place.
- What is the most common mistake on plumbing websites here?
- Treating the site as a brochure about the company rather than a tool for the person in trouble. Years in business above the phone number, a stock photo of a wrench, no mention of whether anyone works nights, and a contact form asking for a message. Fixing the order of information usually does more than a redesign.
