Skip to content
CiteScore

Guide

AI search visibility for roofers

How a roofing contractor site can be fetched and quoted by ChatGPT, Perplexity, and Google AI Overviews: RoofingContractor markup, service-area pages, reviews, FAQs, robots.txt. llms.txt is optional; Google says it ignores llms.txt. No citation rate.

22 October 2026 · CiteScore Team · 12 min read

A roofing contractor is cited when an answer engine can fetch a page and find a sentence that states the business, the work, the place served, or the limit of that page. ChatGPT search, Perplexity search, and Google AI Overviews each publish a crawler or indexing control. None of those pages publishes a citation rate for roofing contractors, a required word count, or a schema type that turns a homepage into a footnote. CiteScore does not log into those products, and it does not give roofing, licensing, insurance, or legal advice. It does not say which license a business must hold, and it does not say what an insurance claim will pay. The work here is how those products pick a source, the business record, service-area pages that say something distinct, one URL per service, the name and phone a person can already read, reviews, questions the page already answers, robots.txt, and llms.txt as a reading list.

The local markup rules are on GEO for local businesses. The engine pages are ChatGPT, Perplexity, and Google AI Overviews. A plumbing business’s office, service area, and hours are on AI search visibility for plumbers. An HVAC company’s office, service area, and hours are on AI search visibility for HVAC. A restaurant’s location, menu, and hours are on AI search visibility for restaurants. A dental practice’s office, services, and hours are on AI search visibility for dentists. An accounting, CPA, or bookkeeping firm is on AI search visibility for accountants. A law firm’s office page is on AI search visibility for law firms. A brokerage, an agent, or a property manager is on AI search visibility for real estate. A store’s price problem is on AI search visibility for ecommerce. A software company’s comparison page is on AI search visibility for B2B SaaS.

How an assistant picks a source

An assistant can quote a page it is allowed to fetch, when that page states the fact in a sentence. Blocking the search crawler keeps the site out of that product’s answers. Allowing the crawler does not promise a citation. There is no published rate for how often a roofing contractor, a business, or a service is named.

Google’s optimization guide, read on 22 October 2026, says structured data is not required for AI Overviews or AI Mode, and that there is no special schema.org type to add for those features. The same guide says a unique page does more over time than a commodity summary, and that a separate URL for every query variation, written to manipulate rankings or generative AI responses, violates the scaled content abuse policy. A folder of city pages that only swap the city name is that pattern. A folder of “roofing near me” pages that only swap the neighborhood name is the same pattern. Write the places and the services the site actually covers.

A directory or a review site can be the page an answer quotes. You can keep one business name so a mention and your H1 match. You cannot edit their page from your deploy. To see whether ChatGPT names the business, repeat the same prompts and keep a log, as on how to check if ChatGPT mentions your brand. The free check does not run those prompts.

RoofingContractor for the business

schema.org RoofingContractor, read on 22 October 2026, is a roofing contractor. It is a HomeAndConstructionBusiness. That type, read the same day, is a LocalBusiness that provides services around homes and buildings, and it can be described as a provider of one or more services. Use RoofingContractor for the page about the roofing business. Use HomeAndConstructionBusiness or LocalBusiness when the page is a home-services business and RoofingContractor does not fit. Do not use Plumber, Electrician, or HVACBusiness for a roofing contractor. An electrical contractor’s pages are on AI search visibility for electricians. A landscaping business’s pages are on AI search visibility for landscapers. An auto repair shop’s pages are on AI search visibility for auto repair. A chiropractic office’s pages are on AI search visibility for chiropractors. An insurance agency’s office, lines of coverage, and hours are on AI search visibility for insurance agents. A veterinary clinic’s office, services, and hours are on AI search visibility for veterinarians. Use Organization for a homepage that is not one street address. Google’s local business documentation, read on 22 October 2026, says to use the most specific subtype. Its examples are Restaurant, DaySpa, and HealthClub. It does not name RoofingContractor. The subtype still applies, because that is the type schema.org defines for this business.

That same Google page requires name and address for a local business rich result. Recommended fields, when the page shows them, include geo to at least five decimal places, openingHoursSpecification, telephone with country code and area code, and the url of that page. Google does not guarantee that the panel or the list will show. If the page does not show a street address, do not invent one to qualify. A rich result that requires an address is then outside what this page can honestly mark up. Google’s structured data gallery, read on 22 October 2026, lists Local business. It does not list a separate roofing rich result.

{
  "@context": "https://schema.org",
  "@type": "RoofingContractor",
  "name": "Example Roofing",
  "url": "https://example.com/offices/springfield",
  "telephone": "+1-555-010-0196",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "418 Cedar Street",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62704",
    "addressCountry": "US"
  },
  "openingHoursSpecification": {
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "07:00",
    "closes": "17:00"
  }
}

