Nashville, TN

    A roofing site built for a phone held in a Donelson driveway

    A roofing website has one job and about eight seconds to do it. The visitor is usually standing outside looking at something that worries them, on a phone, with a competitor's site open in another tab. They want three answers: do you come to my street, do you handle roofs like mine, and can I reach a human today. Everything else on the site is secondary to those three. Below is how we would build a roofing site for a Middle Tennessee contractor working across Davidson, Williamson and the counties around them, including what the inquiry form has to capture for this trade and why the gallery is usually the thing losing you visits.

    Almost every visit starts on a phone held in somebody's driveway

    The design decisions that matter are the ones that survive a small screen, one bar of signal and a person who is not sitting down.

    Design the phone view first and let the desktop version follow. Most roofing traffic is mobile, and the person is often outside, distracted, and doing this between other things.

    A tap to call button belongs in the top bar and it belongs there on every scroll position, not just the top of the page. Half your visitors have no intention of filling out a form.

    Type has to be readable in daylight without pinching. Contrast, size, and buttons big enough for a thumb. Small gray text on white is a design choice that costs calls.

    Nothing should move on its own. Sliders, autoplaying video and pop ups that fire before the page settles all steal the moment where the visitor was deciding whether to tap the phone number.

    If a form is the primary conversion path, the first field should be visible without scrolling twice.

    The first screen has to name the counties you cross for and the ones you do not

    The most common unanswered question on a roofing website is whether the contractor actually comes out to this address.

    Metro Nashville and Davidson County run as a consolidated government while Williamson, Rutherford, Sumner and Wilson do not, and homeowners know perfectly well that a contractor may or may not cross the line for their street. Put the answer in the header, not on a buried service area page.

    Name real places. Franklin, Brentwood, Hendersonville, Mount Juliet, Murfreesboro, Bellevue, Donelson. A list of county names alone reads like a legal disclaimer; a list of towns reads like somebody who works there.

    Say what you do not do as clearly as what you do. A contractor who states plainly that they do not run repairs past a certain distance saves the estimator a wasted morning and earns trust from the person they turned away.

    Give each county a real page with real content behind that header link. Not a template with a name swapped in, which visitors spot as quickly as search engines do.

    Ask for the roof's age and pitch before you ask for a last name

    A roofing inquiry form should collect what the estimator needs to decide whether this is a truck roll, and nothing else.

    The fields that earn their place: address or at least the town, roughly how old the roof is, what is happening now, whether there is active water coming in, and the best number to reach them on. Photograph upload is worth having, because half of them already took pictures.

    Roof age is the single most useful field on the form. A roof under ten years old is usually a repair conversation and a very different appointment from a roof at the end of its life. Knowing which one is arriving changes who you send.

    An upload field pays for itself in this trade. A photo of a ceiling stain or a lifted ridge tells your estimator more than three paragraphs of description.

    Cut everything else. Preferred contact time, how they heard about you, a dropdown of nine services: each optional field is another reason to abandon on a phone.

    Route the submission to a phone somebody actually holds, not only to an inbox that gets checked at five. A roofing inquiry has a short shelf life.

    Show roofs people recognize: a 12 South gable, a Germantown row, a Brentwood hip

    Photography is the part of a roofing site that does the persuading, and stock photography does none of it.

    A homeowner in Sylvan Park has been looking at their own cut up, steep, added onto roof for weeks. A photograph of a generic suburban ranch tells them nothing. A photograph of a roof shaped like theirs tells them you have done this.

    Organize the gallery by the kind of roof rather than by date. Older inner neighborhood work, subdivision replacement work in Mount Juliet or Murfreesboro, low slope sections, metal. Let the visitor find themselves.

    Include before and during shots, not only the finished roof. Decking, underlayment, the flashing detail at a wall. Homeowners who have been quoted three times are trying to work out what they are paying for, and the during shots are what explains it.

    Use your own crews and your own trucks. It is the cheapest credibility on the site and it is the one thing a competitor cannot copy.

    Keep specific client addresses off the page. Neighborhood level is plenty.

    A full resolution gallery is what loses the Green Hills homeowner comparing three tabs

    Roofing sites are heavy because roofing sells on photographs, and heavy sites lose the visit before the first photograph appears.

    Phone camera images straight off the card are enormous. Resize them to the size they are actually displayed at, serve modern formats, and let anything below the fold load only when it is scrolled to.

    Load the hero image eagerly and everything else lazily. The first image is the one holding the visitor; the other forty are not needed in the first second.

    Drone footage is the single heaviest thing most roofing sites carry. If it stays, it should never autoplay and never load on mobile by default.

    Audit what the site is loading beyond your own content. Chat widgets, review carousels, tracking pixels and font files add up quietly, and a site can be well designed and still slow because of what was bolted on afterward.

    Test on a real phone on cellular data, standing outside, not on the office wifi. It is a different website out there.

    Ice storm traffic arrives at night and wants one button, not a contact page

    Weather driven demand in Middle Tennessee arrives outside business hours, and the site has to hold that visitor until morning.

    Real winters mean real ice, and the traffic that comes with it lands late, worried, and looking for one thing: somebody to stop the water.

    Build a single emergency path. One page, one number, one plain statement about what happens after hours and how fast someone can be there. Not a general contact form.

    If you cannot answer at midnight, say so and say what you do instead. An honest line about being on site first thing beats silence, and it beats an answering service reading a script.

    The same page should tell people what to do while they wait, and what not to do. Nobody should be climbing onto an iced roof because your website suggested it.

    On coverage and claims, keep the language conditional. What an insurer will pay for is worth confirming with the insurer, and the site should not rule on it.

    Questions we actually get

    What actually belongs above the fold on a roofing homepage?
    Four things: what you do, which towns and counties you cover, a tap to call number, and one photograph of real work that looks like the visitor's roof. Everything else can wait. Awards, taglines and a mission statement are not answers to the questions somebody standing in a driveway is asking.
    How many fields should the inquiry form have?
    As few as possible while still telling your estimator whether to send someone. Town or address, approximate roof age, what is happening, whether water is actively coming in, and a phone number. A photo upload is worth adding because most people already took pictures. Every additional optional field costs completions on a phone.
    Should we put pricing on the site?
    Not a firm price, because roofs vary by pitch, access, decking condition and covering, and quoting a number you cannot honor damages the first conversation. What does work is explaining how a roof is priced and what a proposal should itemize. Newcomers to the area have no baseline, and the page that gives them one is often the page they call from.
    Is a chat widget or an AI assistant worth adding?
    Only if someone answers it. An unattended chat widget adds page weight, competes with your phone number, and leaves messages nobody reads until morning. For a trade where the inquiry has a short shelf life, a visible phone number and a fast form generally do more than a chat bubble.
    How do we handle insurance claim content on the website?
    Carefully and conditionally. Explain what an inspection generally looks at and what documentation usually helps, and stop there. Do not state that a claim will be approved, do not diagnose a specific roof from a description, and point people to their insurer or their own counsel on coverage. It is the riskiest copy on a roofing site and the easiest to get wrong.

    What is different here

    Florida has tightened what a roofing contractor may say to a homeowner about an insurance claim, and the rules around soliciting claim work carry real consequences for the client rather than the agency. Design wind speed and product approval also vary by county, so a re-roof specification is a local document. Marketing built around storm claims needs legal review before it runs.

    Written by KC Thompson, Morgul Marketing.

    Tell us the number you are trying to move.

    We will say which of these disciplines would move it, and which would not.

    Book a Strategy Call