Roofing Schema Markup
RoofingContractor Schema for Roofing Sites
Add the RoofingContractor structured-data type to a roofing site so search engines read the business as a roofing company, not a generic local business.
Roofing-exclusive SEO | structured data built for roofers
Free Roofing Schema Audit
Most roofing sites run generic plugin schema or none at all. Get a free audit that checks the RoofingContractor markup, its properties, and how it tests in the Rich Results Test.
What Is RoofingContractor Schema?
RoofingContractor schema is a structured-data type from Schema.org that labels a business as a roofing company in machine-readable code, so search engines read what the company does, where it works, and how to trust it.
A Named Schema.org Type
RoofingContractor is a defined type at schema.org/RoofingContractor. You set it as the @type in the JSON-LD that describes the roofing business.
A Subtype of LocalBusiness
It sits under LocalBusiness, so it inherits address, phone, hours, and rating, then adds the roofing label on top. See LocalBusiness schema.
Markup, Not a Concept
This page covers the code. For the idea of a business as a search entity, see entity SEO for roofers.
Why Use RoofingContractor Instead of LocalBusiness?
Use RoofingContractor because it states the trade, while LocalBusiness only states that a local company exists. The specific type removes the guesswork about what the business does.
A Specific Type Says More
- LocalBusiness marks a local company without naming the trade.
- RoofingContractor names the trade, so search engines do not have to infer it from page text alone.
- The narrower type lines up the business with roofing queries and roofing-related entities.
It Inherits Every LocalBusiness Field
- RoofingContractor keeps name, address, telephone, openingHours, and aggregateRating.
- Switching the type costs nothing in lost properties, since it is a subtype.
- Use it as the single business node on the home page or the about page.
Which Properties Go on RoofingContractor Markup?
Fill the core identity fields first: name, url, telephone, address, image, and the areaServed and aggregateRating fields that carry the most weight for a roofer.
Identity Fields
name, url, telephone, and image identify the roofing business. They should match the name and number shown on the site and the Google profile.
Location Fields
address holds the PostalAddress, and areaServed lists the cities and regions the roofer covers. See the areaServed property.
Trust Fields
aggregateRating and review carry the star data. sameAs links the official profiles. See aggregateRating schema.
Turn Markup Into Phone Calls
A roofing site can rank yet read as a generic business to search engines. We add the RoofingContractor type and its properties so the listing reads as a roofer and earns the call.
Call Now For PricingOr call +1 272-207-3231
A RoofingContractor JSON-LD Example
Place one JSON-LD block in the page head, set @type to RoofingContractor, and fill the identity, location, and trust fields. The markup below is a working starting point for a roofing home page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "RoofingContractor",
"@id": "https://example-roofing.com/#business",
"name": "Summit Roofing Co.",
"url": "https://example-roofing.com/",
"telephone": "+1-555-555-0142",
"image": "https://example-roofing.com/images/crew.jpg",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "120 Market Street",
"addressLocality": "Springfield",
"addressRegion": "OH",
"postalCode": "45502",
"addressCountry": "US"
},
"areaServed": [
{ "@type": "City", "name": "Springfield" },
{ "@type": "City", "name": "Dayton" }
],
"openingHours": "Mo-Fr 07:00-18:00",
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.9",
"reviewCount": "187"
},
"sameAs": [
"https://www.facebook.com/summitroofing",
"https://www.google.com/maps/place/summitroofing"
]
}
</script>What Each Block Does
- @type sets the business as a roofing contractor.
- @id gives the node a stable identifier other markup can reference.
- address, areaServed, and aggregateRating fill the location and trust fields.
Keep the Data Honest
- The name, phone, and rating must match what shows on the page and the profile.
- The aggregateRating should reflect reviews the site can display.
- Use one business node, not a duplicate on every template.
How Do You Add RoofingContractor Schema to a Site?
Add it as a JSON-LD script in the page head, either through a plugin field, a theme setting, or a hand-placed script. JSON-LD is the format Google recommends for structured data.
Three Ways to Place It
- A schema plugin that lets you set the business type and fields.
- A theme or builder option that outputs a JSON-LD block site-wide.
- A hand-written script in the head template, edited directly.
Place It Once, Cleanly
- Output the business node on the home page and reference it by @id elsewhere.
- Confirm a plugin is not already emitting a second LocalBusiness block.
- Use JSON-LD, not Microdata, so the markup stays separate from the visible HTML.
How Do You Test RoofingContractor Markup?
Test it in the Rich Results Test and the Schema Markup Validator, which parse the page and list every type and property they detect. Fix any error or warning before moving on.
Run the URL or the Code
Paste the live URL or the raw HTML into Google's Rich Results Test. It reports the detected types and any blocking error.
Read Errors and Warnings
An error blocks a feature; a warning flags a missing recommended field. Clear errors first, then add the recommended fields.
Confirm a Single Node
The validator should show one business node, not two. See rich results eligibility.
How Does RoofingContractor Connect to Other Schema?
RoofingContractor is the parent business node that other roofing markup attaches to, through makesOffer, review, and sameAs. The type rarely stands alone on a full site.
Services and Offers
- Each roofing service can carry its own Service markup, linked back to the business.
- The makesOffer field can point to repair, replacement, and inspection offers.
- See Service schema for the per-service setup.
Reviews and Profiles
- review holds individual customer reviews on the business node.
- sameAs links the official profiles that confirm the same business. See sameAs entity links.
- Reviews use Review schema on the nested nodes.
Organic Clicks Cost Less Than Paid Ones
A click earned from a strong organic listing costs nothing per visit, against 50 to 150 dollars for paid roofing leads. Mark up the business correctly and earn the listing instead of buying it.
Call Now For PricingOr call +1 272-207-3231
Common RoofingContractor Schema Mistakes
Roofing sites break their markup through six recurring schema mistakes, each one visible in the Rich Results Test and fixable in the page head.
Conflict and Syntax Errors
- Two plugins both emit a business node, so the page carries duplicate, conflicting markup.
- A broken comma or bracket in the JSON-LD stops the parser from reading the block.
- A generic LocalBusiness type is left in place instead of RoofingContractor.
Accuracy and Upkeep Errors
- An aggregateRating that no review on the site supports.
- An address or areaServed that does not match the real service area.
- Outdated markup with an old phone number or a service the company no longer offers.
What Results Can RoofingContractor Schema Support?
Schema makes the business eligible for richer listings, though it does not force them. Google reports that structured data helps it understand a page, and eligibility for rich results follows correct markup.
What the Markup Enables
- Clearer entity understanding, so search engines read the business as a roofer.
- Eligibility for star ratings in the listing where reviews support it.
- Consistent business data that lines up the site with the Google profile.
What It Does Not Do
- Schema is not a direct ranking factor, per Google's own guidance.
- Markup alone does not guarantee a rich result; Google decides when to show one.
- Reported click-through gains from rich snippets vary by site and query, so treat figures as a range.
From the Case Studies
Results You Can Verify
No stock photos and no first names without a company. Numbers from named clients, with the charts published.
A brand-new roofing company taken from zero to 9.61K Google impressions in its first 2 months.
Alpha Holistic Roofing
Launch-phase local SEO
Read the case studyA site that flatlined at zero impressions for two months, standing back up at 18.6K impressions in six.
RoofingPros Milwaukee
Recovery and rebuild
Read the case studyThe Roofing Schema Markup Checklist
Run the RoofingContractor markup through this checklist before you submit the page for indexing.
@type set to RoofingContractor, not generic LocalBusiness?
name, url, telephone, and image all present?
address as a PostalAddress with full fields?
areaServed lists the real cities and regions served?
aggregateRating backed by reviews the page can show?
Only one business node, with no duplicate from a plugin?
JSON-LD valid, with no broken comma or bracket?
Page passes the Rich Results Test with no errors?
Frequently Asked Questions
Clear answers about RoofingContractor schema for roofing sites.
What is RoofingContractor schema?
RoofingContractor schema is a structured-data type from Schema.org that marks a business as a roofing company. You set it as the @type in JSON-LD so search engines read the trade, not just a generic local business.
Is RoofingContractor a real Schema.org type?
Yes. RoofingContractor is a defined type at schema.org/RoofingContractor. It is one of the HomeAndConstructionBusiness subtypes under LocalBusiness, so it is part of the standard vocabulary search engines read.
What is the difference between RoofingContractor and LocalBusiness?
LocalBusiness marks a local company without naming the trade. RoofingContractor is a subtype that names roofing specifically, while inheriting every LocalBusiness field. See LocalBusiness schema.
Which properties are required on RoofingContractor markup?
Schema.org sets no hard required fields, but Google expects name, address, and telephone at minimum. Add url, image, areaServed, and aggregateRating so the markup is complete and useful for a roofer.
Should I use JSON-LD or Microdata for roofing schema?
Use JSON-LD. Google recommends it because the markup sits in a single script block, separate from the visible HTML, which makes it easier to edit and validate than Microdata woven through the page.
Where do I put the RoofingContractor JSON-LD?
Place the script in the page head, or anywhere in the HTML body. Google reads JSON-LD from either spot. Output the business node once, on the home page, and reference it by @id on other pages.
How do I test RoofingContractor schema?
Run the URL or the raw code through Google's Rich Results Test and the Schema Markup Validator. Both list every detected type and property. Clear any error first, then add the recommended fields shown as warnings.
Does RoofingContractor schema improve rankings?
Schema is not a direct ranking factor, per Google. It helps search engines understand the business and can make the listing eligible for rich features such as star ratings, which can lift click-through.
Can I add aggregateRating to RoofingContractor markup?
Yes. aggregateRating holds the average score and review count on the business node. Only include figures the page can display. See aggregateRating schema.
How do I mark up service areas for a roofer?
Use the areaServed property with City or AdministrativeArea entries that list the towns and regions the roofer covers. Keep them matched to the real service area. See the areaServed property.
Can I link the markup to other roofing schema?
Yes. The business node can carry makesOffer for services and review for customer reviews, and link profiles through sameAs. See Service schema for the per-service setup.
Why does my roofing schema show duplicate markup?
A theme and a plugin both emit a business node, so the page carries two. Pick one source, disable the other, and confirm the validator shows a single RoofingContractor node.
Does every roofing page need RoofingContractor schema?
No. Define the business node once and reference it by @id elsewhere. Service pages can carry Service markup, and review pages can carry Review markup, all tied back to the one business node.
How often should I update the schema markup?
Update it when the phone number, address, services, or service area change, and refresh the aggregateRating as reviews accumulate. Outdated markup that no longer matches the business can mislead search engines.
Get Your Free Roofing Schema Audit
We'll check the structured data across your roofing site, confirm the RoofingContractor type and its properties, and run the page through the Rich Results Test to show what is missing.
What You Get:
- Type and Property ReviewA check of the @type, the identity fields, areaServed, and aggregateRating on each key page.
- Duplicate Node ScanA list of pages where a theme and a plugin both emit a business node.
More Deliverables
- Validation ReportThe errors and warnings the Rich Results Test returns on your key roofing pages.
- JSON-LD SamplesDrafted RoofingContractor markup for your home page and top service pages.
Claim your free roofing schema audit today. No commitment required.