Morgul Marketing

    Designing a roofing site that sorts Kentucky from Indiana in ten seconds

    A roofing website in this metro has one job before it has any other: tell the visitor whether you work their street. Most arrive on a phone, many are standing outside looking at something wrong, and a real share of them are on the far side of the Ohio River in a different state. Everything else on the page competes with that question. After it is answered, the site becomes an intake tool, and the fields it asks for decide which truck goes out. Design here is less about style than about sorting, speed and a form your estimator would actually recognize.

    Talk to us

    Your first screen has one job: settle the river question

    Before a photo, a badge or a founding year, the visitor needs to know whether their address is one you serve.

    Put the service area at the top in words, not in a map graphic that loads slowly and reads badly on a phone. Name Jefferson County and Louisville Metro, name the outlying counties you take, and say plainly whether you cross into Clark or Floyd County.

    Real place names do the work. St. Matthews, Jeffersontown, Middletown, Prospect, Crescent Hill on the Kentucky side. Jeffersonville, New Albany, Clarksville if you go.

    Then one phone number and one action. A slideshow of roofs is not an action.

    If you do not serve Indiana, say so. A visitor who leaves in four seconds because you were honest costs you nothing. A canceled appointment costs a half day.

    Let a homeowner send the photo of the ceiling stain

    A roofing form should collect what your estimator asks on the phone, and a single photo answers three of those questions at once.

    Ask for the address, whether water is coming in right now, the approximate age of the roof, the covering type if they know it, one story or two, and a photo upload. Nothing else.

    Photo upload is the highest-value field on a roofing form. It separates a repair from a replacement before anybody drives, and it tells you what ladder to bring on a narrow lot.

    Keep the form short. Budget questions belong in the conversation, not the first contact, and they suppress submissions from people who would have signed.

    The auto-reply confirms receipt and names the next step and the time window. Never diagnose from a photo in writing. Say what you would look at in person.

    Crew phone photos, not the design, are what slow a roofing site

    The heaviest thing on most roofing websites is a gallery uploaded straight off somebody's phone.

    A modern phone photo can run several megabytes. Twenty of them on a homepage, opened on cellular in a driveway, is an abandoned visit and a lost call.

    Resize before upload, compress, serve modern image formats, lazy load anything below the fold, and set explicit width and height so the layout does not jump while a thumb is reaching for the call button.

    Then cut scripts. Chat widgets, review carousels, heat mapping and a stack of tags usually cost more speed than every photograph combined.

    Test on a mid-range Android phone on cellular, outdoors. Office wifi on a laptop hides every problem you are trying to find.

    Third shift needs a way to book at 3 a.m. without calling anyone

    Shift work is ordinary in this metro, so a phone-only site loses the people who are awake when your office is not.

    Offer a booking step with real inspection windows, or at minimum a form that promises a specific callback time rather than a vague soon.

    State your hours in plain words, including whether an emergency reaches a person overnight. Vagueness reads as no.

    Make text a first-class channel. Let somebody send a photo by text and get a human reply. Plenty of people would rather do that than talk at eleven at night.

    Overnight inquiries should not sit until Monday. Whatever the site promises, the operation behind it has to keep.

    Say plainly who handles the permit on each side of the river

    Practice differs by jurisdiction, so the site should describe what you do rather than pronounce on what the rules are.

    Louisville Metro and Jefferson County are a merged government. Oldham County, Bullitt County and the Indiana counties are not, and requirements generally differ across them. Worth confirming with the local building department rather than publishing your own version of the code.

    What the page can say is your practice: which jobs you handle permitting on, what you ask the owner to do, and who to call with a question.

    Do the same for insurance work. Describe your process with an adjuster and stop there. Never promise an outcome or characterize what a policy covers.

    Keep license and insurance details for each state you work in on a single page you can text to somebody standing in their yard.

    Publish a range for a replacement or lose the researcher

    A price range with the variables named holds a visitor who would otherwise leave to go find one somewhere else.

    Give a range and explain what moves it: square footage, pitch, number of stories, layers to tear off, decking condition, covering type, and access on a narrow lot in a neighborhood like Germantown or Butchertown where the truck cannot get close.

    Show financing with real terms rather than a lender logo. A homeowner comparing three bids is doing arithmetic, not admiring badges.

    Explain the warranty in one paragraph a homeowner can repeat to a spouse from memory. Anything longer does not survive the conversation.

    Put all of it above the contact form. A PDF download is where price information goes to be ignored.

    Questions we get

    Do we need a new site or can the current one be fixed?
    Often it can be fixed. Speed, form fields, service area language and the emergency path account for most of the lost work, and all four can usually be changed without a rebuild. A rebuild makes sense when the platform itself blocks those fixes.
    What should the contact form ask for a roofing job?
    Address, whether water is entering now, approximate roof age, covering type, stories, and a photo upload. That set lets you triage a repair against a replacement and pick the truck. Everything beyond it costs you submissions.
    Should we show prices on the website?
    Show a range with the variables that move it. It is honest, it filters out jobs you would not want, and it keeps a researching homeowner on your page instead of on somebody else's. Avoid a single precise figure, because roofs are not sold that way.
    How many pages does a roofing site need?
    Fewer than most agencies sell. A strong homepage, a page per covering type, a page for repairs, a page for the emergency path, an honest service area section with a real Indiana page if you cross the river, and proof pages. Publish more only when you can fill them.
    Is a chat widget worth it?
    Only if a person answers it. An unstaffed widget slows the site and frustrates the visitor who tried. In a market with this much odd-hour searching, a fast text-back number is usually the better investment.

    Written by KC Thompson, Morgul Marketing. Updated .

    Talk to us about web design for roofing contractors in Louisville

    Tell us about your business and where your marketing stands. We'll tell you what we'd do first, and what we'd leave alone.

    We won't add you to a mailing list. A person will reply.