Common Schema Markup Mistakes
on Roofing Websites
Schema markup is the structured data that tells Google exactly what your business is, where it operates, and what it offers. Most roofing sites either skip it entirely or implement it wrong. Here’s what typically goes wrong, and what correct schema actually looks like.
What Schema Markup Actually Does
Schema markup is a block of structured data, usually JSON-LD, added to a page’s code that explicitly labels information for Google: your business type, service area, phone number, reviews, and more. It doesn’t change what a visitor sees, it changes what Google understands. Without it, Google is left inferring these details from unstructured text, which it does imperfectly at best.
The Most Common Schema Mistakes
Generic “Organization” Instead of “RoofingContractor”
Using the broadest possible schema type wastes the chance to explicitly tell Google you’re a roofing-specific business, weakening the relevance signal for roofing searches.
Copy-Pasted Schema With Wrong Business Info
Schema templates lifted from another site or an old version of your own often carry over an outdated address, phone number, or business name that contradicts what’s visible on the page.
Missing or Broken JSON-LD Syntax
A single misplaced comma or bracket in the JSON-LD block can invalidate the entire schema, meaning Google reads none of it even though the code appears to be present.
No Service Area Defined in Schema
Without an explicit service area property, Google has no structured way to know which towns and cities you actually serve beyond what’s mentioned in body text.
Duplicate or Conflicting Schema Blocks
Multiple plugins or page builders each adding their own schema can result in contradictory or duplicated markup on the same page, confusing rather than clarifying things for Google.
Find Out What Your Schema Is Actually Telling Google
The free audit checks your structured data for errors, gaps, and missed rich result opportunities.
Which Schema Types Roofing Sites Actually Need
LocalBusiness / RoofingContractor
The core identity schema: business name, address, phone, hours, and industry-specific type, placed on the homepage at minimum.
Service
Defines each individual service you offer, roof replacement, repair, storm damage, so Google can associate specific pages with specific offerings.
FAQPage
Marks up visible FAQ content so it’s eligible to appear as an expandable dropdown directly in search results.
Review / AggregateRating
Surfaces your star rating directly in search results, but only when it accurately reflects genuine, visible reviews on the page.
How to Check Your Current Schema
| Tool | What It Checks | What Good Looks Like |
|---|---|---|
| Google Rich Results Test | Validates JSON-LD syntax | No errors, eligible for rich results |
| Schema Markup Validator | Checks schema.org compliance | Correct types, no warnings |
| View Page Source | Confirms JSON-LD is present | ld+json block visible in the code |
| Search Console Enhancements | Shows live rich result eligibility | Items marked “Valid” |
Schema markup won’t make a bad page rank, but broken or missing schema on an otherwise good page leaves rich-result opportunities on the table that competitors with correct markup are already capturing. Star ratings and FAQ dropdowns in the search results directly influence which listing a homeowner clicks, even at the same rank position.
Schema Markup FAQ
Not directly as a ranking factor, but it helps Google understand your content more accurately and makes you eligible for rich results like star ratings and FAQ dropdowns, which improve click-through rate even from the same ranking position.
“Organization” is a generic business type that could describe any company. “RoofingContractor” is a specific schema.org type that tells Google exactly what industry you’re in, which strengthens the relevance signal for roofing-specific searches.
Basic LocalBusiness and FAQPage schema can often be added through SEO plugins or manually with a JSON-LD generator and minimal technical knowledge. More complex or site-wide schema implementations typically benefit from developer review to avoid syntax errors.
No. Your homepage, service pages, and location pages benefit most from LocalBusiness and Service schema. FAQPage schema only belongs on pages with actual visible FAQ content, and Review schema should only be used where genuine reviews are displayed.
Yes. Schema that doesn’t match the visible content on the page, or that’s implemented with broken syntax, can result in rich result eligibility being revoked or, in more serious cases, a manual action from Google for structured data spam.
More from CurbSide Search
Get Your Schema Checked, Free
The free audit reviews your structured data alongside every other ranking factor.
Free audit. No retainer required to start.