FAQ pages aren't boring — they're strategic
There's a perception problem with FAQs. Business owners think of them as a dumping ground for questions they're tired of answering. A necessary evil. Something to stick at the bottom of the footer and forget about.
That mindset is costing you money. A proper FAQ page serves at least four distinct functions simultaneously:
- It pre-qualifies visitors by answering objections before they bounce
- It reduces inbound support tickets and repetitive phone calls
- It gives search engines (traditional and AI) structured content to index and cite
- It builds topical authority around your core services
Research from multiple UX studies shows that 67% of consumers prefer self-service over speaking to a representative. Your FAQ page is self-service. If it doesn't exist, or if it's thin and unhelpful, you're pushing people toward your competitors who do have one.
The schema markup piece most people ignore
Having an FAQ page is good. Having one with FAQPage schema markup is significantly better. Schema is structured data — a way of tagging your content so that search engines can understand it programmatically rather than just reading it like a human would.
When you add FAQPage schema to your questions and answers, several things happen. Google can display your answers directly in search results as rich snippets. Your content takes up more visual real estate on the results page. And critically for where search is heading, AI models like ChatGPT, Perplexity, and Google's AI Overviews can parse your answers cleanly and cite them in their responses.
This is the core of what we work on with our AI search optimisation service — making sure your content isn't just visible to humans, but machine-readable in a way that earns citations from AI engines. FAQ schema is one of the lowest-effort, highest-impact ways to get there.
A study by Search Engine Journal found that pages with FAQ schema saw up to a 20-30% increase in click-through rate compared to the same pages without it. For a small business competing against bigger players, that kind of edge is enormous.
What makes a good FAQ page (and what makes a terrible one)
Most FAQ pages I see are terrible. They're either too short (three generic questions), too long (fifty questions with no organisation), or written in a way that doesn't actually match how customers think or speak.
A good FAQ page has a few specific characteristics:
- Questions are written in the customer's voice, not the business's jargon
- Answers are concise but complete — 2-4 sentences, not essays
- Questions are grouped by topic if you have more than 10
- Each answer links to a relevant service or product page where appropriate
- The page is updated regularly as new questions emerge
Here's an example. Bad question: "What is our returns policy?" Good question: "Can I return something if it doesn't fit?" The second one mirrors how a real person types into Google or asks ChatGPT. That distinction matters more than you'd think, because AI search engines are trained on natural language patterns. They favour content that matches how people actually phrase queries.
If you're building or redesigning a site, this should be baked in from day one. It's something we factor into every website project we build at Draxiq — the FAQ isn't an afterthought, it's part of the information architecture.
FAQ pages and the rise of AI search
This is where it gets really interesting. Traditional SEO rewarded you for ranking on page one. AI search — ChatGPT, Perplexity, Google AI Overviews — rewards you for being the source an AI cites in its answer.
Those are fundamentally different games. In traditional search, you need backlinks, domain authority, and keyword density. In AI search, you need clarity, structure, and schema. FAQ pages tick all three boxes naturally.
When someone asks Perplexity "What's the best way to clean a leather sofa in Manchester?" and your cleaning company has an FAQ page with that exact question, answered clearly, tagged with schema — you've just become a candidate for citation. Not buried on page three. Actually named and linked in the AI's response.
I wrote about this shift in detail in a post about how to optimise your website for AI search in 2026 and beyond. The short version: structured, question-and-answer formatted content is exactly the shape that large language models prefer to ingest and cite. FAQ pages are that shape by default.
How many questions do you actually need?
I get asked this a lot. The answer depends on your business, but as a general rule: start with 15-25 questions across three or four categories. That's enough to cover the main objections and queries without overwhelming visitors.
Here's how I'd think about sourcing those questions:
- Support inbox: What do people actually email you about? Those are your FAQs.
- Sales calls: What questions come up before someone commits? Those are your objection-handling FAQs.
- Google Search Console: What queries are people using to find you? Turn those into questions.
- Competitor gaps: What questions do your competitors fail to answer on their sites?
- AI tools: Ask ChatGPT "What would someone want to know before hiring a [your industry] in [your city]?" — the results are surprisingly useful.
Once you've got your initial set, add 2-3 new questions per month. This keeps the page fresh, gives search engines new content to index, and steadily builds your topical authority.
The technical side: schema isn't as scary as it sounds
I think a lot of small business owners hear "schema markup" and assume it requires a developer. It doesn't — but it does need to be done correctly. A misconfigured schema can actually hurt you, because Google will flag it as misleading structured data and you'll lose eligibility for rich snippets entirely.
The FAQPage schema format is relatively straightforward. Each question-answer pair is wrapped in a specific JSON-LD structure that sits in your page's head or body. The key rules:
- Every question on the page must appear in the schema (you can't cherry-pick)
- Answers in the schema must match the visible content exactly
- No promotional content disguised as answers — Google explicitly penalises this
- Schema must be valid JSON-LD (test it with Google's Rich Results Test)
If you're running a WordPress or Shopify site, there are plugins that automate schema generation. If you're on a custom build, it's a one-time setup that a decent developer handles in an hour or two. We often layer this into broader integration and automation work we do for clients, because schema shouldn't live in isolation — it needs to be part of a connected data strategy across your entire web presence.
The payoff is disproportionate to the effort. One afternoon of work can earn you rich snippets, AI citations, and a measurable drop in support volume. I genuinely can't think of many other changes to a small business website that deliver that kind of return.
The point
If you run a small business and your website doesn't have a proper FAQ page with schema markup, you're leaving money on the table. Not in some abstract, theoretical sense — in a very concrete, measurable sense. Fewer rich snippets. Fewer AI citations. More repetitive support enquiries. Lower conversion rates. All because you haven't taken an afternoon to write down the questions your customers are already asking you and mark them up properly.
This is one of those rare situations where the simplest thing you can do is also the most effective thing you can do. Don't overthink it. Just do it.
— Graham
Related reading
Frequently asked questions
