Key takeaways
- An audit should end in a short, ordered list of fixes with owners and dates.
- You can check most of it yourself in an hour with Search Console, PageSpeed Insights and your phone.
- Submit your own inspection form: a lead that never reaches the CRM is the most expensive problem on the list.
- Roofing sites most often suffer from heavy gallery photos, stale storm pages and copied area pages.
An SEO audit for a roofing company website checks whether Google can find your pages, whether homeowners on a phone can use them, and whether your profile and tracking turn searches into booked inspections. You can run a useful version yourself in about an hour, which also lets you check what a provider tells you.
What an audit checks
A good audit answers a handful of plain questions about the site, the profile and the path from a search to your CRM.
| Area | The question | How to check |
|---|---|---|
| Indexing | Can Google see your service, storm and area pages? | Search Console's page indexing report |
| Search terms | Which searches already show your site? | Search Console's performance report |
| Speed | Do pages load fast on a phone? | PageSpeed Insights and Core Web Vitals |
| Pages | Is there a page for repair, replacement, storm and insurance, and gutters? | Your own site menu |
| Profile | Are the category, services and service areas right? | Your Google Business Profile |
| Lead path | Does a form or call reach the CRM, with its source? | A test submission |
Each area gets a verdict: fine, fix now or fix later. That verdict is the part worth paying for.
What an audit checks
Google profile
- Categories and services
- Service area and hidden address
- Photos and review replies
Website
- Speed on a phone
- A page for each service
- Titles and descriptions
Reviews
- How recent they are
- Whether each one is answered
Listings
- Name and phone consistent
- Duplicate listings
Tracking
- Calls tracked by source
- Forms tracked to bookings
Run a quick self-audit
Set aside an hour, open a laptop and keep your phone next to it.
- Search like a homeowner (10 minutes). On your phone, in a private browser tab, search "roof repair" and "roof replacement" with the name of a town you serve. Note where you appear on Maps and below it, and which page of yours shows.
- Check indexing (10 minutes). In Search Console (Search Console), open the page indexing report. Look for your service, storm and area pages. A page that is not indexed cannot rank.
- Read your search terms (10 minutes). In the performance report, sort queries by impressions. Do "roof replacement", "roof leak repair" and "hail damage" appear? If you only show for your company name, the pages are not doing their job.
- Test speed on the heaviest page (10 minutes). Run your project gallery or replacement page through PageSpeed Insights (PageSpeed Insights). Galleries of full-size drone and job photos are the usual reason roofing pages load slowly on phones (Core Web Vitals).
- Submit your own inspection request (10 minutes). Fill in the form as a homeowner with a leak. Time how long until it shows up in JobNimbus or AccuLynx, whether the source is recorded, and whether anyone calls you back.
- Check the profile (10 minutes). Confirm Roofing contractor is primary, the address is hidden, the service areas are towns you serve, and the website link goes to a working page. Look for a second listing under your name from an old office or a former partner, which breaks Google's guidelines (guidelines).
Write each finding down with a verdict. That list is your audit.
Most common problems for roofing companies
The same handful of problems shows up on roofing sites again and again, and most trace back to how storm seasons and lead vendors shape the business.
- A storm page frozen in time. A page about a hailstorm from seasons ago, still promising this week's inspections, tells homeowners nobody is minding the site.
- Photo galleries that drag down mobile speed. Hundreds of uncompressed images from drones and phones on one page.
- Area pages copied from one template, with only the town name changed.
- No storm and insurance page at all, even though insurance work may be a large share of signed roofs.
- A site or domain the owner does not control, built by a lead vendor or a former agency.
- Forms that go to an inbox nobody watches during the busiest weeks of the year.
- Duplicate or abandoned profiles from a past sales office or a canvassing partner.
What to do after the audit
Turn the findings into five fixes, in order, each with an owner and a date. Put anything that stops a lead reaching the CRM first, because it costs signed roofs today. Indexing and profile errors come next, then speed, then new pages.
Schedule the work so it finishes before spring storms. Then re-run the six checks after each change so you know it held. The local SEO checklist for roofers covers the ongoing work, and the roofing website conversion checklist helps once visitors arrive.
How VETS Growth Marketing helps
We run this audit live at the start of every growth consultation, with you watching, so nothing depends on taking our word for it. The five fixes become a dated project in accounts you own, and we report the result in booked inspections and signed roofs. Book a growth consultation and bring your Search Console login if you have one.
Sources
- Google Search Console, Google
- PageSpeed Insights, Google
- Understanding Core Web Vitals and Google search results, Google Search Central
- Guidelines for representing your business on Google, Google Business Profile Help