The first screen belongs to site conditions, not to a sunset rendering
Before a buyer here cares about finishes, they want evidence you have dealt with the ground under their yard.
Renderings sell the finish, and the finish decision comes late. The first screen should carry three things instead: what you build, which counties and cities you build in, and one clear line acknowledging the site work that comes before any concrete goes in.
A photograph of an excavation with steel in it is more persuasive to a nervous Tampa buyer than any twilight render. It says you have been in this ground before, which is precisely the doubt they arrived with.
Keep the phone number and a booking link visible without scrolling and without a modal. A homeowner in a backyard is not going to hunt for a way to contact you when the next builder's number is one tab away.
Say who you are in a sentence a peer would use. Licensed builder, this many years, these counties, these kinds of jobs. Vague brand language costs you the reader who came to check whether you are real.
A service area page that admits which side of the bay you will drive
Publishing an honest map saves more money than any headline you could write.
Name the Hillsborough places you serve and the Pinellas places you serve, and say plainly where you do not go. A homeowner in Tarpon Springs who reads a clear boundary self-selects out, and you keep the truck roll you would have wasted.
Vague coverage claims across a metro split by water produce inquiries you have to disqualify by phone. Every one of those calls costs a person twenty minutes and costs the caller a bad first impression of you.
If a city page exists, give it real content. Typical lot conditions, access constraints, what permitting generally involves there and where a reader should confirm it. A page that swaps a city name into the same paragraph fools nobody, including search engines.
If you do cross the bay, say what that means practically. Route days, a longer lead time on the first visit, a minimum project size. Buyers respect a stated constraint far more than a vague promise that quietly falls apart later.
Ask what the survey, the gate and the county will allow
The inquiry form for this trade has to capture the facts that decide whether a job is buildable and worth driving to.
The useful fields: city and county, new build or renovation, whether a pool exists now, rough timeline, budget range, HOA or deed restrictions, and access. Eight fields is the outer limit before completion falls off a cliff.
Access is the field almost every pool site omits and the one that decides the equipment you bring. Ask about gate width, side yard route and whether a machine can reach the back. Then add an optional photo upload for the yard and the access path, because a photograph answers what three questions cannot.
Ask whether they have a current survey. A yes shortens your timeline noticeably, and a no tells you what the first follow-up conversation has to cover.
Never ask for anything you will not use on the first call. Every field you do not act on is a field that quietly cost you an inquiry.
Show the excavation and the steel, because that is the part buyers worry about
Finished glamor shots are table stakes; the middle of the build is where trust is actually earned in this market.
Publish a real sequence: layout, dig, steel, plumbing, shell, inspections, deck, finish and startup. Photos from your own jobs, in order, with plain captions explaining what is happening and roughly how long it takes.
Include the parts that go sideways. An unexpected condition below grade, a design change an engineer required, how a change order gets handled and priced. Buyers here are already anxious about surprises, and a company willing to describe one is the one they call.
Label work by neighborhood, never by address. No client addresses, no recorded paperwork, no permit documents with names on them, and nothing that could identify a specific property.
Short clips of a dig or a gunite day outperform drone flyovers for this reader. Aerial footage is beautiful and answers none of the questions keeping a homeowner awake.
A phone stuck on the Gandy still has to load your gallery
Pool sites are heavy by nature and your buyer is frequently on a phone in a driveway or a truck, not on office wifi.
Serve modern image formats at the dimensions actually displayed, lazy load everything below the first screen, and give the hero image loading priority so the page has something on it immediately.
Cut the third party scripts. Chat widgets, review carousels, heat maps and tag managers stack up fast, and a chat bubble that blocks the first paint loses more inquiries than it captures.
Test on a throttled mobile connection rather than the office network. The experience that matters is a phone in a backyard with two bars, not a desktop on fiber.
Fonts are a common silent tax. Two weights of one family, loaded properly, is enough. Nobody has ever chosen a pool builder on typography.
Let the engineer make the engineering claims on your site
Pages that touch soil, structure or insurance need attribution and hedging built into the sentences themselves.
Write that a licensed engineer determines what a given site requires, and that coverage questions belong with the reader's insurer. Say that permitting requirements are worth confirming with the county. Keep those qualifiers in the copy, not in a footer disclaimer.
Publish your license number and say how a reader can verify it with the state. Reference insurance in general terms. Both are checked more often than builders assume, particularly by newcomers who have no local network to ask.
Never publish anything that implies a property is safe, that a claim will be paid, or that a specific lot will pass a review. Those sentences create exposure and they add nothing a buyer needs.
Have counsel read the technical pages once. A single review of the soil, permitting and warranty language is cheap insurance against a page that outlives the person who wrote it.
Questions we actually get
- How many photos should the site show before it gets slow?
- Volume is less of a problem than weight. A well-built gallery with correctly sized modern formats and lazy loading can carry hundreds of images. A dozen full resolution files dropped straight onto a homepage will sink it. Judge the site by how fast it paints on a throttled phone, not by an image count.
- Should I put pricing on the website?
- Ranges help more than they hurt in this trade. A stated starting range filters out buyers who were never going to sign and improves the quality of the inquiries you do get. Frame it as typical range for a scope, note that site conditions change costs, and keep it current.
- Do I need separate pages for each city I serve?
- Only for places you genuinely work and can describe with specifics: lot conditions, access, permitting notes worth confirming locally, and real projects. Substance is the whole test. A page that mentions Clearwater once and says nothing about Clearwater is worse than nothing.
- What should never appear on a pool company website?
- Client addresses, recorded permit documents with names, anything implying an insurance outcome, and any claim that a property is or is not affected by ground conditions. Also avoid before and after photos published without the owner's written permission.
- Is a photo upload field on the form worth the friction?
- Yes, as long as it is optional. A single photo of the yard and the access route often answers what three form fields cannot, and inquiries that include one convert to booked visits at a noticeably better rate because you can qualify before you drive.
