Q&A and Discussion Forum Schema for Local Service Businesses: 2026 Implementation Guide

If your site still uses FAQPage markup for everything, you’re probably getting outdated results. Google moved on, and most local service businesses don’t need “classic FAQ” schema for every kind of community content.

What actually helps in 2026 is using the right structured data for the page you built: service-page FAQs, “we answered this question” pages, and review/Q&A response threads. In March 2026, Google expanded support for Discussion Forum and Q&A Page structured data, including richer comment thread interpretation. That change matters because it affects how your content can be understood, not just whether markup is present.

This guide is for busy operators who want the implementation to be simple and safe. Use the schema type that matches the page’s real content. Don’t force everything into FAQPage. Build a clean QAPage for one main question and a best answer, and a DiscussionForumPosting for a real multi-participant thread.

What changed in March 2026

In March 2026, Google expanded support for Discussion Forum and Q&A Page structured data. The practical takeaway is this: richer thread structure can be interpreted more accurately, so your markup has more value when it matches the way your content is actually organized.

Here’s the part you should care about for local service businesses:

Discussion Forum support expanded for forum-style discussions with multiple participants and comments. Google can better interpret the thread structure instead of treating it like a generic block of text.
Q&A Page support expanded for pages centered on one main question and one accepted/best answer. Google can interpret the question/answer relationship more reliably.
Richer comment thread interpretation improves how “comment arrays” and participation look in structured data, which is a big deal for community-style pages and response threads.

And while those changes sound technical, the decision is simple:

If the page is one core question with one best answer, use QAPage.
If the page is a multi-person thread with multiple comments, use DiscussionForumPosting.

For local service businesses, the highest-value use case still isn’t “classic forums.” It’s service-page FAQs and review/Q&A response pages where you can show a specific question and a real answer, written by a real person.

If you want the schema fundamentals first, start with the machine understanding layer chapter.

Three schema types service businesses should know

FAQPage — what it still does, what it no longer does

FAQPage can still be used, but it’s not the universal solution it used to be. For most local service businesses, it’s now mainly limited for promotional use and is surfaced primarily for authoritative health/government sites.

Plain-English fit for local service businesses:

Use FAQPage when you have a page that clearly qualifies as an FAQ-style informational page in the way Google expects for those surfaces.
Don’t use FAQPage as your default template for “everything with a question mark.”

If your “FAQ” is really a customer question answered by your company, QAPage is usually the better match.

QAPage — when to use it

QAPage is for pages where one main question has one accepted/best answer. The markup is designed around that relationship: one question, one best answer, and the page context that proves the answer belongs to the question.

Plain-English use-case for local service businesses:

A service page section titled like “Do you do emergency repairs?” with your company’s best answer.
A page that mirrors a customer question from GBP or a review thread, where you post your response as the “best answer.”
A response page where you show the question, then your owner/manager’s answer, and it’s clearly the definitive response.

This is the most practical schema for local services.

DiscussionForumPosting — when to use it

DiscussionForumPosting is for forum-style discussions where multiple participants/commenters interact over time. The schema supports a headline, publishing/author data, and a comment array representing the thread.

Plain-English use-case for local service businesses:

A service-area community thread where you and customers discuss the same topic across multiple replies.
A moderated Q&A thread where multiple people add follow-up questions or experiences.
A community response page where there are multiple comments, not just a single accepted answer.

For most HVAC, plumbing, roofing, and electrical businesses, this is still less common than QAPage. Use it when you truly have a thread with multiple participants.

QAPage example for a local service business

Below is a realistic example for a plumbing business. The page is about emergency service and includes one main customer question with the company’s best answer.

{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "Do you have emergency plumbing hours for burst pipes on weekends?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Yes. If you have a burst pipe or active leak, call us anytime. Our dispatch team will route your request, and we offer same-day service when a technician is available. If the leak is in an unsafe area, we can advise on immediate shutoff steps while you wait for the first available appointment.",
      "author": {
        "@type": "Person",
        "name": "Martin Reyes"
      },
      "dateCreated": "2026-05-01"
    }
  },
  "datePublished": "2026-05-01",
  "author": {
    "@type": "Person",
    "name": "Martin Reyes"
  }
}

Operator notes:

The question reads like something a customer would ask.
The answer is written by your business representative (name shown in markup).
There’s one accepted/best answer because the page is built around one definitive response.

