knowsAbout Property: Declare Your Roofing Expertise in Schema
Roofing Schema Markup

knowsAbout: Declare Your Roofing Expertise in Schema

Add the knowsAbout property to your Organization schema so search engines and AI systems read the exact roofing topics your business is expert in.

Roofing-exclusive SEO | entity signals that AI search can read
knowsAbout schema property

Free Roofing Schema Audit

Most roofing sites ship Organization schema with no knowsAbout array at all. Get a free audit that checks your structured data and drafts the topic list your markup is missing.

What Is the knowsAbout Property?

The knowsAbout property is a Schema.org attribute that lists the topics an Organization or Person is expert in, written as a machine-readable array inside the schema markup. On a roofing site it tells search engines which roofing subjects your business covers.

Where It Lives

knowsAbout sits inside the Organization or Person node of your JSON-LD, alongside name, url, and sameAs.

What It Accepts

The value can be a plain text string, a URL to a relevant resource, or a structured Thing object. Most roofing sites use plain text topics.

It Markup, Not the Concept

This page covers how to write the property. For the entity idea behind it, see entity SEO for roofers.

Why Add knowsAbout to a Roofing Site?

knowsAbout matters because it connects your business entity to specific roofing topics in a way search engines and AI systems can parse directly. The property signals relevance; it does not by itself prove expertise.

Entity Association

  • It helps Google link your Knowledge Graph entity to roofing-specific subjects.
  • The array names topics in terms a homeowner would search.
  • It works with sameAs to confirm which entity the topics belong to.

AI Search Visibility

  • AI search features pull from entity data when generating answers.
  • Clear topic declarations raise the chance of a citation in an AI overview.
  • A site with no entity signals can be left out regardless of its rankings.

Topic Reinforcement

  • Each declared topic should map to a real page on the site.
  • The array reinforces the relationship between service pages and content.
  • See on-page SEO for roofers for the page side.

A knowsAbout JSON-LD Example for Roofers

Add the knowsAbout array to the Organization node of your JSON-LD, with sameAs links and a short description beside it. The block below is a working pattern you can adapt with your own company name and topics.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Roofing Company Name",
  "url": "https://yourdomain.com",
  "logo": "https://yourdomain.com/logo.png",
  "description": "Licensed roofing contractor for roof repair, replacement, and storm damage restoration.",
  "sameAs": [
    "https://www.google.com/maps?cid=YOUR_GBP_ID",
    "https://www.linkedin.com/company/your-company",
    "https://www.bbb.org/your-listing"
  ],
  "knowsAbout": [
    "roof repair",
    "roof replacement",
    "storm damage roofing",
    "emergency roof repair",
    "asphalt shingles",
    "metal roofing",
    "flat roofing",
    "roof inspection",
    "hail damage roof repair",
    "insurance claim roofing",
    "residential roofing",
    "commercial roofing",
    "roof leak repair",
    "roof maintenance",
    "wind damage roof repair"
  ]
}
</script>

Place this in the head or body of the page, most often the homepage or the about page, where your Organization schema already lives.

Which Topics Belong in a Roofing knowsAbout Array?

Choose topics that map directly to the queries homeowners type, grouped by service, material, problem, and segment. Aim for 10 to 20 specific topics rather than a few broad ones.

Services and Materials

  • Core services such as roof repair, replacement, installation, and leak repair.
  • Materials you work with, such as asphalt shingles, metal, tile, and TPO.
  • Name each one the way a homeowner would, not in internal jargon.

Problems and Segments

  • Problem topics such as storm damage, hail damage, and wind damage.
  • Recurring work such as roof inspection and roof maintenance.
  • Segments such as residential, commercial, and insurance claim roofing.

How to Add knowsAbout to Your Roofing Schema

Add the property in four steps: audit your work, write the array, pair it with sameAs, then back each topic with a page. Treat it as a one-time setup that you revisit when services change.

The Four Steps

  • Audit the services, materials, problems, and areas you actually cover.
  • Add the knowsAbout array to the Organization node of your JSON-LD.
  • Combine it with sameAs links so search engines know which entity it describes.
  • Confirm each declared topic has a matching page or content section.

Where the Property Goes

knowsAbout belongs on the entity that represents the business, your Organization node, not on individual service pages. Pair it with RoofingContractor schema when that type fits your business.

Make Your Roofing Entity Readable

Search engines and AI tools answer from entity data. We write the knowsAbout array, wire it to your sameAs links, and align it with the pages on your site so the topics carry weight.

Call Now For Pricing

Or call +1 272-207-3231

How to Test knowsAbout in the Rich Results Test

Validate the markup with Google's Rich Results Test and the Schema Markup Validator, which read your JSON-LD and flag syntax errors. knowsAbout has no rich result of its own, so you check that the property parses, not that it triggers a snippet.

What to Check

  • Paste the page URL or the code into the Rich Results Test.
  • Confirm the Organization is detected with no errors or warnings.
  • Expand the detected item and verify the knowsAbout array is read in full.

