FAQ strategy after a search change
Google retiring FAQ rich-result documentation is not a reason to delete helpful answers. It is a reason to stop treating FAQs as a markup tactic and start treating them as part of the buying journey.
What actually changed
Google’s documentation updates show that FAQ rich-result documentation was removed after the feature stopped appearing in Google Search. That change affects a special search-result display. It does not mean customer questions stopped mattering.
The mistake is to ask, “Do FAQs still help SEO?” as if every FAQ block has the same value. A better question is: “Does this answer help a real visitor make the next decision?” If the answer is yes, the FAQ probably still belongs somewhere. If the answer is no, markup will not rescue it.
Keep
Questions sales, support or project leads hear repeatedly before someone buys, books or asks for a quote.
Rewrite
Answers that are technically true but too vague to reduce hesitation or explain what happens next.
Remove
Keyword-led question lists copied from competitors, hidden content, and promises that schema guarantees visibility.
The new job of an FAQ page
A useful FAQ is not a dumping ground. It should reduce friction at a specific moment: pricing uncertainty, service fit, timing, process, location, policy, maintenance or risk. That makes the FAQ a conversion and trust asset first. Search benefits are secondary.
For example, a website design FAQ should not sit alone on a generic archive if the question helps someone decide whether to request a new website. It belongs near the website creation service, where the visitor can connect the answer to the offer, scope and next step.
A sharper FAQ audit
| Audit question | Keep, move or cut? | Why it matters |
|---|---|---|
| Has a real customer asked this more than once? | Keep or rewrite | Repeated questions reveal genuine uncertainty. |
| Does the answer help someone choose, book or contact? | Keep near the relevant service page | The answer is strongest where the decision happens. |
| Is the answer only there for a keyword? | Cut or merge | Thin FAQ blocks make the page feel generic. |
| Does the answer need a tailored estimate or diagnosis? | Set a boundary and invite contact | False precision damages trust. |
| Does the schema match visible copy? | Fix before keeping schema | Structured data should describe the page honestly. |
Bad vs good FAQ answers
Weak answer: “How much does a website cost? Our websites are affordable and tailored to your needs. Contact us for more information.”
Stronger answer: “The price depends on page count, content readiness, design complexity, forms, multilingual needs and SEO requirements. A small brochure site is different from a lead-generation site with service pages, tracking and ongoing updates. The first step is to clarify scope, then quote the work against that scope.”
Weak answer: “Do you do SEO? Yes, we offer professional SEO services.”
Stronger answer: “Yes. The useful starting point is usually an audit of indexability, service-page clarity, internal links, metadata, local signals and structured data. For small businesses, SEO work should connect to real enquiries, not only rankings.”
Those stronger answers are not longer for the sake of length. They explain variables, remove false certainty and point the visitor toward a sensible next action. That is the difference between an FAQ that fills space and an FAQ that helps a buyer.
Where each question should live
Many small-business websites create one large FAQ page because it feels tidy. That can work for policies or support topics, but service questions often perform better next to the service they explain.
| Question type | Best location | Next step to show nearby |
|---|---|---|
| Scope, deliverables and timelines | Relevant service page | Quote request or discovery call |
| SEO, visibility or audit questions | SEO & GEO optimisation or audit page | Audit enquiry or visibility review |
| Pricing variables | Service page, pricing note or proposal process section | Scope clarification |
| Policies, ownership or aftercare | Support, process or terms-related page | Contact route for exceptions |
| Very broad education questions | Article or guide | Internal link to the service page |
How to rewrite existing FAQs
Start each answer with the direct answer. Then add the conditions that matter. End with the logical next step only when it genuinely helps. This keeps the copy useful for visitors and easier for search systems to interpret without turning every page into a block of generic question text.
- Use the customer’s wording. Keep natural questions instead of keyword-stuffed variations.
- Lead with the answer. Do not make visitors read three sentences before learning the point.
- Name the variables. Timing, budget, scope and suitability often depend on specific factors.
- Show boundaries. Say when an estimate, audit or diagnosis is needed.
- Link only where useful. Use descriptive links such as request a website or SEO review.
What to do with FAQPage schema
FAQPage schema should be a faithful description of visible content, not a workaround for lost search real estate. If the question and answer are visible to users and genuinely part of the page, schema can still help describe that content. If the FAQ is hidden, duplicated or unrelated to the page purpose, remove or rewrite it before thinking about markup.
Google’s FAQPage structured data documentation remains the technical reference. Pair it with Search Essentials: useful content, accessible pages and honest presentation still matter more than a schema field.
A 30-minute FAQ cleanup plan
- List every FAQ block on the site.
- Mark each question as real customer question, useful but misplaced, outdated, invented or unclear.
- Move service-specific questions to the matching service page.
- Rewrite the top five answers so each starts with a direct answer and names the real variables.
- Remove duplicated or low-value questions.
- Check links, mobile readability, keyboard accessibility and schema alignment.
This is a small task, but it usually improves the website more than adding another long FAQ page. It makes existing pages clearer and gives visitors fewer dead ends.
Frequently asked questions
Should I delete my FAQ page now?
No. Keep it if the questions are genuine and useful. Delete or merge questions that are duplicated, outdated, invented for keywords or disconnected from a real customer decision.
Should every service page have FAQs?
No. Add FAQs only where they answer common objections or decisions for that service. A short, specific FAQ section is better than a long generic one.
Does FAQPage schema still matter?
It can still describe visible FAQ content, but it should not be treated as a guarantee of a search-result feature. Use it only when it matches the page accurately.
What is the best first FAQ to rewrite?
Start with the question people ask before contacting you: price, timing, scope, suitability or process. Those answers often have the clearest business value.