# FAQ Page: How to Build One for Free, With a Schema Example

> Build an FAQ page from your real support questions, publish it free in Google Sites, add FAQ schema, and know when a help center should take over.

_Source: https://professionalstoolkit.com/articles/faq-page — The Professional's Toolkit · updated November 2026_

---

An FAQ page is a single page that answers the questions customers already ask you, in their own words, grouped by topic so each reader finds theirs in seconds. The do-it-yourself method takes an afternoon: pull the real questions from your inbox, write a direct answer for each, and publish them as collapsible sections on a free page such as Google Sites. That page stays useful until the list outgrows one screen or you can no longer tell which questions it failed to answer. Then a help center tool takes over.


**May 7, 2026** — The day Google stopped showing FAQ rich results in Search



- **1982** — Year the FAQ format began, per Nielsen Norman Group
- **62 of 100** — Emails covered by five topics in our shop illustration
- **10 articles** — Cap on Help Scout's Free Docs site


## Where your FAQ questions should come from

The fastest way to ruin an FAQ page is to invent the questions. Nielsen Norman Group has warned against made-up questions for years, and it advises writing in your users' vocabulary, because people search for their problem, not for your solution [1]. So the list starts in your support inbox, not in a brainstorm. Sales calls, chat transcripts and the replies you keep retyping are the other sources worth an hour.

1. **Pull a sample.** Take your last 100 customer emails or chats, or a full month if you get fewer.
2. **Tag each one** with a short topic: shipping, returns, billing, account, product use.
3. **Count the tags.** The top five to ten topics are your first FAQ.
4. **Copy the customer's phrasing** for each question, then trim it until it applies to most people.
5. **Drop the one-offs.** A question asked once is a ticket, not an FAQ.

Keep that tally after launch. It is your baseline. If the same topics keep arriving once the page is live, the answer is missing, buried or wrong. Nobody reads a page they can't find, so that is the first thing to check.


> 💡 **Mine your sent folder first:** Any reply you have typed more than three times is an FAQ answer already written. Clean it up and publish it.


## How to write answers people can scan

Good FAQ web page design is mostly writing, not visuals. Each question is a heading the reader can skip past. The first sentence of the answer settles it; the rest adds conditions and exceptions. If an answer needs more than a short paragraph and a small list, it deserves its own article, with the FAQ entry linking to it. That split is how an FAQ grows into a knowledge base, which our [guide to building a knowledge base](/articles/how-to-build-a-knowledge-base) covers in full.

### Rules that hold on every FAQ page

- **Group by topic**, most-asked group first, so readers can rule out whole sections at a glance.
- **Lead with the answer.** Yes, no, a number of days, or the one action to take.
- **Write the question the way a customer types it.** *Where is my order?* beats *Order fulfillment status*.
- **One question per heading.** Two questions under one heading get half an answer each.
- **End with a way out.** A contact link under the last group catches whatever the page missed.
- **Date it.** A last-updated line tells readers the answers are current.

Short answers also travel well. An agent can paste one into a reply, a chatbot can quote it, and a search engine can match it to the exact question someone typed. Long answers do none of that. Aim for two to four sentences per answer and a link where more is needed.


> ⚠ **Keep policy wording in one place:** If the FAQ says one return window and the policy page says another, customers will quote whichever suits them. Link the policy instead of restating its terms.


## How to build an FAQ page in Google Sites, step by step

Google Sites is free with a Google account and has a built-in collapsible text block, which is exactly the shape an FAQ needs: the question shows, and the answer opens on a click. Google's own help page gives these steps [2]:

1. On your computer, open a site in Google Sites.
2. On the right, click **Insert**, then **Collapsible text**.
3. Click the text boxes to add the heading (your question) and the body (your answer).
4. Repeat steps 2 and 3 for each question. Above each topic group, add an ordinary heading: on the right, click **Insert**, then **Text box**.
5. To check the result, click **Preview** at the top right.
6. To publish your changes, click **Publish** at the top right.

To edit later, click the heading to expand it, then click the heading or body text box. To turn a block back into ordinary text, point to the top of the box, click the blue outline to select the group, and turn off Collapsible. The same help page notes that you can use an anchor link to send someone to a specific header on a published site. With it, an agent can answer an email with a link to one answer instead of retyping it.


> 💡 **Link one answer, not the page:** Use an anchor link to the exact question when you reply to a customer. They land on the answer instead of scrolling for it.


If your website runs on another builder, look for its accordion or toggle block. The tool changes; the writing rules above do not. Link the finished page from your site footer and your contact page, since that is where people go when they are stuck.

## FAQ page schema example, and what Google changed in 2026

FAQ schema is structured data, usually JSON-LD, that labels each question and answer for machines. For years it could earn an expandable FAQ snippet under your Google result. That has now ended. Google announced that the FAQ rich result would no longer appear in Google Search starting May 7, 2026, and later removed its documentation for the feature [3].

Should you still add it? The markup is short and harmless, and it states your questions and answers in a form other software can read. Just don't expect a richer Google listing from it. Here is a minimal FAQ page schema example with two questions, placed inside a script tag of type application/ld+json in the page's HTML:

```json
{"@context": "https://schema.org",
 "@type": "FAQPage",
 "mainEntity": [
  {"@type": "Question", "name": "Where is my order?",
   "acceptedAnswer": {"@type": "Answer", "text": "Use the tracking link in your shipping email."}},
  {"@type": "Question", "name": "How do I return an item?",
   "acceptedAnswer": {"@type": "Answer", "text": "Start a return from your account."}}
 ]}
```