That block is an example, not a business. Google’s structured data policies say the markup has to describe content people can see. The Local business schema generator already lists RoofingContractor. It copies the name, the address, the phone, the hours, and optional geo into one script in the browser. It does not emit areaServed, review, or aggregateRating. The address in that script is the address the page shows. It is not a customer’s street, and it is not the street of a second shop you left off the page.

schema.org areaServed is the geographic area where a service or offered item is provided. It supersedes serviceArea. Add it by hand on the RoofingContractor script only when the page names the places served. A list of every city you hope to rank for is not that property. A page that names one person the site already credits uses Person. The Person schema generator builds that script. This guide does not print a personal name. A group homepage that is not one office can use the Organization schema generator. A photo that shows a credit or a license uses the ImageObject schema generator. A restaurant the business publishes, on its own URL, uses the Restaurant schema generator. The restaurant page is not the roofing business.

Service-area pages

A roofing contractor often works at the customer’s address and also publishes pages for the cities or counties it covers. Publish a separate URL only when that page states something a person in that place can check: which services are offered there, which shop or crew covers it, the hours, and a limit the page is willing to state. A page that changes only the city name is the scaled-content pattern in Google’s optimization guide. Leave that page unpublished. A draft city page does not belong in the sitemap.

Say the area in a sentence, then repeat that place in areaServed on the service that page describes. Do not mark the city page as a second RoofingContractor with a fake street address. Do not paste a customer’s home address into the script to prove you work there. The business address, when you publish one, stays the address on the business page. The service area stays the places the page names. A storm in one county is not a reason to publish a copy of the same page for every town in that county.

One URL per service

A repair, a replacement, an inspection, and a leak call are different offers when the site publishes them as different pages. Put the name of the work, who it is for, and the place it covers in the HTML the server sends. Say the limit the page is willing to state, such as which area or which hours, and leave out a price, a response time, a material brand, or a result the page does not show. This guide does not say which services a business should offer, and it does not describe a repair. A draft service that is not public does not belong in the sitemap.

A page about one system the company installs belongs on its own URL only when the site already does that work and the page says so. Do not add a manufacturer name the page does not show. Do not promise an insurance payment, a storm settlement, or a code outcome. If the page describes an inspection after a storm, the sentence can say what the inspection is. It should not say what a carrier will pay. CiteScore does not give insurance advice.

schema.org Service is that offer. serviceType is the label. provider is the business. areaServed is the place the page names. The Service schema generator copies that shape, with the provider as an Organization. It writes an Offer only when you enter both a price and a currency. Do not mark every city as its own Service when the page does not describe a different offer. Do not mark the whole homepage as one Service that lists every job. A fee the page does not show does not belong in the Offer.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Example roof inspection",
  "serviceType": "Roof inspection",
  "description": "Roof inspection for homes in Springfield. Example markup only. This is not a quote, and it is not an insurance outcome.",
  "url": "https://example.com/services/roof-inspection",
  "provider": {
    "@type": "Organization",
    "name": "Example Roofing",
    "url": "https://example.com/offices/springfield"
  },
  "areaServed": "Springfield"
}

Questions the business itself answers, visible on the page, can use the FAQ schema generator. Google’s Search updates, read on 22 October 2026, say the FAQ rich result stopped appearing on 7 May 2026, and that the documentation for that feature was later removed. Keep the questions when they are real and visible. The markup does not bring the accordion back, and it does not create a citation. Other types are on the schema guide.

The name, the address, and the phone

People call that trio NAP: the name, the address, and the phone. The business page, the JSON-LD, and Google Business Profile are three records of one business. Google’s optimization guide says Business Profile information can be included in AI responses and in other Google Search results. Use one spelling of the name, one phone, and, when you publish a street, that same street. A profile that says “Example Roofing” and a site that says “Example Roofing LLC” are two names an assistant can split. Pick the spelling the page is willing to keep, and use it in the H1, the script, and the profile.

If you do not publish a street address, leave streetAddress empty. Do not borrow a home address, a PO box the page does not show, or the address of a supplier. The city, the phone, and the hours the page shows are the record. An office line that closes at 17:00 and an after-hours line that answers later are two phones. Write the number the page is about. Use department only when a unit has its own phone or its own hours, and add it by hand. The local business generator does not write department. The longer local note is GEO for local businesses.

Google’s local business page shows a closed day as opens and closes both set to 00:00. The local business generator writes the times you enter, including that pair, on the days you select. It does not invent a closed day you left blank. Leaving Sunday out of the script does not tell a reader the shop is closed. Say so in the HTML. Google’s page also documents validFrom and validThrough for a seasonal closure. Add those dates by hand only when the page shows the dates. If the page shows a license number and the jurisdiction, repeat that license and the jurisdiction in a sentence a person can read. Do not add a license the page does not show. This guide does not say which license a business must hold.

