Search appearance & customer experience
Keep useful FAQ pages because they help customers decide—not because they promise a special Google result. Google retired FAQ rich-result documentation in June 2026, so the sensible next move is to improve answers, page structure and the paths people take after reading them.
What changed, and what did not
Google’s July documentation update records that FAQ rich-result documentation was removed after the feature stopped appearing in Google Search. That affects a search-result treatment, not the value of answering real customer questions. A well-written FAQ can still reduce uncertainty before someone contacts you, compares services or completes a purchase.
For a small business, that distinction matters. A question such as “How long does a website project take?” is useful when it gives a realistic range, explains the variables and offers a relevant next step. It is weak when it repeats a keyword or makes a promise the business cannot keep.
Keep
Questions customers ask before buying, booking or requesting a quote.
Improve
Answers that are vague, outdated, hidden or disconnected from a useful next step.
Avoid
Copied question lists, invisible answers and claims that markup guarantees a result.
A practical FAQ review in five steps
1. Start with evidence from real conversations
Review enquiry emails, sales calls, support requests and on-site search terms. Group recurring questions by decision: price and scope, timing, suitability, process, location, aftercare or policies. One clear answer is more valuable than ten invented questions.
2. Put the answer on the page that owns the decision
A question about website design belongs naturally on the small-business website design service page. A question about visibility or technical review belongs with SEO & GEO optimisation. This gives visitors context and lets them continue to the relevant service instead of sending them through a generic FAQ archive.
3. Write the answer first
Lead with the useful answer in one or two sentences. Then add conditions, examples or limits. For example: “Most small brochure sites need a focused discovery, content and review phase; the timetable changes when pages, photography or approvals are still missing.” That is clearer than a blanket deadline.
4. Check the visible experience
Questions should be readable on a phone, expandable with a keyboard and placed near related content. Do not hide important service limits solely inside an accordion. Use descriptive links such as discuss your website project, rather than “click here”.
5. Treat schema as a faithful description
If you use FAQPage structured data, it should match the questions and answers visible to visitors. It is not a performance guarantee. Google’s FAQPage documentation remains the right technical reference for eligibility and implementation details; review it before changing site-wide templates.
Choose the right home for common questions
| Customer question | Best page | Useful answer should include |
|---|---|---|
| What is included in a new website? | Website creation service page | Deliverables, client responsibilities and a contact route |
| When should we commission an SEO audit? | SEO audit or SEO/GEO service page | Symptoms, scope limits and what the audit produces |
| Can you help us show up in AI-assisted search? | GEO/SEO service page | Evidence, structured content and measurement—not ranking promises |
| How do we update our WordPress site safely? | Support article | Backup, staging and post-update checks |
How FAQ content supports search and AI-assisted discovery
Clear questions and direct answers make a page easier for people to scan and easier for systems to interpret. But the foundation is still the same: original, accurate information, a page that serves a real purpose, and technical basics that work. Google’s guidance on Search Essentials is a useful baseline for that work.
Use FAQs to clarify entities and decisions: the service offered, who it is for, where it applies, what is included and what happens next. Pair them with helpful headings, relevant examples and internal links. Our schema markup guide explains how structured data can describe visible content without replacing it.
Before you change an FAQ template
- Confirm the question is genuinely asked by customers.
- Make the visible answer complete, current and accessible.
- Check that any markup matches the visible question-and-answer pair.
- Keep one clear page purpose; do not turn every page into a long generic FAQ.
- Test the page on a narrow phone screen and follow every important internal link.
Frequently asked questions
Should I remove FAQ sections now?
No. Keep FAQ sections that answer genuine customer questions. Review them for accuracy, visibility and usefulness instead of keeping them for a promised search-result feature.
Does FAQPage schema guarantee a Google rich result?
No. Structured data helps describe visible content, but it does not guarantee a specific Search appearance. Follow current Google documentation and keep the page useful without relying on a display outcome.
Where should a small business put FAQs?
Put them near the service, product, policy or process they explain. This helps visitors act on the answer and keeps internal linking relevant.