Sample layout. Not a real client.
Trade, city: the problem in one line
- Starting point
- Rank grid before any change
- What changed
- The one or two changes that moved it
- Result
- Rank grid after, and the change in calls
A roofing site serves two readers: a homeowner with a leak who wants a phone number, and one planning a replacement who wants evidence. I structure the pages for both and measure what each change does to your rankings.
No long contracts. You talk to Simon.
Map pack: tile roof repair Poway
A
B
C
Scientific SEO
A roofing website that ranks gives each kind of job (leak repair, roof replacement, tile roof work) its own page, and each page answers the search behind it with photos and facts a homeowner can check. It’s ordinary site architecture and on-page SEO, applied to the way people search for a roofer.
Someone in a hurry opens this one, so it has to be short at the top and quick to load. The phone number comes first, tappable, with the hours you answer. Below it go the cities you cover and a few lines on what happens after the call: who comes out, what a temporary fix is, what follows.
On a rainy night the homeowner opens it on a phone, sometimes on a weak signal. Oversized photos are a common reason a roofing page loads slowly, and they are a site speed problem I can fix.
Length is earned here, because this reader will take their time and compare you with other bidders. They want to know what comes off and what goes on, how the property is protected, what the written estimate includes and who will be on the roof. I leave price figures and warranty terms off the page unless you give me exact wording you stand behind, because a number on a website becomes a promise.
Tile roofs are common in this county and the questions about them are specific, which earns the material a page to itself. Often the tile is fine and the underlayment beneath it has failed, which confuses homeowners: the roof looks intact and the ceiling is wet. A page that explains this and shows the layer with the tile off, and that describes the difference between a spot repair and lifting and resetting a section, will match searches a general roofing page doesn’t.
Photos of real jobs are the strongest material a roofer has, and a plain gallery wastes them. A grid of images gives Google almost no text to read. A project page gives each job a few sentences (the city, the roof type, the problem found, the work done) with before and after photos, descriptive file names and alt text, the short description attached to each image. Each one links to the matching service page and to the service area page for that city. A flat roof in North Park and a tile reset in Carlsbad become two pages that can each match a search.
A roofing site also has to answer the worry left by door-to-door roofers: is this a real local company? Show your contractor license number so a homeowner can look it up with the state license board, a local phone number, the area you work in and the people who will show up. The same facts go into schema markup, code that states them in a form search engines read directly. An insurance page fits here if it’s modest: explain how you document damage, and leave coverage to the insurer.
I publish one change at a time and check the rankings about two weeks later, alongside calls and estimate requests. I can’t promise a new page will rank. If it doesn’t move the search it was written for, I rework it before adding more pages.
Every engagement starts and ends with the same measurement.
Sample layout. Not a real client.
Only for cities where you can say something true and specific. A Poway page that shows Poway jobs, names the neighborhoods and describes the roofs you see there can rank. Thirty pages with the city name swapped won't help and can hurt. I start with cities where the rank grid shows a gap and you have real projects to show, and each project page then links to the matching service page and to the service area page for its city.
List them if you'll honor them. If not, explain what drives a roof's cost (size, pitch, material, access, and what is found under the old roof). That answers honestly and gives a homeowner a reason to request an estimate.
Usually not at the top of the page. Large video files and sliders are heavy, and a homeowner with a leak won't wait for them on a phone. Put one compressed photo and the phone number first. Drone footage of finished roofs is good evidence lower down the replacement page or on project pages, where the reader has time.
It depends on your contract, and it's worth checking before any SEO work starts. Find out who holds the domain registration, who controls the hosting, and whether the phone number on the site is yours or a tracking number the vendor keeps. If those aren't in your name, work done on the site can leave with the vendor.
I need your site address and the cities you serve. From those I check how the site ranks for repair, replacement and tile searches before recommending a change.
Prefer to talk? Call (619) 675-7678, 9am to 6pm.