The Bulletin Trade guides

No. 007

What a roofing website should include, and the deductible wording to keep off it

Roofing is one of the few trades where common website wording can break the law. Here is what the site should show, and the deductible language several states now prohibit.

A new roof is a big, infrequent purchase, often made under pressure after a storm. A roofing website has one job: make a nervous homeowner feel they can trust you before you ever climb their ladder.

Show that you're local and accountable

After a storm, homeowners get approached by out-of-town crews, and many have been burned. So the first things to establish are that you're real and that you'll be around.

Pages that match how roofs get bought

Explain the process

A roof replacement is unfamiliar to most people. A short, clear sequence lowers the anxiety: inspection, written estimate, permit if required, tear-off, installation, cleanup and final walk-through. Say what's included and how long it usually takes.

Warranties, in plain words

Many roofing jobs carry two warranties: one from the manufacturer on the materials, and one from you on the workmanship. Explain what each covers and for how long. If you hold manufacturer certifications, name them and say what they mean.

Audit your site for deductible wording

Roofing is unusual because some ordinary marketing phrases are illegal in some states. The reason is insurance fraud: a contractor who waives a deductible can inflate the claim to make up for it.

So search your own site, ads and social posts for "free roof," "we'll cover your deductible," "$0 out of pocket" and "we handle your claim." Rules differ by state and change, so check the current law where you work, or ask a local attorney or your state insurance department. It's a one-hour audit that removes a real legal risk.

Photos do the selling

Organize your projects by roof type and job. Before-and-after pairs of the same house from the same angle are the strongest content on the site. See why real photos beat stock.

Mark it up

Use the RoofingContractor type in your schema, with your name, address, phone, hours and service area.

What a good written estimate shows

A page that explains your estimate builds trust before the inspection. Tell customers what a proper estimate includes:

An estimate that spells these out is easy to compare, and customers who compare carefully tend to pick the business that was clearest.

Publish the questions homeowners should ask

It seems backwards, but a checklist called "What to ask any roofing contractor" earns trust. Include questions about licensing, insurance, references, warranties, who does the work and who supervises it. A homeowner who reads it will know you're comfortable being asked.

Timing content

Roofing demand follows the weather. Consider seasonal content: what to check after a storm, what to look for before winter, how heat affects roofing materials. It matches what people search when the weather turns, and it's worth updating each year.

What homeowners say they want

A 2026 survey by Roofr of 292 US homeowners who had hired a roofer in the previous two years gives useful targets:

It's a modest sample from one company's customers, so treat it as a signal and not a rule. But it lines up with the pages above: a clear estimate breakdown, a free-inspection page, and a fast, honest reply.

Questions

Should I put roof prices on the website?

Give ranges by material and roof size, with a note on what changes the price. It filters out browsers and prepares serious buyers.

Do I need a page about storm damage?

Yes, if storms drive your work. It matches what people search when weather hits, and it's a chance to explain your process.

What matters most on a roofing homepage?

The proof that you're local and accountable, and an easy way to book an inspection. See what to put on a contractor's homepage.

Should I list the manufacturers I work with?

If you're authorized or certified, name them and say what the certification means. If not, describe your materials and warranty honestly instead.

Sources

Want a site that launches with answers already written?

Start a project