Reviews and job photos

Google’s local business documentation recommends review and aggregateRating only for sites that capture reviews about other businesses. A roofing contractor marking up its own stars is outside that recommendation. Leave both properties off the RoofingContractor script. The local business generator already leaves them off. Google’s review snippet guidelines, read on 22 October 2026, say the same limit for a local business or an organization that controls the reviews about itself. A page that shows reviews of a product or an app uses the Review schema generator, which does not write LocalBusiness. A star count copied from a review site into JSON-LD, when the business page does not show those reviews, describes a rating the reader cannot see.

A review a customer wrote on your site can stay on the page when it is real and the page shows it. Do not invent a customer, a quote, or a star rating. A photo of a finished roof can stay on the page when the page shows it. Do not put the customer’s name, the street, or the inside of the home in the caption, the script, or llms.txt. A photo that shows a credit or a license uses the ImageObject schema generator. An assistant can quote a sentence you wrote about the work. It should not receive a customer’s address from your markup.

Questions the page already answers

The questions worth publishing are the ones the business already answers: which area the page covers, what the visit includes, which hours are the office and which are the after-hours line, and what the page will not promise. Put the question and the answer in the HTML a person can read. Then, if you want the labels, use the FAQ schema generator. One question without an answer is left out of that script. A question you do not actually answer does not belong on the page. Google’s Search updates say the FAQ rich result stopped appearing on 7 May 2026, so the reason to keep the block is the visible answer, not an accordion under a Google listing.

Customer files stay out

An estimate, an invoice, a scheduling login, a photo that shows a customer’s street, a form that only works after sign-in, and a draft page are not public pages. Disallow them in robots.txt, leave them out of the sitemap, and do not link them from llms.txt. A portal URL that only works after a login is not a page a crawler can quote. The public business page and the public service pages have to be allowed if you want them fetched.

robots.txt for the search crawlers

Give each token its own group when User-agent: * already disallows the host. The token list is robots.txt for AI crawlers, and the copy-paste file is the robots.txt generator. An Allow line can still sit behind a firewall 403. Staff pages and anything that is not public stay disallowed. Decide GPTBot, Google-Extended, and the search crawlers separately. Blocking the training token does not, by itself, block the search token. Blocking Google-Extended does not, by itself, remove the site from AI Overviews. The user-agent reference, including tokens this site has not confirmed, is AI crawler user agents.

llms.txt is a reading list

The llms.txt proposal, v2, updated 10 August 2026 and read on 22 October 2026, is an optional Markdown file, usually at /llms.txt. The H1 is the only required section. Google’s optimization guide says Google Search ignores the file, so it neither helps nor harms AI Overviews, AI Mode, or other Google Search rankings. A missing file is not a block, and a present file is not a citation.

For a roofing contractor, link the homepage, the public business page, and the public services you want read. Use canonical URLs. Link a city page only when that page states a distinct fact. Leave out estimates, invoices, customer names, home addresses, and any page that asks the reader to sign in. Do not paste every city when the site already has one service URL. The proposal says the links should point at a Markdown version of the page when you publish one. Until you do, link the public HTML URL. Section order and the mistakes that break a read of the spec are on llms.txt best practices. The llms.txt generator copies a starter file in the browser. The checker only looks for a non-empty file. Worked files are on llms.txt examples.

# Example Roofing

> Example Roofing is one roofing business in Springfield, Illinois. This file is an example.

## Office

