Bodyne
Schema beginner ·20 min

Add FAQ Answers and Schema to Your Restoration Site

The steps

  1. Write three real customer questions and answers
  2. Put the questions and answers on the page as visible text
  3. Add the optional FAQPage schema block
  4. Add the code to your site
  5. Validate the markup in Schema.org Validator

Most restoration websites answer customer questions in paragraphs, buried three scrolls down. A homeowner scanning for one fact gives up, and so does anything reading the page on their behalf. This guide turns the three questions you get asked every week into clear, crawlable answers, then adds optional FAQPage markup on top. About twenty minutes, no developer.

One thing to set straight before you start. Google retired the FAQ rich result in May 2026, and it states that its AI features require no special AI markup or files. So the markup is optional and it guarantees nothing. The visible answer is the part that does the work. Add the schema because it describes your page accurately, not because it buys you a result.

You do not need to understand the code. You need three real answers and the ability to paste a block of text into your site.

Step 1: Write three real questions and answers

Open a note and write the three questions homeowners ask you most. Real ones, in their words. For a water and mold company that is usually something like:

  • “How fast can you start water extraction?”
  • “Do you bill my insurance directly?”
  • “How long does mold remediation take?”

Write a short, accurate answer under each. Two to four sentences. No marketing language, no superlatives. If a homeowner read it out loud it should sound like you on the phone.

Now put them on the page as visible text, under real headings, where a person can read them. This is the step that actually matters. Do not hide a useful answer inside code and leave the page itself vague.

Keep these answers somewhere you can copy from. You will use them twice: once as visible text on the page, once inside the schema.

Step 2: Build the optional FAQ schema block

Here is the template. Replace the question and answer text with yours. Keep the quotes and commas exactly where they are.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How fast can you start water extraction?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We answer calls 24/7 and aim to have a crew on site within an hour for active water loss in our service area. Standing water gets worse by the hour, so we treat it as an emergency."
      }
    },
    {
      "@type": "Question",
      "name": "Do you bill my insurance directly?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. We document the loss, send our scope to your adjuster, and bill the carrier directly so you are not floating the cost. You handle your deductible and we handle the paperwork."
      }
    },
    {
      "@type": "Question",
      "name": "How long does mold remediation take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A typical residential job runs three to five days depending on the affected square footage and whether containment and clearance testing are required. We give you a written timeline before any work starts."
      }
    }
  ]
}
</script>

The text inside each "text" field must match the answer that appears on the page for a visitor to read. If the page does not yet show these questions and answers as real content, add them to the page body first.

Step 3: Add the code to your site

WordPress

Use a code snippet plugin so you never touch theme files. Install WPCode (free), create a new snippet, set the type to HTML, set the location to Site Wide Header if the FAQs are sitewide or to the specific page if not, paste the block, and activate it. If you prefer page-level control, edit the page, add a Custom HTML block at the bottom, and paste the same code.

Wix

Open the page in the Editor. Add an Embed Code → Custom Embeds → Embed HTML element, click Enter Code, and paste the block. Place it low on the page. Publish. Note that Wix can wrap embeds in an iframe on some templates; after publishing, verify with the test in Step 4 and, if it fails, move the markup to Settings → Custom Code → Add Custom Code, set it to load on that page, in the Head.

Squarespace

Edit the page, add a Code block at the bottom, set the mode to HTML, and paste the block. Save. For a sitewide FAQ, use Settings → Advanced → Code Injection → Header instead.

GoDaddy Website Builder

GoDaddy’s Websites + Marketing builder documents custom HTML through an HTML section placed on a page, not a site-wide header field. Add the section to the page and paste the block there. If you cannot find that section on your product, send us the product name and plan rather than guessing at a settings path that may not exist on your account.

Custom or developer-built site

Hand the block to whoever manages your code and ask them to place it inside the <head> of the relevant page. It is inert markup and cannot break the page.

Step 4: Validate the markup in Schema.org Validator

Use Schema.org Validator for this one, not Google’s Rich Results Test. The two tools do different jobs. Schema.org Validator checks generic Schema.org vocabulary and syntax. The Rich Results Test only checks types that are currently eligible for a Google rich result, and FAQ is no longer one of them, so a clean page can look like a failure there.

Paste the live URL of the page and run it. You want the FAQPage type recognized, your questions and answers listed back to you, and zero errors. If the tool shows markup whose wording does not match the visible text on the page, fix the page or the markup until they agree.

Do this on the live page, not a draft. If you just published, give it a minute and run it again.

Be clear about what a clean result means. It confirms your markup is well-formed and matches the page. It is not a ranking, a rich result, or an AI citation, and no tool can confirm those.

That is the whole job. Clear answers a homeowner can read, described accurately for anything reading the page on their behalf. If you would rather have this done across every page of your site instead of one at a time, our team implements it for you. The Score is free and shows you where the gaps are first.

Common questions

Will FAQ schema get me into Google's AI Overviews?

No. Google says its AI features need no special AI markup or files, and it retired the FAQ rich result in May 2026. Clear, accurate, crawlable answers are what an engine can use. Nothing you add to a page guarantees a citation.

Do the questions on the page have to match the schema exactly?

Yes. The questions and answers in your JSON-LD must match visible text on the same page. Mismatched or hidden FAQ markup violates Google's guidelines and can cause a manual action.

How many FAQs should I add?

Start with three to six genuine questions per page. Padding the markup with questions no customer asks adds no value and can read as spam.

Rather have it done for you? Start with the free Score to see exactly where your site stands, then decide.

Get Your Free Score →