If you’re doing “GBP Q&A mirror pages,” this is usually the markup you want, because the page is often a single question with your response as the best answer.

DiscussionForumPosting example

Here’s a service-area community thread example using DiscussionForumPosting. The thread is about summer drain clogs, and it includes comments from multiple participants.

{
  "@context": "https://schema.org",
  "@type": "DiscussionForumPosting",
  "headline": "What causes slow drains in summer and what should homeowners do first?",
  "datePublished": "2026-05-03",
  "author": {
    "@type": "Person",
    "name": "Ava Thompson"
  },
  "comment": [
    {
      "@type": "Comment",
      "text": "We get slow drains every July. Is it usually grease, or is it something else in older pipes?",
      "dateCreated": "2026-05-03",
      "author": {
        "@type": "Person",
        "name": "James W."
      }
    },
    {
      "@type": "Comment",
      "text": "A lot of the time it’s a mix of hair/soap buildup and minor sediment. Start with a plunger for toilets, check the P-trap under the sink, and avoid chemical cleaners if you suspect roots. If water backs up after basic cleaning, schedule an inspection so we don’t miss a bigger issue.",
      "dateCreated": "2026-05-04",
      "author": {
        "@type": "Person",
        "name": "Ava Thompson"
      }
    }
  ]
}

Operator notes:

This is a thread. There are follow-ups.
There are multiple comments, not just one Q and one A.
The content style matches a discussion, not a marketing paragraph.

If your page is mostly a sales pitch, don’t try to force it into DiscussionForumPosting. That schema expects thread-like participation.

Where to put each type

Use a page-level mapping. Don’t decide the schema type first. Decide based on what the page actually contains.

Service pages

Best fit: QAPage for “one question, your accepted answer.”
Example sections:
- Emergency hours
- Warranty coverage
- What to do when a furnace won’t light
- How fast you can arrive for storm damage
Avoid: stuffing multiple unrelated questions/answers into one QAPage block. If it’s multiple questions with multiple answers, split into separate pages or use a different approach.

GBP Q&A mirror pages

Best fit: QAPage for each mirrored question where your response is the accepted/best answer.
Typical workflow: capture a question from your GBP Q&A, post it on your site, then publish your reply as the definitive answer.
If you’re managing the process, pair it with the workflow in the GBP Q&A management system.

Review-response detail pages

If your page shows a single question-like prompt (for example, a “How fast can you come out?” from a review thread) and you provide one clear best answer, use QAPage.
If the page is a multi-comment thread with follow-ups, use DiscussionForumPosting.
Don’t mix the two in the same URL. Pick one structure that matches the reader experience.

Implementation checklist

Match the schema type to the page structure. QAPage = one main question + one accepted answer. DiscussionForumPosting = thread with multiple comments.
Only one schema type per page. If a page is QAPage, don’t also add DiscussionForumPosting on top. Keep it clean.
Validate with the Rich Results Test before you ship it live, and validate again after edits to the page.
Use real names, not placeholders. If you don’t want Martin Reyes on the page, don’t put “Martin Reyes” in the JSON-LD. The markup should reflect the on-page authorship.
Include the correct author and date fields. Don’t skip dateCreated/datePublished on content you’re presenting as a real post/answer.
Link the markup to the source page content. In QAPage, your mainEntity question should reflect what the page actually shows. In DiscussionForumPosting, the headline and comments should match the thread text.
Keep answers truthful and operational. Emergency hours, availability, and service boundaries should be accurate. Structured data will make your claims easier to understand and cross-check.

Common mistakes

Stuffing fake Q&As into the markup. If your site doesn’t actually show the same question and answer in plain text, the markup becomes a mismatch. Make the content real, then mark it up.
Mixing FAQPage and QAPage on the same page. If you’re building one question with one accepted answer, QAPage is the match. Don’t throw FAQPage in “just in case.”
Missing dateCreated/datePublished. Google can interpret freshness better when you supply publishing and creation dates that align with the page content.
Using QAPage for marketing copy that isn’t a real question/answer. QAPage is for a specific question and a best answer. If the page is mostly promotional, it won’t fit the intent of the schema.

Bottom line

In March 2026, Google expanded support for Discussion Forum and Q&A Page structured data, with better interpretation of thread structure. For local service businesses, the practical play is to use QAPage for service-page FAQs and GBP/review response pages built around one best answer, and use DiscussionForumPosting only when you truly have a multi-participant comment thread.