# Mark up builder FAQs only after the answers are right

FAQ schema describes questions and answers a buyer can already read on the page. Pick the questions buyers ask at plan review, selections and the warranty walk. Write the answers from your own documents. Generate the markup from the visible text so the two never drift. Check Google's current FAQPage documentation before you add it or keep it.

## Which builder questions belong in a marked-up FAQ?

Use the questions that follow from the page. A plan page answers what can change, what lot information you need and whether the photographed options are standard. A warranty page explains the request channel, the information needed and how you separate punch items from later requests.

Do not add a question because it contains a search phrase. The section exists to remove a buyer's uncertainty and reflect how you work.

### Choose questions from field evidence

| Page | Useful question source | Answer reviewer |
| --- | --- | --- |
| Plan page | Plan review and lot-fit meetings | Design or preconstruction lead |
| Allowance guide | Specification and selections discussions | Estimator or selections lead |
| Build process page | Buyer updates, draws and site-access questions | Construction lead |
| Completion page | Walkthrough and punch-list preparation | Project lead |
| Warranty page | Request intake and owner handoff | Warranty lead |

Strip names from the notes before you use them. The public answer explains the process without exposing a buyer's situation or contract detail.

## How should a builder write the answers?

Answer in the first sentence. Add only the context that prevents a misunderstanding. If the answer depends on the plan, the lot, the contract or a current document, say what the team reviews instead of forcing a universal statement.

1. **Collect the exact question.** Preserve the language buyers use.

2. **Identify the operating source.** Find the plan set, specification, process note or warranty document behind the answer.

3. **Name the responsible reviewer.** Route technical and scope answers to the person accountable for them.

4. **Draft a direct response.** Put the usable answer before background explanation.

5. **Check implied promises.** Remove assumptions about availability, schedule, cost or coverage.

6. **Publish visibly.** Make the same question and answer available to the reader.

Have the reviewer mark any exception that must stay in both the visible answer and the structured copy.

## Where should FAQ sections appear on a builder site?

Put a short FAQ near the end of the page it supports. The questions settle what is left after the main explanation. One large FAQ page can still work as an index if it links to the deeper pages instead of repeating every subject in shallow form.

- Plan pages can answer lot-fit, option and image questions.

- Community pages can answer builder fit, plan availability and inquiry questions when current.

- Process pages can clarify responsibilities, documents and handoffs.

- Project pages can distinguish completed examples from active offerings.

- [Warranty pages](/guides/warranty-and-aftercare-pages/) can explain request preparation and communication channels.

Keep questions page-specific. If an answer appears on several pages, record each location so a source change reaches every visible and structured copy.

## How does the visible FAQ become structured data?

The markup reproduces the visible questions and answers in machine-readable form. Generate it from the same source as the page. Punctuation, wording and updates then stay in step.

Before you publish, check eligibility, content restrictions and supported display in Google Search Central's current FAQPage documentation. Do not rely on an old checklist or assume the markup will produce a particular result. [Structured data](/glossary/schema-markup/) describes the content. The search engine decides what to do with it.

The [home builder schema article](/articles/search-and-answer-engines/schema-for-home-builders/) covers organization, website, breadcrumb and article markup. The [schema markup](/glossary/schema-markup/) glossary entry has the base definition.

### What should the publishing check catch?

A builder FAQ needs an operating review and a parity test. In a local preview, change one approved answer and regenerate the page. Compare the visible answer with the structured one, conditions and links included. If either still holds the old text, fix the shared source or the generator before release.

| Check | What to verify |
| --- | --- |
| Visibility | Every marked-up question and answer appears on the page |
| Accuracy | The responsible person approved the current answer |
| Consistency | Markup and visible wording match |
| Scope | The answer does not add unsupported service or warranty claims |
| Syntax | The rendered structured data passes the chosen validation check |
| Maintenance | The page has a review trigger tied to operational change |

Our agents compare visible answers with structured values, flag duplicate questions and check links. People supply the sources and review every output. Warranty coverage, contract interpretation and plan feasibility stay with the responsible person.

## How should builder FAQs stay accurate?

Tie each FAQ group to a source owner and a change trigger. A revised [allowance schedule](/glossary/allowance-schedule/) triggers the allowance answers. A new plan option structure triggers the plan FAQs. A change in warranty intake triggers the warranty page and any [handoff](/process/handoff/) page that points to it.

Remove stale questions. Do not keep them for page length. If an answer now needs a full explanation, give it its own page and leave a short summary plus a link in the FAQ.

The [Semantic content stage](/process/semantic-content/) places these questions inside the wider builder knowledge map. The [process article method](/articles/search-and-answer-engines/writing-process-articles/) says when a recurring question deserves a full page. The other [search and answer engine articles](/articles/search-and-answer-engines/) cover the connected subjects.

## Questions about FAQ schema on builder sites

### Does FAQ schema guarantee a search feature?

FAQ schema should not be treated as a promise of a search feature. Check eligibility and presentation with the search engine’s current FAQ structured-data documentation.

### Can the markup contain a shorter answer than the page?

Generate the structured FAQ answer from the visible answer to avoid drift. Compare both after edits, including any links, conditions or exceptions needed to preserve meaning.

### Should every page have an FAQ?

A builder page needs an FAQ when readers have recurring follow-up questions about its subject. Avoid adding questions that merely repeat the body or unrelated page topics.

### Who should review warranty FAQ answers?

The person responsible for the builder’s warranty process should approve warranty FAQ answers against current documents and intake procedures before markup is generated.