I run an ad agency and clients have frequent questions. I want to gather these in an FAQ page. What's the ideal number of questions?
Google shows a special widget next to FAQ questions for some sites. Can we get that kind of display too? What's it called?
How detailed should I be when writing the questions?
An FAQ page should consist of 8-12 questions. If it's too long, it's complicated to build, if it's too short, people can't find answers.
The special display on Google is called a 'Rich Result'. This requires FAQPage schema markup. If you mark up the question + answer format with JSON-LD, it can appear in search results.
Write in detail but keep it concise — question 1-2 sentences, answer 2-4 paragraphs. Add internal links too (directing to other pages).
Doki · Log management setup · 2025
when writing the faq we wrote everything in q&a format. anyway schema markup scared us a bit but the rest was easy
FAQ content examples: - How to use the product - What is the refund period - Is there a free trial - How to get support - About the company - How to cancel the free trial
FAQPage schema example: { '@context': 'https://schema.org', '@type': 'FAQPage', 'mainEntity': [{ '@type': 'Question', 'name': 'Question text', 'acceptedAnswer': {'@type': 'Answer', 'text': 'Answer'} }] }
when you write schema markup dont panic if there are errors in google search console fixing them is very simple. tbh but if you write it carefully rich results come through
Quick side: 1. Collect frequent questions from customer surveys 2. Write 2-3 sentence answers for each question 3. Add schema markup 4. Test (Google Search Console) 5. Publish
There's one point I'm curious about. Internal linking is the cheapest and most neglected task.
If you have questions, write them; I'll answer as best I can.
There's one point I'm curious about. Trying to do this alone is the most expensive way.
Proven by experience.
Yes, that's exactly how it is with faq page. Most time waste accumulates in tasks waiting for approval.
Start with a small trial; don't commit to everything at once.
I disagree with you on this point. When we decide without measuring, we always end up in the same place.
When making a decision, first look at what data you have on hand. Correct me if I'm wrong.
There's a trap here, let me mention it. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.
Correct me if I'm wrong.
Looking at it as a process, the picture changes. Just because everyone does it doesn't mean it's right.
If you're going this route, sort this out first. Solutions that work at a small scale collapse when you grow; I learned this late.
That's all, sorry if I went on too long.
This is exactly what we experienced. Updating an existing page yields faster results than creating a new one.
If rankings stay the same but clicks drop the issue isn't your page, but the search result appearance. I mean this is my opinion I'm not claiming it's absolute truth.
My question might sound amateurish, sorry about that. When making a decision first look at what data you have on hand.