The short answer
Keep an FAQ when it helps a customer decide or prepare. Review its technical markup separately. A change to Google's search presentation does not remove the value of a good answer, and useful questions should not be deleted merely because a former search enhancement has ended.
Keep the customer question in view
Your website has answers about preparation, exclusions and how to request a quote. A technical report recommends removing FAQ markup, and the cleanup is about to delete the visible questions too.
That combines two different decisions. One concerns a format used by external systems. The other concerns information your potential customers may still need.
Judge the questions by the conversation they save
A useful FAQ resolves something a reader still needs to know after the main explanation. 'What should I send before asking for a quote?' or 'Can you work with our existing content?' can help someone take a sensible next step, provided the answers match the actual offer.
A weak FAQ repeats the page's introduction in question form or adds broad topics simply to make the page longer. Keep the questions that remove a real uncertainty. Move essential buying information into the main page where appropriate, rather than hiding every important condition in an accordion.
A worked example
Suppose a service page explains what materials a customer must provide before production can start.
Where it goes wrong
A cleanup removes both FAQ markup and the visible preparation answer. The technical report looks cleaner, but customers now have to ask the team for the same information.
What to do instead
Keep the preparation explanation where it helps the customer. Decide separately whether the markup has a current, justified use.
The customer information survives a change in technical presentation. The example is about separating responsibilities, not preserving every FAQ block.
A vocabulary and a search feature are different things
Google has retired its FAQ rich result feature. That concerns a presentation in Google Search, rather than a rule that websites must stop answering questions. A structured-data type can also exist independently of one consumer's use of it.
Ask why the markup remains and which supported consumer needs it. Then assess the maintenance cost and current guidance. Do not promise an obsolete Google enhancement, but do not treat a technical cleanup as a reason to remove useful customer information.
Make the answers easy to find and trust
Use the customer's wording where it makes the question clearer. Answer directly, with relevant conditions beside the promise. If the answer depends on the agreed scope, say which decision still needs a conversation.
Keep repeated answers consistent across service pages and articles. When the business changes an inclusion or process, review the FAQ as well as the headline copy. A helpful answer is part of the offer's explanation, not an isolated SEO decoration.
Take this into your next conversation
Questions to ask your agency
- Does this question resolve a genuine customer uncertainty?
- Should the answer be in the main explanation instead?
- Which current consumer needs the markup?
- Who checks the answer when the service changes?
Common questions
Should we remove all FAQs because Google changed its feature?
No. Assess the visible answers for usefulness and the markup for its own current purpose. They are separate decisions.
How many questions should a page have?
Enough to resolve the meaningful follow-up questions that remain. There is no reason to fill an arbitrary quota with repetition.
Source notes
Platform guidance behind this topic:
From explanation to implementation
This guide is published by NAVIFLARE, a website, CRM and AI workflow practice. Source notes identify the platform guidance; worked examples explain a method rather than claim a client result.
Explore seo and ai search visibilityYour next step
Bring the FAQ block and any recommendation to remove it. We can discuss which answers support the customer journey and which technical assumptions need updating.
Review your service-page questions
