Roofing Schema Markup
HowTo Schema for Roofers: Mark Up Step-by-Step Guides
Add HowTo structured data to a roofing guide so Google can show its numbered steps, images, and time estimate as a how-to rich result in search.
Roofing-exclusive SEO | valid markup that qualifies for rich results
Free Roofing Schema Audit
Most roofing guides have no HowTo markup, or markup that fails validation. Get a free audit that checks your structured data against the Rich Results Test and lists the fixes.
What Is HowTo Schema?
HowTo schema is structured data markup that tells Google a page contains step-by-step instructions, so the search engine can read each step, its image, and a time estimate. On a roofing guide, the markup wraps the steps you already wrote and labels them as a procedure.
A Markup Type, Not Content
HowTo is a schema.org type added in JSON-LD. It describes content that already exists on the page; it does not write the guide for you.
Built From HowToStep
Each instruction is a HowToStep node inside a step array. The order of the array is the order Google reads the procedure in.
Separate From the Entity
This page covers the markup, not the concept of a roofing entity. For the concept side, see entity SEO for roofers.
Why Add HowTo Schema to a Roofing Guide?
HowTo markup matters because it can turn a plain guide listing into a step-rich result that takes more space and reads as an authoritative answer before the click. The markup signals that the page holds a complete procedure.
More Space in the Result
- A how-to rich result can show numbered steps and a thumbnail, taking more vertical space than a plain listing.
- Visual prominence can lift click-through, with Google citing gains in the range of 20 to 35 percent for well-implemented structured data.
- The steps position the roofing company as the source of the answer before a homeowner opens the page.
Eligibility, Not a Guarantee
- Valid HowTo markup makes a page eligible for the rich result; Google decides when to show it.
- Mobile and desktop can render the result differently, and Google has narrowed how-to display over time.
- See rich results eligibility for what qualifies a page.
Which HowTo Properties Should a Roofing Page Use?
A roofing HowTo needs a name, a step array, and at least two HowToStep entries; image, totalTime, supply, and tool are recommended. Each property maps to something already on the page.
name and step (Required)
The name states the task, such as "How to spot a roof leak". The step array holds the ordered HowToStep nodes that make up the procedure.
image and totalTime
image gives each step a photo from the actual roof. totalTime states the duration in ISO 8601 format, such as PT30M for thirty minutes.
supply and tool
supply lists what gets consumed, such as roofing cement. tool lists what does not get consumed, such as a caulk gun or a ladder.
A HowTo JSON-LD Example for a Roofing Guide
Place a JSON-LD block in the page head or body, with the type set to HowTo and each instruction as a HowToStep. The example below marks up a roof-inspection guide.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to Inspect a Roof for Storm Damage",
"description": "A homeowner walkthrough for checking a roof after a storm.",
"totalTime": "PT30M",
"image": "https://example-roofing.com/images/roof-inspection.jpg",
"supply": [
{ "@type": "HowToSupply", "name": "Notepad" }
],
"tool": [
{ "@type": "HowToTool", "name": "Ladder" },
{ "@type": "HowToTool", "name": "Binoculars" }
],
"step": [
{
"@type": "HowToStep",
"name": "Check from the ground",
"text": "Scan the roof with binoculars for missing, cracked, or lifted shingles.",
"image": "https://example-roofing.com/images/step-ground.jpg",
"url": "https://example-roofing.com/roof-storm-inspection/#step1"
},
{
"@type": "HowToStep",
"name": "Inspect the gutters",
"text": "Look for shingle granules collecting in the gutters, a sign of wear.",
"image": "https://example-roofing.com/images/step-gutters.jpg",
"url": "https://example-roofing.com/roof-storm-inspection/#step2"
},
{
"@type": "HowToStep",
"name": "Check the attic",
"text": "Look for water stains or daylight through the roof deck from inside.",
"image": "https://example-roofing.com/images/step-attic.jpg",
"url": "https://example-roofing.com/roof-storm-inspection/#step3"
}
]
}
</script>Swap the example domain, image URLs, and step text for the real roofing guide. Keep the step order in the markup identical to the order on the page.
Turn Guide Traffic Into Phone Calls
A how-to result can draw the click while the guide still routes the homeowner to a service page and a phone number. We wire the markup and the calls to action together so the education leads to a booked job.
Call Now For PricingOr call +1 272-207-3231
How to Add HowTo Schema Step by Step
Add the markup in a fixed order: write the steps on the page, build the JSON-LD to match, place the script, then validate. The markup must describe what a reader actually sees.
The Four-Step Workflow
- Write the numbered steps in the page content first, with a short heading per step.
- Build a HowTo JSON-LD block where each HowToStep matches a step on the page, in the same order.
- Place the script in the head or near the steps in the body.
- Run the page through the Rich Results Test and fix any flagged property.
Plugin or Manual
On WordPress, a schema plugin can generate the HowTo block from fields you fill in, or you can paste the JSON-LD into a custom HTML block. Either way, the markup must match the visible steps, since invented steps break the rule that markup describes on-page content.
How to Test HowTo Schema in the Rich Results Test
Validate the markup with Google's Rich Results Test and the schema.org validator before and after publishing. A test confirms the parser reads every step and property.
Two Validators to Run
- Paste the URL or the code into Google's Rich Results Test to see detected items and warnings.
- Use the schema.org validator to catch syntax errors the rich-results tool may pass over.
- Confirm every HowToStep is detected and that totalTime parses as a valid duration.
Errors vs Warnings
An error blocks eligibility and must be fixed; a warning flags a missing recommended property, such as image, that improves the result but is not required. Resolve errors first, then add recommended fields where the page supports them.
Which Roofing Topics Suit HowTo Schema?
Use HowTo on educational roofing content that builds trust, not on service or pricing pages. The markup fits a true sequence of steps a homeowner can follow safely.
Good Fits
Roof inspection guides, leak identification tutorials, maintenance checklists, and storm damage assessment steps that a homeowner can do from the ground.
Risky Topics
Complex repair or installation steps that need professional skill, or content that could push a homeowner toward a dangerous DIY attempt on the roof.
Never Use For
Service pages, pricing pages, and emergency repair pages built for immediate lead capture rather than a step-by-step procedure.
How to Keep HowTo Content From Replacing the Sale
Balance the guide so it educates the homeowner while it makes the case for professional work. The markup should strengthen lead generation, not eliminate the demand for service.
Educate Then Hand Off
- Cover the diagnostic steps a homeowner can safely take, such as spotting damage from the ground.
- State plainly where the task crosses into professional territory and why.
- Close the guide with a route to a service page and a call to action.
Mark Up Only the Safe Steps
Keep the HowToStep nodes on the inspection and identification stages. Leave the actual repair to a service description, so the rich result promotes assessment, not a risky climb onto the roof.
Markup Is Cheaper Than Paid Clicks
A how-to result earns clicks at no cost per visit, against 50 to 150 dollars for paid roofing leads. Mark up the guides you already have and keep the click instead of buying it.
Call Now For PricingOr call +1 272-207-3231
Common HowTo Schema Mistakes Roofers Make
Roofing sites lose eligibility through recurring HowTo markup mistakes, each one visible in the Rich Results Test.
Markup and Match Errors
- Adding HowTo to non-sequential content that has no real steps.
- Marking up steps that do not appear in the visible page content.
- Reusing the same HowTo block across several pages, which creates duplicate markup.
Quality and Upkeep Errors
- Overusing HowTo across the site instead of on genuine guides.
- Ignoring Google's structured data quality guidelines.
- Publishing an isolated guide with no supporting cluster around it.
How Does HowTo Fit Other Roofing Schema?
HowTo gains authority when it sits inside a roofing site that also carries the core business and content markup. The types work together rather than in isolation.
Pair With Content Types
A guide can carry a HowTo block and an FAQ schema block, and reference an ImageObject for each step photo.
Sit On a Marked-Up Site
The guide lives on a site that already runs LocalBusiness and Service markup, so the educational content connects to a credited business.
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 HowTo Schema Checklist
Run each roofing guide through this checklist to confirm the HowTo markup is valid and eligible for a rich result.
Type set to HowTo with a clear name?
At least two HowToStep nodes in order?
Every marked-up step visible on the page?
totalTime in valid ISO 8601 format?
A step image for each HowToStep where possible?
Markup limited to safe, educational steps?
Validated in the Rich Results Test with no errors?
No duplicate HowTo block reused across pages?
Frequently Asked Questions
Clear answers about HowTo schema for roofing guides.
What is HowTo schema?
HowTo schema is structured data that marks a page as a set of step-by-step instructions. On a roofing guide it labels each step so Google can read the procedure and may show it as a how-to rich result.
What format should HowTo schema use?
Use JSON-LD, the format Google recommends. Place a script of type application/ld+json with the HowTo object in the page head or near the steps in the body.
What are the required HowTo properties?
A name and a step array are required, with each step a HowToStep. image, totalTime, supply, and tool are recommended and improve how the result can appear.
What is a HowToStep?
A HowToStep is one instruction in the procedure. It carries a name, the step text, and optionally an image and a url that anchors to the step on the page.
How do I write totalTime for a roofing HowTo?
Use ISO 8601 duration format. Thirty minutes is PT30M, one hour is PT1H, and one hour thirty minutes is PT1H30M. The Rich Results Test flags a value it cannot parse.
How do I test HowTo schema?
Paste the URL or the code into Google's Rich Results Test, then confirm with the schema.org validator. Check that every step is detected and resolve any error before adding recommended fields. See rich results eligibility.
Does HowTo schema still produce a rich result?
Google has narrowed how-to display over time, so the visual result is not guaranteed. Valid markup still helps Google understand the page as a procedure, so keep it accurate and test current behavior.
Which roofing pages should use HowTo schema?
Use it on educational guides such as roof inspection, leak identification, and maintenance checklists. Avoid it on service pages, pricing pages, and emergency repair pages built for lead capture.
Should I mark up roof repair steps with HowTo?
Keep the HowToStep nodes on safe diagnostic steps a homeowner can do from the ground. Leave the actual repair to a service description, so the markup does not promote a risky climb onto the roof.
Can HowTo content reduce my roofing leads?
Only if it teaches a homeowner to do the whole job. Keep the guide on assessment, state where professional work is needed, and close with a route to a service page so the content still drives leads.
Can I reuse one HowTo block across pages?
No. Reusing the same HowTo markup on several pages creates duplicate structured data. Each guide needs its own block that matches the steps visible on that specific page.
Can a page have HowTo and FAQ schema together?
Yes, when both reflect real on-page content. A guide can carry a HowTo block for the steps and an FAQ schema block for its questions.
Do I need a plugin to add HowTo schema?
No. A WordPress schema plugin can generate the block from fields, or you can paste the JSON-LD into a custom HTML block. Either way the markup must match the visible steps on the page.
How does HowTo schema relate to entity SEO?
HowTo schema is the markup; entity SEO is the concept of being understood as a known thing. This page covers the markup. For the concept side, see entity SEO for roofers.
Get Your Free Roofing Schema Audit
We'll review the structured data across your roofing guides and service pages, run them through the Rich Results Test, and show where the markup fails or is missing.
What You Get:
- Markup Coverage ReviewA check of which guides and pages carry valid HowTo and related schema.
- Validation ErrorsA list of Rich Results Test errors and warnings on each guide.
More Deliverables
- Step Match CheckWhether the marked-up steps match the steps a reader sees on the page.
- JSON-LD SamplesDrafted HowTo blocks for your highest-value roofing guides.
Claim your free roofing schema audit today. No commitment required.