- [Springfield](https://example.com/offices/springfield): The name, address, phone, and hours on that page

## Services

- [Roof inspection](https://example.com/services/roof-inspection): The work the page describes, and the Springfield area named there

## Optional

- [News](https://example.com/news): Business announcements a reader can skip

What you can measure

Google’s optimization guide tells a site owner to use the Generative AI performance report in Search Console for AI Overviews and AI Mode on Google Search. CiteScore does not read Search Console. AI Mode uses the same eligibility as AI Overviews, on Google AI Mode optimization. Meeting the indexing rules does not guarantee indexing. A prompt you type into ChatGPT, Perplexity, or Gemini is a sample, not a share of voice. Keep the wording the same if you repeat it, and write down the date. The free check does not run that sample.

A workable order

  1. Publish one business URL with the name, the phone, the hours, and the street if you show one, and the same facts on the Business Profile.
  2. Add RoofingContractor JSON-LD from those visible facts. Leave the street out when the page does not show one. Leave reviews and ratings off that script.
  3. Publish one URL per service the site actually offers. State the work and the place in text. Point the service script at that URL, with areaServed set to the place the page names.
  4. Publish a city or county page only when it states a distinct fact. Do not swap the city name across an otherwise identical page.
  5. Publish the questions the business already answers, in HTML. Add FAQ markup only for those visible pairs.
  6. Allow OAI-SearchBot, PerplexityBot, and Googlebot on the public pages. Decide GPTBot and Google-Extended separately. Keep estimates, invoices, customer files, and drafts disallowed.
  7. Add /llms.txt only as a curated list for readers other than Google Search.
  8. Submit the sitemap, and confirm Search Console includes the site in generative AI features.

These steps make a sentence fetchable. They are not a citation. The longer on-page list is the AI Citation Readiness Checklist.

Free AI Answer Snapshot, then the Fix Pack

The free AI Answer Snapshot asks logged-out ChatGPT and Perplexity who they name for a local business and sends one page. AI answers vary run to run. No payment. The Fix Pack, $49 is the done-for-you work after you have seen who was named.

Run the free check on the public host. It reads the homepage, GPTBot, PerplexityBot, Google-Extended, llms.txt, a sitemap, and homepage JSON-LD. It does not read OAI-SearchBot, and it does not query ChatGPT, Perplexity, or Google AI Overviews. For a business or service URL, start with the free AI Answer Snapshot. The Fix Pack is the done-for-you work after you have seen who was named. The homepage check does not open that path.

The GEO Content Template Pack ($19) is a separate $19 purchase from the check and the Fix Pack.

Questions about roofing contractor visibility

Does RoofingContractor schema get a roofing contractor cited by ChatGPT, Perplexity, or AI Overviews?

No. schema.org describes RoofingContractor as a roofing contractor. It is a HomeAndConstructionBusiness, which is a LocalBusiness that provides services around homes and buildings. Google’s local business documentation says name and address are required for a local business rich result, and that Google does not guarantee the feature will show. Google’s optimization guide, read on 22 October 2026, says structured data is not required for AI Overviews or AI Mode, and that there is no special schema.org type to add for those features. None of those pages publishes a citation rate for roofing contractors. The script has to match the visible page. This page is not roofing, licensing, insurance, or legal advice.

When should the page be RoofingContractor, and when a service or a service-area page?

Use RoofingContractor for one public page about the roofing business, with the name and the address the page shows. HomeAndConstructionBusiness is the parent type. Use it, or LocalBusiness, when the page is a home-services business and RoofingContractor does not fit. Plumber, Electrician, and HVACBusiness are different trades. Organization fits a homepage that is not one street address. Use Service on the page for one offer the site actually publishes, such as a repair, a replacement, or an inspection, with the place the page names in areaServed. A city page that only swaps the city name is not another RoofingContractor, and it is not another Service. Do not mark a customer’s home, an invoice, or a job photo as the business.

Does a review star, a matching phone number, a license line, or llms.txt put a roofer into ChatGPT or AI Overviews?

No. The same name, the same phone, and the same address, when you publish an address, make one record an assistant can match. They do not create a citation. A license number helps only when the page already shows that number and the jurisdiction. This page does not say which license a contractor must hold. Google’s local business page recommends review and aggregateRating only for sites that capture reviews about other businesses. A roofing contractor marking up its own stars is outside that recommendation. The stars do not create a citation. The llms.txt proposal is a Markdown reading list. Google’s optimization guide says Google Search ignores special AI text files, including llms.txt, so the file neither helps nor harms AI Overviews or AI Mode. A missing file is not a block, and a present file is not a citation. Google-Extended, which covers Gemini Apps, is a separate robots.txt choice from whether Search includes the site in AI Overviews.

Does the free check query ChatGPT, Perplexity, or Google AI Overviews, or open a customer file?

No. The free check reads the homepage, robots.txt for GPTBot, PerplexityBot, and Google-Extended, a non-empty llms.txt, a sitemap, and JSON-LD types on the homepage. It does not read OAI-SearchBot, it does not log into an answer engine or Search Console, and it does not open invoices, estimates, or a scheduling login. An office URL or a service URL is outside the homepage check. CiteScore does not give roofing, licensing, insurance, or legal advice.

Sources

Request a free AI Answer Snapshot

Same request as the free snapshot page. AI answers vary run to run. This is a snapshot, not a ranking, and not a promise that any assistant will name the business.

All fields are required.

We email the snapshot to this address. We do not ask for passwords, cookies, or content behind a login. We do not sell emails. Privacy.

Email this request instead
citescore@mail.grokbot.com

No mail app opened? Copy this and email it to citescore@mail.grokbot.com from any inbox.

If that send fails, email this request instead, or use the copy buttons.

Sends the business name, city, service, website, and email to citescore@mail.grokbot.com through FlowForm. This page path is included. No account and no paid checkout.

Prepared by the CiteScore Team.