Website Examples
FAQ Page Examples: 18 Real FAQ Pages and What They Include
Real FAQ page examples, counted: questions, topic groups, accordion or open answers, search and schema, plus a copyable HTML FAQ section and checklist.
A good FAQ page includes the questions customers really ask, in their words, each with a short direct answer, sorted into topic groups once the list gets long, with links to the pages that hold the detail and a way to reach a person when the answer is missing. This page collects 18 real FAQ page examples from remodelers, a cleaning company, a dental group, restaurants, a law firm, online stores, software companies, nonprofits, a national park, and a concert venue, and counts what each one contains: how many questions, how many groups, accordion or open answers, search, structured data, and where unanswered questions go. After the examples come the patterns, when an FAQ page is worth having, what Google does with FAQ markup in 2026, a text wireframe, a copyable HTML FAQ section, and a checklist. It is part of the website examples library.
Jump to: the comparison table · examples by type · patterns · do you need one · Google and FAQ schema · accordion or open · wireframe · HTML · FAQ
What should be included in FAQ?
An FAQ page needs six things:
- Real questions: the ones that arrive by email, phone, and at the counter, phrased the way customers phrase them
- Short direct answers: the answer in the first sentence, detail after it
- Topic groups with headings once the list passes about 20 questions, so a visitor can skip most of the page
- Links from answers to the page that holds the full detail (pricing, delivery, booking, returns)
- A route for unanswered questions: a sentence and a link to your contact page, an email address, or a phone number
- Text that is in the HTML: questions and answers a browser, a search engine, and a screen reader can all read without running a script
Optional: a list of jump links at the top of a long page, a search box if you have dozens of questions, and an "expand all" control if you use an accordion.
FAQ page examples at a glance
Every page below is a real, live FAQ page. Each was fetched on 2026-11-19 and read as HTML, so the counts describe what the page sends to the browser. "Questions" counts question elements in the FAQ itself, not questions inside answers or in menus. "FAQ search" means a search box for the FAQ, not the site-wide search in a header. "FAQPage JSON-LD" means the string FAQPage appears in the page's structured data.
| FAQ page | Type | Questions | Topic groups | Format | FAQ search | FAQPage JSON-LD | Prompt for unanswered questions | Links in answers |
|---|---|---|---|---|---|---|---|---|
| Hammer & Hand | Builder and remodeler, Portland and Seattle | 66 | 10 | Script accordion | No | No | None on the page | Yes |
| Sun Design | Design-build remodeler, Northern Virginia | 18 | None (plus 10 topic cards) | <details> for 15, 3 open | No | Yes | "Have a Question About Your Home?" | Yes |
| Dashing Maids | House cleaning, Denver | 13 | None | <details> | No | Yes | "Still curious?" | No |
| Tend | Dental studios, several cities | 40 | 6 | Script accordion | No | Yes | None after the list (footer only) | Yes |
| Alinea | Restaurant, Chicago | 18 | 4 | Script accordion | No | No | "If you have additional questions, please email" | Email and one external link |
| Levain Bakery | Bakery with an online shop | 45 | 7 | Groups collapse, answers open | No | No | "I HAVE ANOTHER QUESTION." | Yes |
| Stange Law Firm | Law firm, several states | 7 | None | Script accordion | No | No | None (a general contact section follows) | Yes |
| Xendoo | Online bookkeeping and accounting | 33 | 8 | <details> | No | Yes | None (a consultation button follows) | Yes |
| Designjoy | Design subscription, one person | 14 | None | Script toggle, section on the homepage | No | No | "Prefer to email?" | No |
| Studio Neat | Pens and notebooks, online store | 66 | 8 | All open | No | No | None (email in the footer) | Yes |
| Ugmonk | Independent online store | 15 | 4 | <details> | No | No | "If you have a question that isn't answered below" (at the top) | Yes |
| Intelligentsia Coffee | Coffee roaster and online store | 52 | 4 | Script accordion | No | No | None (Contact Us in the footer) | Yes |
| Pinboard | Bookmarking service | 98 | 16 | All open, with a question index | No | No | None (support email inside an answer) | Yes |
| Oh Dear | Website monitoring service | 88 links | 7 | Index: each question links to its own page | Yes | No | "Can't find what you're looking for?" (at the top) | Every question is a link |
| San Francisco SPCA | Animal shelter and veterinary hospital | 51 | 4 | Script accordion | No | No | "Still have questions?" (one group only) | Phone, email, external |
| SF-Marin Food Bank | Food bank | 11 | None | Script accordion | No | No | None | Yes |
| Yellowstone National Park | U.S. National Park Service | 15 | None (plus 15 links to topic FAQs) | All open | No | No | None (contact details in the footer) | Yes |
| Red Rocks Amphitheatre | Concert venue and park, City of Denver | 0 (21 topics) | 21 | Open, with expand buttons for mobile | No | No | None | Yes |
"Script accordion" means the answers are in the HTML but opening and closing them depends on JavaScript. <details> means the page uses the browser's built-in disclosure element. Sites change, so a page may have been edited since the check.
FAQ page example: 18 real pages by type
The descriptions below are limited to what is in each page's HTML: headings, questions, markup, links, and stated text. Nothing here states prices, ratings, or results.
Local service businesses
Local businesses use the FAQ to answer the questions that come before a booking: cost, timing, service area, and what happens on the day.
Hammer & Hand: hammerandhand.com/faq/
| Field | Observation |
|---|---|
| Type | Builder and remodeler with Portland and Seattle offices |
| Questions | 66, each an accordion title, from "What does Hammer & Hand do?" to "Will there be a dedicated project manager overseeing my project?" |
| Groups | 10 headings: About Us, New Home Build, Kitchen Remodels, Bathroom Remodels, Basement Remodels, Condo Remodels, ADUs, Passive House Doors, Commercial Projects, and General |
| Other | A "Table of Contents" block; answers link to the start-a-project form, with the note that it "does not commit you to anything, nor does it put you on a mailing list" |
| What to copy | One group per service, so a kitchen customer never scrolls through commercial questions |
Sun Design: sundesigninc.com/design-build-remodeling-faqs/
| Field | Observation |
|---|---|
| Type | Design-build remodeler, Northern Virginia and the DC area |
| Questions | 15 in <details> elements with the first one open, introduced with "Start here. These are the fifteen questions that come up in nearly every first conversation we have with a homeowner.", plus 3 open questions under "Real Homes, Real Solutions" that each link to matching portfolio projects |
| Groups | None for the 15; below them, 10 topic cards for dedicated FAQ pages, 9 marked "Coming soon" and 1 live |
| Contact | A closing section, "Have a Question About Your Home?", with a "Schedule a Conversation" button |
| What to copy | The count in the intro (fifteen questions is a promise the reader can check) and answers that end in a link to real work |
Dashing Maids: dashingmaids.com/faqs
| Field | Observation |
|---|---|
| Type | House cleaning company, Denver |
| Questions | 13 in <details> elements, one list, no groups: cost, whether you need to be home, pets, the oven, sheets, dishes, insurance, payment, and "Should I tip the maids?" |
| Contact | A side card headed "Still curious?" with a tel: link and a link to the contact page |
| Other | FAQPage structured data; no links inside the answers |
| What to copy | The length. Thirteen everyday questions answered in a sentence or two each is a complete FAQ for a local service |
Tend: hellotend.com/site/faqs
| Field | Observation |
|---|---|
| Type | Dental studios in several cities |
| Questions | 40 accordion items under 6 categories: Booking, Your Visit, Insurance, Studio, Teeth Whitening, and Billing |
| Navigation | A "Categories:" row of jump links at the top, one per group |
| Contact | Nothing after the last question; the footer has a "Questions?" block with a phone number and an email address. Many answers end with a tel: link, and others link to the services and insurance pages |
| What to copy | Category jump links above a long accordion, and phone links inside the answers where a call is the real next step |
Alinea: alinearestaurant.com/faq
| Field | Observation |
|---|---|
| Type | Restaurant, Chicago |
| Questions | 18 accordion items in 4 groups: Booking FAQs (6), General FAQs (6), Wine FAQs (3), and Gift Card FAQs (3) |
| Contact | The page ends with "If you have additional questions, please email" and a mailto: link; individual answers give separate addresses for the host and the wine team |
| What to copy | Policy questions (late arrival, cancellation, rescheduling, dress code, service charge) answered before the guest has to ask. The restaurant website examples cover the rest of a restaurant site |
Levain Bakery: levainbakery.com/pages/faq
| Field | Observation |
|---|---|
| Type | Bakery with shops and nationwide shipping |
| Questions | 45 under 7 groups: Levain Bakery Locations, Cookies & Cookie Gift Boxes, Nationwide Shipping, Promotions & Discounts, Large Orders + Party Favors, Local Delivery or Pick Up, and Other |
| Format | The reverse of the usual accordion: each group is one <details> element, and inside an open group every question and answer is visible |
| Contact | The last entry is "I HAVE ANOTHER QUESTION.", which links to the contact form with the line "a Levain team member will get back to you within 24-48 business hours" and lists separate emails for orders and press |
| What to copy | Collapsing by topic instead of by question, and a final entry that is the contact route |
Professional services
Professional firms answer fewer questions, and most are about money, process, and the first meeting.
Stange Law Firm: stangelawfirm.com/faq/
| Field | Observation |
|---|---|
| Type | Law firm with offices in several states |
| Questions | 7 in one accordion: "What do you charge?", whether the other side can be made to pay fees, court-appointed attorneys, how long a case takes, scheduling, phone or video consultations, and what to bring |
| Contact | An answer links to the contact page ("contact us online"), and a "Contact Our Team" section follows the list |
| What to copy | Starting with the fee question. It is the first thing a prospective client wants to know |
Xendoo: xendoo.com/faq/
| Field | Observation |
|---|---|
| Type | Online bookkeeping and accounting service |
| Questions | 33 in <details> elements under 8 headings: Bookkeeping, Payroll, Accounting Methods, ECommerce, Deductions, About Us, Services, and Plans |
| Other | FAQPage structured data; some answers link to partner pages; the page closes with a "Schedule a Free Consult" button |
| What to copy | Native <details> under plain headings: an accordion with no script to load or break |
Designjoy: designjoy.co
| Field | Observation |
|---|---|
| Type | Design subscription run by one person ("Designjoy is a one-man agency, ran by Brett, the founder.") |
| Questions | 14, in a "Frequently asked questions" section on the homepage, not a separate page |
| Format | Click-to-open rows; the answers are in the HTML and hidden until a script shows them |
| Contact | Two cards in the same section: "Book a 15-min intro call" and "Prefer to email?" with the address |
| What to copy | An FAQ section instead of an FAQ page, covering speed, scope, pausing, and refunds |
Online stores
Store FAQs are the longest in this list after the software pages, because they cover shipping, returns, payment, and every product.
Studio Neat: studioneat.com/pages/faq
| Field | Observation |
|---|---|
| Type | Maker of pens and notebooks with an online store |
| Questions | 66, all open, as bold paragraphs: 10 under "General FAQs" and the rest under 7 product headings (Mark One, Mark Two, Mark Three, Keepbook, Panobook, Panopad, Totebook) |
| Other | "What is Cerakote?" is repeated under each of the three pens, so each product block stands alone; answers link to refill guides and the custom-order page. One answer reads "When we say no asterisks, we really mean it." |
| What to copy | No accordion at all. Bold questions, one-paragraph answers, product headings |
Ugmonk: ugmonk.com/pages/faq
| Field | Observation |
|---|---|
| Type | Independent online store |
| Questions | 15 in <details> elements under 4 headings: Shipping & Returns (7), Payments (2), Products (2), and About Ugmonk (4) |
| Contact | At the top, before any question: "If you have a question that isn't answered below, feel free to email us directly:" followed by a mailto: link |
| What to copy | The contact line first. A visitor who already knows their question is unusual does not have to read 15 answers to find the email address |
Intelligentsia Coffee: intelligentsia.com/pages/faqs
| Field | Observation |
|---|---|
| Type | Coffee roaster with coffeebars, an online store, and subscriptions |
| Questions | 52 accordion buttons under 4 numbered groups: "01. Coffee" (20 questions), "02. Shopping & Shipping", "03. Coffeebars", and "04. Subscriptions" |
| Other | Each question is a real <button>; answers link to the locations page and give the support email |
| What to copy | Product education and order questions on one page, with the education group first |
Software
Software FAQs are reference material, and both examples here are built to be scanned or searched, not read.
Pinboard: pinboard.in/faq/
| Field | Observation |
|---|---|
| Type | Bookmarking service, run by its founder ("I founded the site in 2009 and work on it full-time.") |
| Questions | 98, every answer open, under 16 headings from General and Payment to Troubleshooting and Anxieties |
| Navigation | The page starts with an index of every question as a jump link, grouped under the same headings |
| Contact | No closing prompt; the General group answers "How can I get help?" with "The quickest way to get support is by emailing me at" and a mailto: link |
| What to copy | The index. With 98 questions, a list of links at the top does the job a search box would |
Oh Dear: ohdear.app/docs/faq
| Field | Observation |
|---|---|
| Type | Website monitoring service |
| Questions | 88 links in 7 panels: General, Uptime, Our Crawler, Notifications, Cron Job Monitoring, Billing & Account, and Status Pages. The page holds no answers; each question links to its own page |
| Search | A "Search the FAQ..." box under the heading, the only FAQ search in this list |
| Contact | In the intro: "Can't find what you're looking for? Contact our support team." |
| What to copy | One page per question once answers get long, with an index page to hold them together. The SaaS website examples show where docs and FAQ links sit on software sites |
Nonprofit, government, and venue
San Francisco SPCA: sfspca.org/frequently-asked-questions/
| Field | Observation |
|---|---|
| Type | Animal shelter and veterinary hospital |
| Questions | 51 accordion items under 4 headings: Veterinary Care & Clinic FAQs, Adoption FAQs, Behavior FAQs, and Returns FAQs |
| Format | Each question is a <button> with aria-expanded inside an <h3>, the structure the accordion guidance below asks for |
| Contact | The veterinary group ends with a "Still have questions?" item giving the pharmacy's phone, text, and email |
| What to copy | The button-in-a-heading markup if you build a scripted accordion |
SF-Marin Food Bank: sfmfoodbank.org/faq/
| Field | Observation |
|---|---|
| Type | Food bank, San Francisco and Marin |
| Questions | 11 in one accordion, no groups, opening with "How can someone access a Food Bank pantry or program?" and ending with "How can I help?" |
| Other | The first answer links to the food locator |
| What to copy | Order. The question from someone who needs food comes first, the donor question last |
Yellowstone National Park: nps.gov/yell/faqs.htm
| Field | Observation |
|---|---|
| Type | U.S. National Park Service park page |
| Questions | 15, all open: each question is a bold line with the answer under it in the same paragraph |
| More | Two link lists below, "Additional Nature and History Frequently Asked Questions" (7 links) and "Additional Area Frequently Asked Questions" (8 links), send detailed questions to topic pages |
| What to copy | A short general FAQ that hands off to topic pages instead of growing without limit |
Red Rocks Amphitheatre: redrocksonline.com/plan-your-visit/faq/
| Field | Observation |
|---|---|
| Type | Concert venue and park, a City of Denver venue |
| Questions | None. Under the line "You've got questions, we've got answers", the page has 21 topic sections (Hours, Ticketing, Weather, Parking, Seating, Alcohol, Pets, Lost and Found, and more), each a bulleted list of facts |
| Format | Sections are open, with a button per topic used to expand them on mobile |
| What to copy | Topics instead of questions when visitors look things up by subject. Nobody has to guess how the venue phrased the parking question |
FAQ section examples: how our demos do it
Our fictional example sites do not have FAQ pages. They put a short FAQ section on the page where the questions come up, each under a "Common questions" heading, with every question in a native <details> element.
- Veterinarian, new patients: 4 questions after the visit steps, from "Do you see cats and dogs?" to "What should I bring to the first visit?"
- Accountant, fees: 4 questions under the fee table, including "How quickly do you respond?" and "Can you catch up on old books?"
- Catering company, quote: 4 questions beside the quote form: the event minimum, staffing, how far ahead to book, and rentals
- Construction company, process: 4 questions under the process steps: cost, build time, licensing, and working with the client's architect
- Chiropractor, new patients: 4 questions, including "Do I need a referral?" and "How many visits will I need?"
Four questions per page, five pages: 20 answers that never needed an FAQ page, because each sits where the visitor is already reading about that subject.
What the examples have in common, and where they differ
The counts below come from the table above, 18 pages checked on 2026-11-19.
- Length splits into two camps. 17 pages have countable questions, from 7 (Stange Law Firm) to 98 (Pinboard), with a median of 33. Eight pages have 18 or fewer, eight have 40 or more, and only Xendoo sits between.
- Long pages group, short pages do not. 12 of 18 sort their content into topic groups. All 9 pages with 33 or more questions use groups. Of the 8 pages with 18 or fewer, 6 are a single list (Alinea and Ugmonk are the exceptions).
- Most collapse the answers. 12 of 18 hide each answer until its question is clicked: 8 with a scripted accordion and 4 with native
<details>elements. 4 show everything open (Studio Neat, Pinboard, Yellowstone, Red Rocks), Levain collapses whole topics instead of questions, and Oh Dear links each question to its own page. - FAQ search is rare. 1 of 18 has a search box for the FAQ (Oh Dear, with 88 questions). Pinboard handles 98 with an index of jump links. Tend and Hammer & Hand also put jump links or a table of contents above the list.
- A prompt for unanswered questions appears on fewer than half. 8 of 18 have one, and 2 of those put it at the top (Ugmonk, Oh Dear). The other 10 leave the visitor to find the footer or a general call to action.
- Answers link out. 16 of 18 link from at least one answer to another page, an email address, or a phone number. Dashing Maids and Designjoy keep every answer as plain text.
- FAQ structured data is a minority choice. 4 of 18 include
FAQPageJSON-LD (Sun Design, Dashing Maids, Tend, Xendoo). The section on Google explains why the other 14 lose nothing in Google Search. - One page has no questions at all. Red Rocks calls the page FAQ and organises it by topic.
Do you need an FAQ page?
Not always. Put each answer on the page it belongs to first, and add an FAQ page when you have questions with no obvious home or enough of them that people need one place to scan.
That is where the forum discussion lands. In a UK Business Forums thread on FAQ pages from May 2024, a business owner asks whether there is any benefit to creating one and whether it has to be a dedicated page. A moderator answers that in most cases an FAQ page gives no search benefit and asks whether the answers would be better on the relevant page. Another member replies that FAQs grouped into sections are usually the good ones.
Both replies fit the examples. Our demos and Designjoy answer questions on the page where they arise. The dedicated pages that work best here are the grouped ones, where a visitor can rule out most of the page from the headings.
The Nielsen Norman Group makes the case for keeping an FAQ in FAQs Still Deliver Great Value: "many people already know to look for an FAQ when they need a fast answer", and "good, large FAQs are chunked by topic and designed to be visually scanned." The same article warns against made-up questions: "If you’re listening to your users, you know what their questions are."
A practical rule:
- Answer on the relevant page when the question is about that page's subject: delivery times on the delivery page, fees on the fees page, what to bring on the new-patients page
- Add an FAQ section to a page when four or five questions keep coming up about it, as in our demos
- Add an FAQ page when you have general questions that fit nowhere else (who you are, where you work, how payment works), or when support email keeps repeating the same dozen questions
- Skip it if you would have to invent the questions. A page of questions nobody asked is the version of an FAQ that earned the format its bad name
If you do add the page, link it from the footer and from your contact page, where it can catch a question before it becomes an email. The contact page examples show two sites that put the FAQ on the contact page itself. For where the page sits in the menu, see the website structure examples; on a single landing page, the FAQ is a section near the bottom, not a page.
FAQ schema and Google in 2026
Google no longer shows FAQ rich results, so FAQPage markup does nothing visible in Google Search. The dates, from Google's own pages:
- August 8, 2023: the Google Search Central blog announced that FAQ rich results "will only be shown for well-known, authoritative government and health websites."
- May 2026: the Google Search Central changelog entry dated May 8, "Deprecating the FAQ rich result feature", says: "This feature will no longer appear in Google Search starting May 7, 2026."
- June 15, 2026: the changelog records "Removed documentation for the FAQ rich result feature", because "The FAQ rich result feature is no longer shown in Google Search results".
What to do with existing markup: nothing. The 2023 post says "there's no need to proactively remove it" and "Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search." That is the position of the 4 pages in the table that still carry FAQPage JSON-LD.
What this changes for a new page: write the FAQ for visitors. Mark up the questions as headings or <summary> elements so the page is readable and its text is in the HTML. Adding FAQPage JSON-LD is optional and harmless for Google, and it is no longer a way to get a larger search result there.
Accordion or open answers?
Show answers open when the list is short or visitors are likely to read several of them. Use an accordion when the list is long and each visitor needs one or two answers.
That is the Nielsen Norman Group's rule in Accordions on Desktop: When and How to Use: accordions "diminish content visibility and increase interaction cost", so "use accordions for content-heavy pages where users will not need to access content under several accordions." The article adds two build rules: "the accordion heading should function as a button, allowing keyboard users to interact with the element", and "Allow users to open or collapse multiple sections at a time."
Applied to the examples:
- Open works for Yellowstone's 15 questions and Studio Neat's 66, because both are bold questions with one-paragraph answers that scan quickly, and the browser's find-in-page reaches every word
- Accordions work for Tend's 40 and Intelligentsia's 52, where a visitor with a billing question does not want to scroll past whitening
- Jump links are the middle route. NN/g's review of FAQ pages, An FAQ's User Experience Deconstructed, describes them: "Jump links are used to navigate from the question list to the answers below." Pinboard does exactly this for 98 questions
- If you collapse, prefer
<details>. It needs no script, works with a keyboard, and the question is a real control. Four of the examples use it per question
FAQ page design template: the anatomy of an FAQ page
Most of the 18 pages fit one skeleton. The diagram is an illustrative pattern, not a specific site, in the same style as the layouts in the website wireframe example.
+--------------------------------------------------------------+
| HEADER Logo Services About FAQ Contact |
+--------------------------------------------------------------+
| H1 Frequently asked questions |
| One line: what this page covers |
| Can't find your question? -> Contact us |
+--------------------------------------------------------------+
| JUMP LINKS (long pages) |
| Booking · Pricing · Delivery · Returns · About us |
+--------------------------------------------------------------+
| H2 Booking |
| > How do I book? |
| Answer in one or two sentences. -> Booking page |
| > Can I reschedule? |
| > What happens if I am late? |
+--------------------------------------------------------------+
| H2 Pricing |
| > How much does it cost? |
| > How do I pay? |
+--------------------------------------------------------------+
| H2 (more topics, each with 3 to 10 questions) |
+--------------------------------------------------------------+
| STILL HAVE A QUESTION? |
| Email, phone, or a link to the contact page |
+--------------------------------------------------------------+
| FOOTER Address · Phone · Hours · FAQ · Privacy |
+--------------------------------------------------------------+
The sections in order:
- Heading and one line: "Frequently asked questions" or "FAQ", plus what the page covers
- Early contact line: for the visitor whose question is unusual (Ugmonk and Oh Dear put it here)
- Jump links: one per topic, only when the page is long (Tend, Pinboard)
- Topic groups: an
<h2>per topic, most-asked topic first - Questions: the customer's wording, open or collapsed, answer first, link to the detail
- Closing contact block: the same route as the top, for the visitor who read everything
- Footer: with a link back to the FAQ from every page
A short FAQ skips items 3 and 4: heading, 7 to 15 questions, contact line.
FAQ page template (copyable HTML)
The file below is a complete FAQ page in the same plain style as our HTML website example: one <h1>, an <h2> per topic, and one <details> element per question with the question in its <summary>. Save it as faq.html and open it in a browser. No script is needed.
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title>FAQ | Larkspur Café</title>
<meta name="description" content="Answers to common questions about visiting Larkspur Café, ordering ahead, and catering." />
<style>
:root {
--ink: #1f2937;
--muted: #6b7280;
--accent: #b45309;
--paper: #fdfaf5;
--line: #e5e7eb;
}
* { box-sizing: border-box; }
body {
margin: 0;
font-family: Georgia, "Times New Roman", serif;
color: var(--ink);
background: var(--paper);
line-height: 1.6;
}
.container { max-width: 760px; margin: 0 auto; padding: 0 20px; }
header { background: #292524; color: #f5f5f4; }
.header-inner {
display: flex;
align-items: center;
justify-content: space-between;
flex-wrap: wrap;
gap: 10px;
padding: 14px 0;
}
.brand { font-size: 1.3rem; font-weight: bold; margin: 0; }
nav ul { list-style: none; margin: 0; padding: 0; display: flex; gap: 22px; }
nav a { color: #e7e5e4; text-decoration: none; }
nav a:hover, nav a:focus { color: #ffffff; text-decoration: underline; }
main { padding: 40px 0 60px; }
h1 { font-size: 2rem; margin: 0 0 6px; }
.lede { color: var(--muted); margin: 0 0 20px; }
.jump { list-style: none; margin: 0 0 28px; padding: 0; display: flex; flex-wrap: wrap; gap: 8px 18px; }
h2 { font-size: 1.2rem; margin: 32px 0 8px; color: var(--accent); }
details { border-bottom: 1px solid var(--line); }
summary { padding: 12px 0; font-weight: bold; cursor: pointer; }
summary:hover, summary:focus { color: var(--accent); }
details p { margin: 0 0 14px; }
a { color: var(--accent); }
.more { margin-top: 36px; padding: 18px 20px; background: #ffffff; border: 1px solid var(--line); border-radius: 4px; }
.more h2 { margin-top: 0; }
footer { background: #292524; color: #a8a29e; text-align: center; padding: 16px 0; font-size: 0.9rem; }
</style>
</head>
<body>
<header>
<div class="container header-inner">
<p class="brand">Larkspur Café</p>
<nav aria-label="Main">
<ul>
<li><a href="index.html">Home</a></li>
<li><a href="menu.html">Menu</a></li>
<li><a href="faq.html" aria-current="page">FAQ</a></li>
<li><a href="contact.html">Contact</a></li>
</ul>
</nav>
</div>
</header>
<main class="container">
<h1>Frequently asked questions</h1>
<p class="lede">Visiting, ordering ahead, and catering. If your question is not here, <a href="contact.html">contact us</a> and we reply within one business day.</p>
<ul class="jump" aria-label="Topics">
<li><a href="#visiting">Visiting</a></li>
<li><a href="#ordering">Ordering ahead</a></li>
<li><a href="#catering">Catering</a></li>
</ul>
<section aria-labelledby="visiting">
<h2 id="visiting">Visiting</h2>
<details>
<summary>When are you open?</summary>
<p>Monday to Friday, 7:00 am to 5:00 pm, and Saturday, 8:00 am to 3:00 pm. We are closed on Sunday.</p>
</details>
<details>
<summary>Do you take reservations?</summary>
<p>No. Tables are first come, first served. Groups of eight or more can <a href="contact.html">write to us</a> a day ahead and we will hold a table.</p>
</details>
<details>
<summary>Is there parking?</summary>
<p>There is free street parking on Eastside Avenue and a public car park one block north.</p>
</details>
</section>
<section aria-labelledby="ordering">
<h2 id="ordering">Ordering ahead</h2>
<details>
<summary>Can I order ahead for pickup?</summary>
<p>Yes. Call (555) 010-0000 or order from the <a href="menu.html">menu page</a>. Orders are ready in about 15 minutes.</p>
</details>
<details>
<summary>Do you have vegan and gluten-free options?</summary>
<p>Yes. Both are marked on the <a href="menu.html">menu</a>. Our kitchen handles wheat, nuts, and dairy, so we cannot promise an allergen-free item.</p>
</details>
</section>
<section aria-labelledby="catering">
<h2 id="catering">Catering</h2>
<details>
<summary>Do you cater events?</summary>
<p>Yes, for 10 to 60 people within Springfield. Send the date and headcount through the <a href="contact.html">contact page</a>.</p>
</details>
<details>
<summary>How much notice do you need?</summary>
<p>Three business days for most orders, and one week for more than 30 people.</p>
</details>
</section>
<section class="more" aria-labelledby="more-heading">
<h2 id="more-heading">Still have a question?</h2>
<p>Call <a href="tel:+15550100000">(555) 010-0000</a>, email <a href="mailto:hello@larkspur.example">hello@larkspur.example</a>, or use the <a href="contact.html">contact page</a>.</p>
</section>
</main>
<footer>
<div class="container">© 2026 Larkspur Café · 12 Eastside Avenue, Springfield · (555) 010-0000</div>
</footer>
</body>
</html>
Notes on the code:
- The questions are in the HTML. Every answer is plain text inside the page, so it can be read without a script and found by search engines and find-in-page.
<details>and<summary>are the accordion. The browser handles opening, closing, keyboard focus, and the announced state. Add theopenattribute to a<details>element to show its answer by default, as Sun Design does for its first question.- The optional
nameattribute. Per MDN, giving several<details>elements the samenamevalue groups them so that "Only one of the grouped<details>elements can be open at a time". The template leaves it out on purpose: a visitor comparing two answers should be able to keep both open, which is also what the NN/g guidance above recommends. None of the 18 example pages uses it. - Plain-text fallback. To show every answer open, replace each
<details>block with an<h3>for the question and a<p>for the answer. Nothing else on the page changes, and this is the right version for a list of ten questions or fewer. - The contact route appears twice: in the first paragraph and in the closing block, both pointing at the contact page. The contact page examples include a matching
contact.html. - Structured data is optional. You can add
FAQPageJSON-LD that repeats the questions and answers. Google treats unused structured data as harmless, and it no longer produces an FAQ rich result in Google Search.
FAQ page checklist
- Every question came from a real customer email, call, review, or conversation
- Questions use the customer's wording, not internal terms
- Each answer gives the answer in its first sentence
- Answers that belong on another page (pricing, delivery, booking) also appear there, and the FAQ links to it
- More than about 20 questions: sorted into topic groups with an h2 heading each, most-asked topic first
- Long page: jump links or a question index at the top
- Questions and answers are in the HTML, not loaded by a script
- Accordion built with details and summary, or with real buttons that work from the keyboard
- Visitors can open more than one answer at a time
- A line and a link for unanswered questions, at the top or the bottom (or both)
- Phone numbers as tel: links and email addresses as mailto: links inside answers
- No answer that says only 'contact us'; state the fact, then offer the contact
- The FAQ is linked from the footer and from the contact page
- A date in your calendar to reread the page: prices, hours, and policies go stale first
FAQPage structured data is optional. Google stopped showing FAQ rich results on May 7, 2026, and has said unused structured data causes no problems.
Add the page to your pre-launch pass as well: the website launch checklist covers testing links, phone numbers, and forms, and every link inside an FAQ answer is one more to click before you go live.
FAQ
Frequently asked questions
What should be included in FAQ?
How to make a FAQ page?
What is a FAQ section?
Is there any SEO benefit to an FAQ page?
Does an FAQ have to be a separate page, or can the answers live on the relevant page?
How many questions should an FAQ page have?
Should FAQ answers be in an accordion or all open?
Where to go next
Start with the questions already in your inbox, answer each on the page it belongs to, and build an FAQ page from what is left. Copy the HTML template, then borrow specifics from the closest example: service groups from Hammer & Hand, a counted short list from Sun Design or Dashing Maids, the contact line first from Ugmonk, a question index from Pinboard, or topics instead of questions from Red Rocks. For the pages around it, see the contact page examples for where unanswered questions go, the website structure examples for where FAQ sits in the menu, the HTML website example for the rest of a hand-written site, and the website launch checklist before you publish. The full website examples library has more.