← Back to blog

FAQ Schema for Contractors: What Still Works in 2026

November 12, 2026
FAQ Schema for Contractors: What Still Works in 2026

FAQ schema will no longer give your contracting website an expandable FAQ listing in Google. FAQ rich results stopped appearing in Google Search on May 7, 2026, after years in which only a small set of authoritative sites qualified. The markup itself is still valid, it is harmless to keep, and the visible FAQ it describes is still one of the most useful things you can put on a service page. This guide covers when to add it, how to write it, which other schema belongs on a service page, and how to test it.

Leapify Media
Turn More Leads Into Booked Jobs
Leapify Media builds AI-powered systems for home service companies to improve lead conversion and make marketing spend work harder.
Visit

TL;DR

  • FAQ rich results are gone from Google Search, so do not add FAQPage markup expecting stars, accordions or extra SERP space.
  • A visible, specific FAQ on each service page still helps customers decide to call, and that is the reason to write one.
  • If you add FAQPage JSON-LD, mirror the visible questions exactly and keep both in sync. Never mark up hidden content.
  • Put your effort first into LocalBusiness-style schema (a contractor type such as Plumber or GeneralContractor) and Service details, then FAQPage as an optional extra.
  • Validate with the Schema.org validator and check the page in Search Console after every template change.

Table of Contents

What happened to FAQ rich results

The short history matters, because most advice still ranking for this topic was written before it. In August 2023, Google limited FAQ rich results to well-known government and health sites. The May 2026 change ended eligibility for even those remaining sites, and Google planned to retire the related Search Console reporting and Rich Results Test support over the following months, according to Search Engine Journal's report.

Two details are good news for you:

  1. FAQPage is still a valid Schema.org type, defined on the Schema.org FAQPage page.
  2. Google's documentation says unused structured data does not cause problems for Search, so you do not need to rip out markup that is already on your site (Search Engine Journal).

So the question for a contractor is no longer "how do I win a rich result?" It is "does this markup cost me anything to keep, and does the FAQ behind it help a homeowner?"

Does FAQ schema still help contractors rank or get cited by AI?

Honest answer: there is no solid evidence that it does either on its own.

Older evidence was positive but narrow. SearchPilot ran a test on informational job pages that rewrote headings as questions and added FAQ markup, and reported an estimated +3% organic traffic after six weeks. The test changed two things at once, and the pages were earning rich snippets at the time, which no longer exist.

For AI answers, the data is thinner still. A 90-day vendor study that added FAQPage markup to 120 pages found no reliable lift in citations in ChatGPT, Gemini or Google AI Overviews. A small Perplexity increase appeared, but the study itself said that was platform-specific and not proof of cause. A second study of 615 already-cited pages found FAQ markup on more of the heavily cited ones, but that link disappeared once repeat publishers were accounted for.

Evidence on FAQ markup and search visibility

The practical reading, which Bugviso also reaches: write a good visible FAQ first, open each answer with the direct answer, and add the markup only if keeping it in sync is cheap. What people and AI engines quote is the text on the page, not the code behind it.

When a FAQ belongs on a contractor service page

A FAQ earns its place when it does the work a good estimator does on the phone: it removes the doubts that stop someone from booking. A sound rule set, in line with guidance on service page schema:

  • Visible on the page. Every question and answer in the markup is readable by a visitor.
  • Specific to the service. "How long does a water heater replacement take?" belongs on the water heater page. "Why choose us?" does not.
  • A real pre-enquiry question. Pull them from your call recordings, booking forms, Google Business Profile questions and the texts your office staff answer daily.
  • Not a copy of the whole page. Five to eight questions is plenty. A FAQ that repeats every paragraph adds nothing.
  • Maintained. When you change your warranty, service area or financing terms, the FAQ changes the same day.

Questions that tend to work by trade

