Key takeaways
- A roofing area page earns its rank with proof from that town: finished roofs, the permit office you deal with, reviews from neighbors.
- Choose towns by signed roofs and drive time, not by where the last storm passed.
- Never publish a page for every town a hail path crossed. That is a doorway page, and Google treats it as spam.
- Ten strong area pages beat fifty thin ones.
Service area pages for a roofing company are website pages for each town where you want more roofs, built on the work you have done there. They reach homeowners in towns where your Google profile is too far away to show in Maps. A page earns its place with local proof: finished roofs, local reviews and what is different about roofs in that town.
What service-area pages are
A service-area page is your website's answer to a homeowner who types "roof replacement" with their town's name, or who searches from that town and scrolls past the Map Pack. Your profile is anchored to where you verified it (Google's service-area rules). Your website is not, which makes it the main way a roofer reaches the far side of its territory.
These pages also do a job the profile cannot. A homeowner choosing between three roofers for a full replacement wants to know you have worked on houses like theirs, nearby. A page showing six finished roofs in their town, with the shingle line and color on each, answers that before they call.
How service-area pages fit your site
- Homepage Who you are and where you work
- Service pages One page for each service you sell
- Area pages Real jobs, reviews and photos from that area
What goes on each page
Build each page in this order, and leave out any section you cannot fill with something true.
- A plain heading and opening. Say what you do in that town in one or two sentences, with the town name used once or twice, naturally.
- Roofs you finished there. Three to six projects with photos: the type of house, what you found at the inspection, what you installed, and whether it was a storm claim or a planned replacement. This section carries the page.
- What roofs there tend to need. The housing stock is the local knowledge only a working roofer has: subdivisions where original roofs are reaching replacement age, streets with heavy tree cover that clog gutters, older homes with more than one layer to tear off.
- Permits and rules you deal with. Which building department issues the permit, whether a final inspection is required, and any homeowner association that approves shingle colors. Only state what you have confirmed on real jobs.
- Storms you responded to. Name the event by month and the work it produced, without inflating it. Dated, factual notes age better than "storm damage experts".
- Reviews from that town. Quote or link reviews from homeowners there, with their permission, and only real ones.
- How fast you can inspect. Your real turnaround for an inspection in that town, and whether that changes during storm season.
- One clear next step. A call button and the short inspection request form, the same as on your service pages.
Link each area page to the matching service pages, and link back from them, so a homeowner can move between "what you do" and "where you do it".
Which areas to target first
Start with the towns that already produce signed roofs you want more of, within a drive your crews and project managers can make without losing a day. Score each candidate on a few questions you can answer from JobNimbus or AccuLynx.
Example, with hypothetical towns. A roofer looks at three towns from last season:
| Town A | Town B | Town C | |
|---|---|---|---|
| Signed roofs last two seasons | Several, mostly replacements | A few repairs | None |
| Drive from the shop | 25 minutes | 15 minutes | 50 minutes |
| Housing | 1990s subdivisions reaching replacement age | Mixed, mostly newer | Older homes |
| Finished projects with photos | Yes | Some | No |
| Build a page now? | Yes, first | Yes, after Town A | Not yet |
Town C may look tempting after a storm, but with no finished roofs there you have nothing true to put on the page. Win a few jobs there first, photograph them, then build it.
The Google Maps ranking guide explains why towns close to your base often need no page at all to rank.
Mistakes that create thin pages
Thin pages are the reason many roofing sites rank worse after adding area pages, not better.
- The same text with a new town name. Google's guidance on helpful content asks whether a page was made for people or for search engines (helpful content). A swapped name fails that test.
- A page for every town a hail path crossed. Pages built only to catch searches in places you do not really serve are doorway pages under Google's spam policies (spam policies).
- Stock photos of roofs that are not yours. Homeowners recognize them, and so do competitors.
- Pages that promise a response time you cannot keep. If storm week means a two-week wait for inspections, say so.
- Orphan pages. An area page nothing links to rarely ranks. Link it from the service pages and your service-area list.
How VETS Growth Marketing helps
We pick your first towns from your own CRM data, then build each page around the roofs you finished there, with a date for each one. The site and every page stay yours. We report booked inspections from each town, so you can see which pages earn their place. Book a growth consultation and we will show you which towns to start with.
Sources
- Spam policies for Google web search, Google Search Central
- Creating helpful, reliable, people-first content, Google Search Central
- Manage your service areas for service-area & hybrid businesses, Google Business Profile Help