Roofing Schema Markup
Review Schema for Roofing Websites
Add Review structured data to a roofing page so each customer review carries machine-readable rating, author, and date that a search engine can read and may show as a rich result.
Roofing-exclusive SEO | star ratings in search listings
Free Roofing Schema Audit
Most roofing sites show reviews to visitors but send no Review markup to search engines. Get a free audit that checks your structured data and flags pages eligible for star rich results.
What Is Review Schema?
Review schema is a block of structured data that marks up a single customer review on a page, so a search engine can read its rating, author, and text in a machine-readable form. You add it as JSON-LD in the page, separate from the visible review a homeowner sees.
It Marks Up One Review
A Review object describes a single testimonial: one author, one rating, one piece of text. It is not the site-wide average.
It Is the Review Type
The schema.org Review type carries the properties Google reads. It sits inside the thing being reviewed, such as a roofing service or the business.
Separate From the Concept
This page covers the markup, not the entity idea behind it. For the concept side see entity SEO for roofers.
Why Add Review Schema to a Roofing Site?
Add Review schema because the markup makes a star rating eligible to appear in the search listing, where it influences the click before a homeowner reads anything else.
Stars Affect the Click, Not the Rank
- Review schema is a trust signal, not a ranking factor. Google does not rank a page higher for having it.
- Roofing is a high-cost decision, often 15,000 to 30,000 dollars, so visible trust carries weight at the search result.
- A starred listing can lift click-through against a plain listing at the same position. Google reports rich results as a common cause of higher click-through.
It Pairs With Aggregate Rating
- A single Review marks up one testimonial; an AggregateRating marks up the overall average and count.
- Most roofing pages use the two together: individual reviews plus the summary rating.
- Both must reflect reviews that are genuinely on the page. See the schema hub for the full set.
Which Properties Does Review Schema Use?
A Review object uses five core properties: itemReviewed, author, reviewRating, reviewBody, and datePublished. The reviewRating holds its own ratingValue, bestRating, and worstRating inside it.
itemReviewed and author
itemReviewed names the thing being reviewed, such as a roofing service or the business. author names the customer who wrote the review.
reviewRating
A nested Rating object. ratingValue is the score, such as 5. bestRating and worstRating set the scale, usually 5 and 1.
reviewBody and datePublished
reviewBody holds the review text. datePublished records when the customer left it, in YYYY-MM-DD form.
A JSON-LD Example for a Roofing Review
Place the markup in a JSON-LD script in the page, with the Review nested inside the roofing service it describes. This example marks up one 5-star customer review of a roof replacement.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Service",
"name": "Roof Replacement",
"provider": {
"@type": "RoofingContractor",
"name": "Summit Roofing Co."
},
"review": {
"@type": "Review",
"author": {
"@type": "Person",
"name": "Mike T."
},
"datePublished": "2026-03-14",
"reviewBody": "Summit replaced our storm-damaged roof in two days and handled the insurance paperwork. The crew was on time and tidy.",
"reviewRating": {
"@type": "Rating",
"ratingValue": "5",
"bestRating": "5",
"worstRating": "1"
}
}
}
</script>Read the Structure
- The outer object is the Service being reviewed; the Review sits inside its review property.
- The author Person names the real customer, not the business owner.
- The reviewRating is its own Rating object with the score and the scale.
Match It to the Page
- The reviewBody text must be the same review a visitor can read on the page.
- Mark up the thing being reviewed with the right type, such as Service schema or RoofingContractor schema.
- Keep one Review object per testimonial, or list several.
Turn Reviews Into Star Listings
A roofing page can hold real reviews yet send no markup to search engines, so the listing stays plain. We add valid Review and AggregateRating schema across the site so the stars can show.
Call Now For PricingOr call +1 272-207-3231
How to Add Review Schema to a Roofing Page
Add the markup in four steps: write the JSON-LD, place it in the page that shows the review, attach it to the thing reviewed, then validate it. Lead with JSON-LD, the format Google recommends.
The Four Steps
- Write a Review object with author, reviewRating, reviewBody, and datePublished.
- Nest it inside the itemReviewed, such as the service or the business.
- Add the script to the same page where the review is visible to a visitor.
- Validate the result before you publish.
Where to Place It
JSON-LD goes in a script tag, usually in the head or near the end of the body. A page builder, an SEO plugin, or a custom HTML block can hold it. The review it describes must also appear on the page for a homeowner to read.
How to Test Review Schema in the Rich Results Test
Test the markup with Google's Rich Results Test, which reports whether the page qualifies for a review rich result and lists any errors. Run it on every page that carries the schema.
Run the Rich Results Test
Paste the URL or the code into Google's Rich Results Test. It shows whether the Review qualifies and flags missing or invalid fields.
Check the Schema.org Validator
The Schema Markup Validator checks the JSON-LD syntax itself. Use it to confirm the structure is well formed before the eligibility test.
Watch Search Console
After publishing, the Enhancements report in Search Console reports valid and invalid review markup across the site over time.
Review Schema vs AggregateRating Schema
The two are different objects: Review marks up one customer testimonial, while AggregateRating marks up the overall score and the total count. A roofing page often carries both.
Review Is the Individual
A Review object holds one author, one rating, and one piece of text. Use it to mark up each testimonial a homeowner can read on the page.
AggregateRating Is the Summary
An AggregateRating holds the average score and the review count for the whole business or service. See AggregateRating schema for that side.
What Are the Rules for Honest Review Markup?
Mark up only reviews that are genuine, visible on the page, and written by real customers. Google can apply a manual action against a site that marks up reviews it does not actually display.
What the Markup Must Reflect
- The review must be visible on the same page that carries the markup.
- The rating in the schema must match the rating the customer gave.
- The author must be the real customer, not the company.
What Triggers a Penalty
- Self-reviews written by the owner or staff and marked up as customer reviews.
- Inflated ratings that show more stars than the real reviews support.
- Marking up a rating on a page that displays no review at all.
Organic Clicks Cost Less Than Paid Ones
A click earned from a starred organic listing costs nothing per visit, against 50 to 150 dollars for paid roofing leads. Add valid Review markup and keep the click instead of buying it.
Call Now For PricingOr call +1 272-207-3231
Common Review Schema Mistakes Roofers Make
Roofing sites lose review rich results through six recurring markup mistakes, each one fixable in the structured data.
Markup and Syntax Errors
- Invalid JSON-LD, such as a missing comma or bracket, which stops the page from parsing.
- A reviewRating with no ratingValue, or a value outside the stated scale.
- No itemReviewed, so the review has nothing to attach to.
Trust and Upkeep Errors
- Marking up reviews that are not visible on the page.
- Self-reviews from the owner presented as customer reviews.
- Stale markup that does not update as new reviews come in.
How Should Multi-Location Roofers Mark Up Reviews?
For a roofer serving several cities, each location page should carry its own reviews and its own markup, rather than reusing a single company-wide rating.
Location-Specific Reviews
- Attach reviews from customers in that city to that location page.
- Keep the reviewBody and author tied to the work done in that area.
- Avoid pasting the same set of reviews onto every city page.
Align With the Business Markup
Keep the review markup consistent with the rest of the page's structured data, such as the LocalBusiness schema and the location data. Consistent data across the page strengthens local relevance.
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 Review Schema Checklist
Run each roofing page through this checklist to confirm the Review markup is valid and honest before you publish.
Review written as valid JSON-LD?
Nested inside the correct itemReviewed?
reviewRating with ratingValue and scale set?
author set to the real customer?
reviewBody matches the visible review text?
datePublished in YYYY-MM-DD form?
Review visible on the same page?
Validated in the Rich Results Test?
Frequently Asked Questions
Clear answers about Review schema for roofing pages.
What is Review schema for a roofing site?
Review schema is structured data that marks up a single customer review on a roofing page. It tells a search engine the rating, the author, the text, and the date in a machine-readable form.
What format should I use for Review schema?
Use JSON-LD. Google recommends JSON-LD in a script tag for review markup. It keeps the structured data separate from the visible HTML and is the simplest format to add and validate.
Which properties does a Review object need?
A Review object needs an author, a reviewRating with a ratingValue, and an itemReviewed. A reviewBody and a datePublished add the text and the date that make the markup complete.
What is the difference between Review and AggregateRating?
A Review marks up one testimonial with one author and one rating. An AggregateRating marks up the overall average and the total count. Roofing pages often carry both.
Does Review schema improve my roofing rankings?
No. Review schema is not a ranking factor. It can make a star rating eligible to show in the listing, which may lift click-through. The click-through, not the markup itself, is what can help over time.
Can I mark up reviews from Google or Facebook?
You can mark up reviews you display on your own page, but Google does not show review rich results for reviews collected from a third-party site about that same business. Mark up first-party reviews the page actually shows.
How do I test Review schema?
Run the page through Google's Rich Results Test to confirm eligibility, then use the Schema Markup Validator to check the JSON-LD syntax. After publishing, watch the Enhancements report in Search Console.
Will star ratings always show in search results?
No. Valid markup makes the page eligible, but Google decides when to show stars. The rich result is not guaranteed even when the schema passes the test. See rich results eligibility.
Can I mark up my own reviews of my roofing business?
No. Self-reviews written by the owner or staff are not allowed. The author must be a real customer. Marking up self-reviews as customer reviews can trigger a manual action against the site.
What happens if I fake the rating in my schema?
Faking or inflating a rating breaks Google's structured data guidelines. It can lead to a manual action that removes the site's rich results until the markup is corrected. The rating must match real reviews.
Where should the Review markup go on the page?
Put the JSON-LD script on the same page where the review is visible to a visitor, usually in the head or near the end of the body. The location in the page does not change how Google reads the markup.
How should multi-location roofers handle review markup?
Give each location page its own reviews and its own markup rather than one company-wide rating. Keep it consistent with the page's LocalBusiness schema and location data.
Do I need a plugin to add Review schema?
No. You can paste the JSON-LD into a custom HTML block or the page head. An SEO plugin or a page builder can manage it for you, but the markup is plain JSON-LD either way.
How often should I update my Review markup?
Update the markup as new reviews come in and old ones change, so the schema keeps matching what the page displays. Stale markup that no longer reflects the visible reviews drifts out of compliance.
Get Your Free Roofing Schema Audit
We'll check the structured data across your roofing pages, confirm whether your reviews carry valid markup, and compare your listings to your top 3 local competitors.
What You Get:
- Schema ValidationA Rich Results Test on each key page to confirm review markup eligibility.
- Missing Markup ScanA list of pages that show reviews but send no Review schema to search engines.
More Deliverables
- Guideline CheckWhether any markup risks a manual action for self-reviews or hidden reviews.
- JSON-LD SamplesDrafted Review and AggregateRating markup for your highest-value roofing pages.
Claim your free roofing schema audit today. No commitment required.