What a Pass Means

A clean parse means the syntax is valid and the topics are machine-readable. It does not produce a visible rich result. For the types that do, see rich results eligibility.

How Does knowsAbout Work With Other Schema?

knowsAbout is one property inside a larger Organization markup, not a standalone block. It gains weight when the same entity also carries sameAs links and an accurate business type.

Pairs With sameAs

sameAs links your entity to its profiles, which confirms who the knowsAbout topics belong to. See sameAs entity links.

Sits On Organization

The property attaches to the business entity. Build that node with Organization schema first, then add the array.

Supports areaServed

Topics cover what you do; areaServed covers where you do it. The two describe the entity from different angles.

Common knowsAbout Mistakes Roofers Make

Roofing sites weaken the property through four recurring mistakes, each one fixable inside the schema markup.

Content and Topic Errors

  • Listing too few topics, which underuses the property; aim for 10 to 20.
  • Generic terms like "home improvement" that dilute the roofing signal.
  • Topics that read like internal labels instead of search queries.

Support and Structure Errors

  • Declaring topics with no matching page, which leaves the claim unsupported.
  • Adding the array with no internal links pointing to those topic pages.
  • Placing knowsAbout on a page node rather than the Organization entity.

Schema Is the Layer Most Roofers Skip

Keywords and links get the attention, while the entity layer sits empty. Declaring your topics is a one-time job that keeps paying back as AI search reads more from structured data.

Call Now For Pricing

Or call +1 272-207-3231

How Does knowsAbout Help AI Search Cite a Roofer?

knowsAbout helps because AI systems read entity data when they assemble answers, and a clear topic list makes your business easier to match to a roofing question. The effect is a higher chance of citation, not a guaranteed placement.

What AI Search Reads

  • Features in ChatGPT, Gemini, and Google AI Overviews draw on entity data.
  • A named topic list gives those systems a clear subject match.
  • A roofer with no entity signals can be passed over despite strong rankings.

What It Cannot Do

The property declares relevance; it does not fake authority. Topics with no supporting pages or reviews carry little weight, so the markup and the content have to agree. See entity SEO for roofers for the concept side.

Proof of Performance

Results from roofing campaigns that rank in local search.

Ranked in Local Search Within 90 Days

Map Pack Rankings

Ranked in Local Search Within 90 Days

150+ 5-Star Reviews Generated

Review Velocity

150+ 5-Star Reviews Generated

300% Increase in Qualified Traffic

Organic Traffic

300% Increase in Qualified Traffic

What Roofers Say

"Since partnering with Roofer Quest, our call volume has tripled. We had to hire two new estimators just to handle the influx from Google Maps."

M

Mike T.

Owner, Elite Roofing Solutions

"They don't just talk about rankings, they deliver signed contracts. The best ROI of any marketing investment we've ever made."

S

Sarah Jenkins

VP of Operations, Summit Commercial Roofs

"We used to rely on HomeAdvisor and shared leads. Now, 100% of our business comes exclusively through organic search. Game changer."

D

David R.

Founder, Apex Restoration

SEO Execution Strategy

The 180-Day Roofing SEO Roadmap

See how we optimize the profile, build the website, and earn local-pack rankings over a 6-month engagement.

1

Month 1: Profile Audit and Setup

  • Category and Field Fixes: Setting the primary category, secondary categories, description, services, and service areas.
  • NAP Cleanup: Correcting the name, address, and phone number across the profile, the website, and the directory citations.
2

Month 2: Reviews and Media

  • Review System: Setting up a steady request flow and replying to every review, positive and negative.
  • Photo and Post Cadence: Uploading job photos from each completed roof and publishing profile posts twice a month.
4

Month 4: Citations and Site Support

  • Citation Building: Adding consistent listings on the directories that feed prominence for a service area.
  • Service-Area Pages: Building city pages on the website that reinforce the profile's service areas.
6

Month 6: Local-Pack Rankings and Leads

  • Map-Pack Position: Reaching the top 3 of the local pack for core roofing queries in the served cities.
  • Lead Tracking: Measuring calls and direction requests from the profile against the cost of paid leads.

Owning Search Demand vs Renting It From Lead Platforms

If you pay Angi or Google Ads, you are renting visibility. The moment you stop paying, your pipeline dries up. Ranking the profile and the website for high-intent local searches builds permanent digital equity.

Shared Lead Platforms (Angi, HomeAdvisor)

  • The Race to the Bottom: Shared leads force you to slash prices to win against 5 other roofers.
  • Low Intent: Half the time they aren't ready to buy, they were just clicking around online.

Local Search SEO (Our Approach)

  • 100% exclusive, direct-to-you inbound calls.
  • Highest closing rate. They chose YOU from the local pack.
  • Compounding ROI. You don't pay per click.

We Identify Search Intent Using Industry-Leading Data Tools

Ahrefs
Semrush
Google Search Console
OpenAI
Nizam Ud Deen - Roofing SEO Expert
SEO Leadership

Expertise Built on Data. Not Guesswork.

