Every customer conversation your business has ever had is a list of questions: how much, how long, do you serve my area, what happens if. FAQ content turns those conversations into pages that search engines can surface and AI assistants can quote. Pair the content with FAQPage structured data and you give Google a machine-readable version of your answers. This guide covers writing FAQs that actually earn their place, marking them up correctly, deciding where they belong, and measuring whether the effort paid off.
Are FAQs still worth it for SEO?
Yes, though the payoff has shifted. Google has tightened which sites receive expanded FAQ rich results in search listings over the years, so the guaranteed dropdown treatment of the past is no longer the main prize. The current value is broader: FAQ content matches how people actually search, especially in voice and conversational queries, and it feeds the AI-generated answers that increasingly sit at the top of search results. A New Westminster contractor whose site clearly answers "do I need a permit for a bathroom renovation in BC" is quotable by search engines and AI assistants alike. Structured data makes those answers easier for machines to parse with confidence, which is exactly the situation you want as more search traffic flows through answer engines.
How do you write FAQs people actually search for?
The difference between useful FAQ content and filler is source material. Strong FAQs come from real questions:
- Mine your inbox and call notes. The questions prospects ask before buying are the questions others type into Google.
- Check the "People also ask" boxes for your target searches; they reveal phrasing real users choose.
- Ask your front-line staff what they explain over and over.
- Look at Search Console queries containing "how," "what," "can," and "does" that already bring you impressions.
Then answer properly. Two to four sentences, direct first sentence, specifics over fluff. "Yes, we serve all of Metro Vancouver including Surrey and Langley, with same-day service in most areas" beats a paragraph of throat-clearing. Write each answer so it could stand alone if quoted out of context, because that is precisely how AI systems use it.
Avoid manufacturing questions nobody asks just to stuff keywords in. Thin, repetitive FAQ blocks are easy for both users and algorithms to recognize, and they dilute the genuinely useful answers around them.
How do you add FAQ schema to a page?
FAQPage structured data uses JSON-LD, a small script block that mirrors the visible questions and answers. A minimal valid example:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do you serve businesses outside Vancouver?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We work with businesses across Metro Vancouver, including New Westminster, Burnaby, and Surrey."
}
},
{
"@type": "Question",
"name": "How quickly can a project start?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most projects begin within one to two weeks of the initial consultation, depending on scope."
}
}
]
}
The block goes inside a script tag with type="application/ld+json" in the page's HTML. Two rules matter above all others: the marked-up questions and answers must appear visibly on the page for users, and the schema text should match that visible content. Marking up content users cannot see violates Google's guidelines. After adding it, run the page through Google's Rich Results Test to confirm the markup parses cleanly.
Many website platforms and plugins can generate this markup from a visual FAQ block, so hand-coding is optional. What is not optional is checking the output, since plugins sometimes emit duplicate or malformed schema.
Where should FAQs live on your website?
Resist the urge to dump everything on one giant FAQ page. Question-and-answer content works hardest when it sits next to the decision it supports:
Service pages. Questions about process, pricing factors, timelines, and guarantees belong beside the service description, where they remove objections at the moment of evaluation.
Location pages. Service-area questions, local regulations, travel fees, and neighbourhood specifics make a location page genuinely local instead of a template with a city name swapped in. This pairs naturally with the tactics in our guide to local SEO in Vancouver.
Blog posts. A short FAQ section at the end of a post captures related long-tail queries the main content did not directly address, and gives the post additional chances to match conversational searches.
A central FAQ page still has a role for company-wide questions like hours, payment methods, and policies. Just do not let it absorb questions that belong on money pages.
Each page's FAQ should be unique. Copying the same five questions across twenty pages creates duplication, and duplicated FAQ answers compete with each other instead of reinforcing the site, a cousin of the on-page problems covered in our Vancouver on-page SEO guide.
How do FAQs feed AI answers and voice search?
AI answer engines and voice assistants work by extracting concise, self-contained answers from pages they trust. FAQ formatting is nearly ideal raw material: an explicit question, a direct answer, and structured data confirming the relationship. When someone asks their phone "how much does a bathroom renovation cost in Vancouver," systems assembling an answer look for exactly this shape of content.
You cannot force inclusion in AI answers, and no vendor honestly can. What you control is eligibility: clear questions matching real query phrasing, answers that stand alone, accurate schema, and a site with enough overall authority to be treated as a credible source. That last part is why FAQ work belongs inside a broader SEO program rather than as a standalone trick.
How do you measure whether FAQ content is working?
Search Console is the primary instrument. Watch three places:
- The Performance report, filtered to question queries. Track impressions and clicks for searches beginning with "how," "what," "can," "do," and similar. Growth here means your FAQ content is matching real questions.
- The Enhancements or rich result reports. If Google detects valid FAQPage markup, it reports the items and flags any errors to fix.
- Page-level performance for pages where FAQs were added. Compare impressions and average position in the weeks before and after.
Also watch behaviour signals in your analytics: pages that answer objections tend to hold visitors longer and convert more of them. Movement takes time, and most businesses see meaningful movement within 3 to 4 months of consistent content work rather than overnight.
Frequently asked questions
Is FAQ schema still worth adding in 2026?
Yes, with adjusted expectations. Expanded FAQ rich results in listings have become rarer for ordinary business sites, but the markup still helps search engines and AI systems parse your answers with confidence, and the underlying content matches conversational and voice queries. The content is the asset; the schema is its label.
Can I add FAQ schema without touching code?
Usually. Most modern platforms offer FAQ blocks or plugins that output JSON-LD automatically, and site builders increasingly include it natively. Verify the result with Google's Rich Results Test either way, because malformed or duplicated markup is common with plugin-generated schema. If your site needs deeper structural work, our web design team builds schema in from the start.
How many questions should an FAQ section have?
Enough to cover the genuine questions for that specific page, which is typically three to eight. Quality and relevance beat volume; a service page with five sharp, specific answers outperforms one with twenty padded entries. Save unrelated questions for the pages they actually belong to.
Will FAQ schema guarantee rich results or AI citations?
No, and be wary of anyone promising otherwise. Valid markup makes you eligible, not entitled; Google decides what to display based on site quality, relevance, and its own display policies. Focus on answer quality and overall site authority, since those drive both eligibility and selection.
Not sure whether your site's structured data is helping or just sitting there? Request a free SEO audit and we will check your markup, your FAQ coverage, and where question-based content could win you more visibility.