The questions differ by trade, so write them from your own jobs rather than from a template:

  • HVAC: How fast can you come out for a no-cool call? What does a tune-up include? Do you service my equipment brand? For inspiration on how homeowners phrase the questions, see this list of questions to ask HVAC professionals.
  • Roofing: How does a storm damage claim work with your crew? What should a roofing contract spell out before work starts? A contractor-written explainer of roofing contracts for homeowners shows the kind of detail buyers want answered.
  • Landscaping and turf: How many bids should I get? How long does installation take? A landscaper's piece on getting two or three bids shows how that question is framed from the buyer's side.
  • Plumbing and electrical: Do you charge a trip fee? Are you licensed in my county? Do you offer same-day service?

A service FAQ from a cleaning company, like this professional carpet cleaning FAQ, is a good model for format: short questions, plain direct answers, no sales pitch.

A word on pricing answers: only publish a price or range you will honor. If you say "most drain clearings run $X to $Y," that number is now a promise your office has to match.

How to write valid FAQPage JSON-LD

JSON-LD is a block of structured data placed in the page's HTML, separate from the visible layout. The FAQPage structure has three layers: the page type, a list of Question items, and for each question an acceptedAnswer of type Answer. The property names are defined on Schema.org.

Here is a template for a water heater page. Swap in your own questions and keep the text identical to what visitors see:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How long does a water heater replacement take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Most standard tank replacements are finished in one visit. We confirm the timeline when we quote the job."
      }
    },
    {
      "@type": "Question",
      "name": "Do you haul away the old unit?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. Removal of the old heater is part of the job."
      }
    }
  ]
}
</script>

How to write valid FAQPage JSON-LD

Only write answers that are true for your company. The two answers above are placeholders to show structure.

Common mistakes to avoid

  • Wrong or missing properties. Every Question needs a name and an acceptedAnswer; every Answer needs text.
  • Mismatched text. The markup says one thing, the page says another, usually because someone edited one and not the other.
  • Broken JSON. A stray comma or an unescaped quotation mark inside an answer invalidates the whole block. Use a backslash before any double quote inside a text value.
  • Markup for content that is not there. Never add questions only in the code to cover topics you have not written about.
  • Empty answers from plugins. Page builders and SEO plugins sometimes output blank answer fields when a field is left unfilled.

The schema a contractor service page needs first

If you only have time for one improvement, make it your business markup, not FAQPage. Schema.org defines HomeAndConstructionBusiness with more specific types beneath it, including GeneralContractor, Plumber, Electrician, HVACBusiness, RoofingContractor and others. Choose the most specific type that fits what you do.

A solid contractor setup looks like this:

Schema typeWhere it goesWhat it describes
Specific contractor type (for example Plumber or HVACBusiness)Home page and location pageName, phone, address, hours, service area, logo, social profiles
ServiceEach service pageThe specific service, who provides it, and the area it covers
BreadcrumbListEvery inner pageThe path from home to service to location
FAQPageService pages with a visible FAQThe questions and answers on the page (optional)

A few rules keep this honest:

  • Match the page. Name, phone number and address in the markup must match your site footer and your Google Business Profile exactly.
  • Do not overclaim. Skip review and rating markup unless the reviews are genuinely displayed on that page and are about that business. Never invent ratings or award data.
  • One service per page. The Service markup on a drain cleaning page should describe drain cleaning, not your entire catalog.
  • Service area, not a fake address. If you work out of a home base and travel to customers, describe the areas you serve rather than listing a storefront you do not have.

Schema supports your visible content and your Google Business Profile. It does not replace them. If you want the surrounding pieces right, our guides on local SEO for contractors, service area pages and the Google Business Profile for contractors cover them in detail.

How to add the markup to your site

The method depends on your platform, but the steps are the same.

  1. Write the visible FAQ first. Put it low on the service page, after the proof and the call to action, with each question as a heading and the answer directly underneath.
  2. Generate or hand-write the JSON-LD. For a handful of questions, a template like the one above is fine. Generators work but check their output: they can miss properties or leave HTML inside text fields.
  3. Insert it. On WordPress, most SEO plugins have a FAQ block that outputs the markup automatically, or you can paste a script block into a custom HTML block. On a custom or builder-based site, add the script to the page's head or body through the page's code field.
  4. Avoid duplicates. If your theme, SEO plugin and a separate FAQ plugin each output FAQPage, you can end up with conflicting blocks on one page. Use one source.
  5. Publish and test as described below.