I'm Nizam Ud Deen, and I don't build generic websites. I build search intent engines specifically for the roofing industry.

For years, I've watched roofers burn money on agencies that brag about "traffic" while the phones stay silent. Traffic without intent is worthless. My system maps exactly how homeowners search during storms, when comparing prices, and when they're ready to buy, and intercepts them at every stage.

100+
Roofers Scaled
15+
Years Experience
10k+
Keywords Ranked
0
Lock-In Contracts

The No-Brainer Roofing SEO Guarantee

We don't guarantee "traffic" or "rankings." We guarantee high-intent leads.

"We guarantee to generate 15 exclusive, inbound replacement or repair leads per month within the first 180 days, driven entirely by high-intent organic search. If we don't hit that metric, we work for free until we do."

Measuring Success: Leads and Revenue

We don't report on vanity metrics. If traffic goes up but revenue stays flat, the strategy failed. We track the pipeline.

100%

Call Tracking

Every keyword mapped to the exact phone call it generated.

Form

Form Fills

Tracking estimate requests from high-intent local landing pages.

ROI

Booked Jobs

Connecting CRM data to SEO efforts to prove actual revenue return.

$$

Cost per Lead

Monitoring organic CPL to ensure it beats shared platform costs.

The Roofing knowsAbout Implementation Checklist

Run your Organization schema through this checklist to confirm the knowsAbout property is written and supported correctly.

Array placed on the Organization node, not a page node?
Between 10 and 20 specific roofing topics listed?
Topics named the way homeowners search them?
No generic terms like "home improvement"?
Each topic backed by a matching page on the site?
Paired with sameAs links on the same entity?
JSON-LD passes the Rich Results Test with no errors?
Internal links point to the declared topic pages?

Frequently Asked Questions

Clear answers about the knowsAbout property in roofing schema.

What is the knowsAbout property?

knowsAbout is a Schema.org property that lists the topics an Organization or Person is expert in. On a roofing site it declares which roofing subjects your business covers, in a form search engines can read.

Where do I add knowsAbout in my schema?

Add it inside the Organization node of your JSON-LD, next to name, url, and sameAs, usually on the homepage or about page. See Organization schema for that node.

What value types does knowsAbout accept?

It accepts a plain text string, a URL to a relevant resource, or a structured Thing object. Most roofing sites use plain text topics inside an array, which is the simplest form to maintain.

How many topics should a roofer list?

A range of 10 to 20 specific topics works well. Too few underuses the property; too many generic ones dilute the signal. List the services, materials, problems, and segments you actually serve.

Does knowsAbout produce a rich result?

No. knowsAbout has no visible rich result of its own. It feeds entity understanding for search and AI systems. For types that do trigger snippets, see rich results eligibility.

Does knowsAbout prove my roofing expertise?

No. It signals relevance, not authority. The claim only holds when each topic has supporting content. See entity SEO for roofers for how the proof comes together.

How do I test the knowsAbout markup?

Paste the page or code into Google's Rich Results Test or the Schema Markup Validator. Confirm the Organization is detected with no errors and the knowsAbout array is read in full. A clean parse is the pass.

Should knowsAbout go on every page?

It belongs on the entity that represents the business, so it sits with your sitewide Organization schema rather than being repeated on individual service pages. One accurate declaration is enough.

What is the difference between knowsAbout and keywords?

Keywords describe what a page targets; knowsAbout describes what the business entity is expert in. The first is a content choice, the second is a structured-data declaration about the organization itself.

Can I use knowsAbout on a Person for a roofer?

Yes. knowsAbout works on both Organization and Person. Use Person for an individual roofer or consultant whose expertise you want to declare, often alongside author schema.

Why pair knowsAbout with sameAs?

sameAs links the entity to its verified profiles, which confirms which business the topics belong to. Together they give a clearer entity than either alone. See sameAs entity links.

What topics should a roofer avoid listing?

Avoid broad terms like "home improvement" or "construction" that dilute the roofing signal, and avoid topics with no supporting page. List only subjects your site can back up with content.

How does knowsAbout help with AI search?

AI search features read entity data when assembling answers. A clear topic list gives them a defined subject match, which raises the chance of a citation. It improves odds, not a guaranteed placement.

How often should I update knowsAbout topics?

Revisit the array when you add or drop a service, a material, or a segment. It is mostly a one-time setup, so updates are occasional rather than routine, made to keep the topics matched to your real work.

Get Your Free Roofing Schema Audit

We'll review the structured data on your roofing site, check whether the Organization node carries a knowsAbout array, and draft the topic list your markup is missing.

What You Get:

  • Schema Parse CheckA read of your Organization JSON-LD against the Rich Results Test for errors.
  • knowsAbout Gap ListWhether the property exists and which roofing topics are missing from it.

More Deliverables

  • sameAs Pairing ReviewWhether your entity links support the topics you declare.
  • Topic-to-Page MapA list pairing each declared topic with the page that should back it.

Claim your free roofing schema audit today. No commitment required.