Add FAQ Schema So AI Engines Cite Your Restoration Company
The steps
- Write three real customer questions and answers
- Build the FAQ schema block
- Add the code to your site
- Test it in the Rich Results Test
Most restoration websites answer customer questions in paragraphs. A search engine can read that text, but an AI assistant deciding what to quote prefers a clean, labeled question-and-answer pair. FAQ schema gives it exactly that. This guide adds a valid FAQPage block to one of your pages in about twenty minutes, with no developer.
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, honest 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.
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 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 builder limits raw code. Add an HTML / Embed section if your plan includes it and paste the block. If your plan does not allow custom HTML, this is a sign you have outgrown the builder for SEO, and a platform that allows code injection will serve you better.
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: Test it in the Rich Results Test
Go to Google’s Rich Results Test, paste the live URL of the page, and run it. You want to see FAQ detected with a green check and zero errors. If it reports the markup but cannot find matching visible text, add the questions and answers to the page body and retest.
Do this on the live page, not a draft. If you just published, give it a minute and run it again.
That is the whole job. You now have answers a machine can quote, on a page a homeowner can read, verified by Google’s own tool.
Common questions
Will FAQ schema get me into Google's AI Overviews?
Schema does not guarantee a citation. It makes your answers machine-readable, which is a precondition for being quoted. Google and AI assistants still choose what to cite based on relevance and trust.
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 →