Keep the markup identical to the visible text. If they drift apart, you are describing a page that doesn't exist. And if your site builder gives you no way to add code to the page itself, skip the markup. A clear, well-ordered page matters far more.

## FAQ page examples: a small shop's first five questions

Here is an illustration with round, invented numbers. An online clothing shop answers about 400 emails a month. The owner tags a sample of 100 and finds five topics that cover 62 of them.

| Topic | Emails in the sample | Question as customers write it | First line of the answer |
|---|---|---|---|
| Order status | 25 | Where is my order? | Use the tracking link in your shipping email. |
| Returns and exchanges | 15 | How do I return an item? | Start a return from your account. |
| Shipping times | 10 | How long does shipping take? | Most orders arrive in 3 to 5 business days. |
| Address changes | 7 | Can I change my address after ordering? | Yes, until the order ships; reply to your confirmation email. |
| Sizing | 5 | Which size should I pick? | Check the size chart on each product page. |

Suppose the page settles half of those 62 for good. That is 31 fewer emails per 100, or about 124 a month at 400. The real figure will be lower. Some customers write anyway, and some questions need an order number only an agent can look up. The lesson is the order of work. Write the five answers that cover most of the volume before the twenty that cover the rest.

## When a homemade FAQ stops keeping up

The free page breaks at a predictable point. Watch for these signs:

- **It outgrows one screen.** Past roughly 25 to 30 questions, or a second product line or language, scanning stops working. That threshold is our rule of thumb, not a standard.
- **Two people edit it**, and nobody knows which answer is current.
- **You can't see failed searches.** Questions customers looked for and didn't find stay invisible.
- **Agents still retype answers**, because the FAQ isn't next to the ticket they are working on.
- **Answers go stale quietly.** The FAQ lives in one place and the tickets in another, so nobody notices the drift.

At that point the job is a help center: searchable articles, a widget that suggests them, and reports on what people failed to find. The gentlest step up is Help Scout, whose Docs site exists on every plan, Free included; our walkthrough shows how to [set up a Help Scout Docs site](/articles/help-scout-docs). Freshdesk lets an agent [turn a ticket reply into a draft article](/articles/freshdesk-knowledge-base) by adding the knowledge base address in BCC. Zendesk's [help center](/articles/zendesk-help-center) adds a Knowledge dashboard that shows searches with no result. Our [comparison of knowledge base software](/articles/knowledge-base-software) covers the wider field.


### Help Scout — solves this

Move each FAQ answer into a Docs article; the Beacon widget then suggests articles on the page a customer is viewing, and the Docs report shows failed searches and article ratings.

- Where it stops: The Free plan includes one Docs site with up to 10 articles; custom branding starts on Standard.
- Plan: Free (Docs); Standard for custom branding
- How Help Scout does it: [Set up a Docs site](https://professionalstoolkit.com/articles/help-scout-docs)
- More: [Help Scout](https://professionalstoolkit.com/tools/help-scout)



### Freshdesk — solves this

Agents add the knowledge base address in BCC to turn a good reply into a draft article, and the customer portal suggests articles while a customer types the ticket form.

- Where it stops: Knowledge base reports and multilingual articles need Pro; no free plan, trial only.
- Plan: Growth (customer portal with your own domain)
- How Freshdesk does it: [Set up the portal and articles](https://professionalstoolkit.com/articles/freshdesk-knowledge-base)
- More: [Freshdesk](https://professionalstoolkit.com/tools/freshdesk)



### Zendesk — solves this

The help center organizes answers into categories, sections and articles; Knowledge builder drafts articles from past tickets, and the Knowledge dashboard shows searches with no result.

- Where it stops: Not on Support Team; Suite Team has one language; no free plan.
- Plan: Suite Team (help center); Suite Professional for multilingual
- How Zendesk does it: [Build a Zendesk help center](https://professionalstoolkit.com/articles/zendesk-help-center)
- More: [Zendesk](https://professionalstoolkit.com/tools/zendesk)



## FAQ

**Does an FAQ page help SEO?**

It can. Questions written in customers' own words match what people type into search engines, and the content can be indexed. Google no longer shows the FAQ rich result, so the benefit comes from the page itself, not the markup.

**What is the difference between an FAQ page and a knowledge base?**

An FAQ page is one page of short answers to the most common questions. A knowledge base is a searchable set of full articles, usually with categories, a search box and reports on what people looked for.

**How often should I update my FAQ page?**

Recount your inbox topics every month or two, and edit the page whenever a policy, price or process changes. Show a last-updated date so readers trust the answers.


## The bottom line

A useful FAQ page is built from your inbox, not your imagination. Tag a sample of real messages, answer the top topics in one direct sentence each, group them, and publish them as collapsible sections on a free page such as Google Sites. Add FAQ schema only if it is easy, since Google no longer shows the FAQ rich result. Recount your inbox a month later. When the page outgrows one screen, needs a second editor, or hides which questions it misses, move the answers into a help center tool that reports on failed searches.



## Sources

[1] Nielsen Norman Group — https://www.nngroup.com/articles/faqs-deliver-value/ (Nov 2026)
[2] Google Help — https://support.google.com/sites/answer/90538?hl=en (Nov 2026)
[3] Google for Developers — https://developers.google.com/search/updates (Nov 2026)