For a template-driven site with dozens of service and location pages, generate the markup from the same data that fills the visible FAQ. That is the only dependable way to keep them in sync.

How to test your markup

Google announced the removal of FAQ support from the Rich Results Test and the Search Console reporting, so use tools that check the structure itself. The Schema.org Markup Validator parses your page or pasted code and flags syntax and property problems regardless of Google's features.

A quick audit routine:

  1. Paste the page URL or code into the validator and fix every error.
  2. Compare each question and answer in the code to the page text, word for word.
  3. Confirm the business name, phone and address match your Google Business Profile.
  4. Check the page is indexable and not blocked, because markup on a page Google cannot index does nothing.
  5. Re-test after any theme, plugin or page builder update.

If a page is going to be cited in an AI answer, the fundamentals decide it: Google's own AI features guidance, as summarized by Anglera, says a page needs no special markup beyond being indexed and eligible to show in Search with a snippet.

Our perspective: write the FAQ for the caller, not for the crawler

We build marketing systems for home service companies, and the pattern we see is consistent: the FAQ that matters is the one that answers the question a homeowner would otherwise call and ask, or worse, never ask because a competitor's page already answered it.

That is why we treat FAQ schema as housekeeping and the FAQ content as strategy. The markup is a few minutes of work once the questions exist. Finding the right questions is the work: reading call transcripts, looking at what people ask dispatchers, and noticing which objections kill a lead before it becomes a booked job.

Our approach is built around converting spend into booked jobs, so we care most about what happens after the click. A service page with clear answers on timing, pricing structure, licensing and service area gives your ads, your local SEO and your phones a better page to work with. Our AI lead scoring and dispatch run on in-house infrastructure, which means the questions your leads ask can feed back into the pages you build, instead of sitting in a third-party tool.

Get the page right for people. Add clean markup behind it. Then spend your energy on the things that move calls: your Business Profile, reviews, service area pages and a fast response to every lead.

Everson Gorski

Where to spend the effort instead

A realistic priority order for a contractor website in 2026:

  1. Service pages that answer the buyer. One page per core service, with scope, process, timing, proof and a visible FAQ.
  2. Business and Service schema. Accurate, specific and consistent with your profile.
  3. Google Business Profile. Categories, services, photos, posts and questions answered.
  4. Conversion-ready landing pages for paid traffic. See our notes on contractor landing pages and HVAC landing page examples.
  5. AI visibility basics. Our 90-day roadmap for AI and local SEO lays out the content and citation work that matters.
  6. FAQPage markup, once the visible FAQ is solid.

Get the whole funnel working, not just the markup

Schema is one small part of turning marketing spend into booked jobs. If your pages, ads and follow-up are not working together, we can help. Leapify Media runs Google Ads and Meta Ads management, local SEO and content, CRM setup and automation, and on-premise AI lead dispatch for home service companies. SEO & Content starts from $2,000 per month, and our Foundation plan starts from $2,500 per month, as listed on our pricing page.

Leapify Media

If you are a home service business with at least $500K in annual revenue and want to see how the pieces fit, look at our services or start at Leapify Media.

FAQ

Is FAQ schema still worth adding for a contractor website?

It is optional. Google stopped showing FAQ rich results on May 7, 2026, but FAQPage is still a valid Schema.org type and Google says unused structured data does not cause problems. If you already have a visible FAQ and can keep the markup in sync, adding it costs little. Do not expect a ranking boost from it.

Can I put FAQ schema on every service page?

Only where the page has a visible FAQ with questions specific to that service. Copying one generic FAQ across every page creates thin, repetitive content and a maintenance burden. Write three to eight real questions per page instead.

What schema should a contractor use on a service page?

Start with the most specific business type for your trade, such as Plumber, Electrician or GeneralContractor, then add Service markup for the page's service and BreadcrumbList for navigation. FAQPage sits alongside these as an optional addition. All details must match what is visible on the page.

How do I check that my FAQ schema is valid?

Run the page or code through the Schema.org Markup Validator and fix any errors. Then compare the markup text with the visible text and confirm the page is indexable. Recheck after theme or plugin updates, since those often change the output.

Sources