An FAQ page earns its URL when one recognisable reader needs a related set of answers to complete one task. It becomes a content cupboard when unrelated questions are swept off stronger pages, stacked beneath accordion headings and defended because every paragraph ends with a question mark.
The useful SEO question is not “Do FAQ pages rank?” It is “Why do these answers belong at the same address?”
That standard matters more now that the old rich-result incentive has gone. Google stopped showing FAQ rich results on 7 May 2026 and later removed the associated feature documentation (Google Search documentation updates). The green validation tick can no longer distract a business from the absence of a page job. Good. Markup was never a sound reason to publish a junk drawer.
TL;DR
- FAQ is a format, not permission to create a page; the reader's task decides where an answer belongs.
- Answers that change price, fit, risk or commitment belong beside the decision, not in a general FAQ.
- Run the shared-address test: seven boundaries, and one failed boundary can stop publication.
- Delete the page on paper, return each answer to its decision, and keep only the collection that survives, under a title that names its job.
The FAQ format can conceal an information-architecture failure
Most bad FAQ pages were not conceived as bad pages. They accumulated. Sales wanted somewhere to explain payment. Operations added appointment instructions. Marketing inserted keyword-shaped questions. Customer service contributed returns. Recruitment supplied a careers answer. Nobody wanted to change the service pages, so “Frequently Asked Questions” became neutral territory.
The result looks organised because the CMS provides headings and accordion controls. Underneath, the page has no coherent audience, sequence or decision. This is why I treat an FAQ as a format, not permission to create a page. Question-and-answer copy can work on a service page, product page, policy page, onboarding guide or support article. The grammatical form does not decide where the answer belongs. The reader’s task does.
For website design, this distinction is fundamental. Components should express the information architecture. They should not be used to avoid designing one.
Find the task hiding behind the questions
A coherent collection supports one recognisable situation. A visitor preparing for an appointment may need to know what to bring, who can attend, where to park and what happens on arrival. An ecommerce customer dealing with delivery may need dispatch timing, tracking, missed-delivery rules and returns. A landlord arranging a survey may need access, responsibility, timescale and report-delivery answers. Those questions belong together because the same person can need several of them while completing the same task.
Now combine appointment preparation, refunds, recruitment, service areas and company history. The only shared context is the label “FAQ”. That is not a page proposition. It is the residue of unresolved ownership. Before approving the page, complete this sentence:
This page helps ⟨specific reader⟩ complete ⟨specific decision or task⟩ without ⟨recognisable uncertainty, risk or delay⟩.
If the sentence requires several audiences, unrelated tasks or “find general information”, the collection is asking to be split. I would rather publish three smaller pages with clear jobs than one large page whose only growth strategy is surface area.
Important answers often belong closer to the decision
The questions most likely to change conversion are often the worst candidates for exile to a general FAQ. Price, eligibility, coverage, suitability, cancellation, response time and material exclusions belong where the buyer decides whether to continue. Sending someone away from a service page to discover that the offer does not cover their property, budget or use case is avoidable friction. That is not good conversion rate optimisation. The extra click may keep the primary page visually clean, but it makes the decision journey less honest.
Use the decision page for the direct answer and controlling condition. Create a deeper guide only when the mechanism, evidence or range of scenarios genuinely needs more room.
- “Do you cover Hove?” usually belongs with the service-area decision.
- “What affects the cost?” belongs on the service or pricing route.
- “Which option suits a listed building?” may need a comparison or specialist guide.
- “What should I bring to my first appointment?” can join a focused preparation page.
- “How do returns work?” belongs with the buying and support journey.
The FAQ must not become the place where commercially awkward facts are hidden. If an answer changes fit, price, risk or commitment, put it beside the proposition it limits.
Apply the shared-address test
Before creating or retaining an FAQ page, test whether the questions have earned one URL.
- Audience
Would the same kind of reader reasonably need these answers?
- Task
Do they support one decision, process or stage?
- Sequence
Can they follow the way uncertainty develops rather than an alphabet?
- Ownership
Does the collection perform a job no stronger existing page owns?
- Answerability
Can the business publish direct, supportable answers with necessary conditions?
- Maintenance
Can one accountable owner keep the changing facts current?
- Conversion
Does the page lead to the next appropriate action rather than a generic form?
This is not a seven-point score. One severe failure can be decisive. Perfect grouping cannot rescue unsafe advice. A useful set of questions cannot survive if nobody owns changing prices or policies. A beautifully written page should still be merged when another page already owns the decision more strongly.
My approval rule is deliberately asymmetrical: a page has to pass every material boundary, but one failed boundary can stop publication. Content volume is cheap. A second owner for the same fact is expensive.
A content dump has a recognisable smell
You can usually detect the dump before opening analytics. It contains twenty questions contributed by six departments. Several answers repeat service-page copy. Others say “contact us” because nobody agreed on a public answer. Keyword variations have been promoted into questions nobody asks. Prices and exclusions remain vague, but the company-history response runs for six paragraphs. Other signals include:
Do not fix this by polishing the introduction or inventing more categories. Empty order is still disorder.
The strongest FAQ page may not use FAQ in its title
Name the page after its job when the job has a better name. “Planning Your Visit” tells a venue visitor what the collection does. “Before Your Property Survey” gives preparation, access and reporting questions a shared context. “Delivery and Returns Help” is more useful than forcing ecommerce policies into a corporate FAQ. “Preparing for Your First Consultation” creates a sequence for documents, confidentiality, attendees and next steps. The answers may still use question headings. What changes is the centre of gravity.
This improves editorial governance because every proposed addition faces a boundary. A question either helps someone prepare for the survey or it does not. A catch-all FAQ has no comparable rejection mechanism, so every stray answer appears eligible. The title is a content rule disguised as reader language. If you cannot replace “FAQ” with a clear task, the page may not have one.
Got an FAQ page that six departments own and nobody maintains? We run the shared-address test and return each answer to the decision it should support.
Frequently asked does not mean briefly answered
Some answers need room to remain honest. “How much does it cost?” may require a range, VAT basis, assumptions, inclusions and variables. “Is this suitable for my property?” may depend on construction, symptoms, access and assessment. “What happens if the work fails?” may require exact warranty scope, exclusions and a claim route. Compressing those answers into two sentences can make the interface neat while making the decision unsafe.
Promote a question into its own maintained page when the answer performs a substantial task by itself; when different reader situations require different treatment; when evidence, calculations, examples or diagrams are necessary; when legal, financial, medical or safety boundaries are material; when the facts change on an independent review cycle; or when several pages need one canonical explanation.
The focused collection can retain a compact answer or route, but the deeper page should own the mechanism and evidence. This is not accidental duplication when each page has a defined role. For AI readiness, that ownership matters. Clear, maintained answers are more useful than repeated fragments whose conditions diverge over time. AI search optimisation begins with factual coherence, not with multiplying question-shaped copy.
Write answers that actually resolve something
A question heading does not convert evasive sales language into an answer. Compare “Can you attend in Lewes? Our friendly team covers the surrounding area. Contact us for details” with “Do you cover Lewes? Planned appointments are available in the Lewes area for the listed services, subject to current capacity. Include the postcode and required service when requesting availability.”
The second answer names the applicable service condition and gives a useful next action. The first hands the uncertainty back with a lead form attached. Each material answer should contain:
Do not invent certainty for a cleaner component. “Individual suitability cannot be established without an assessment” can be a direct answer when it explains why and describes the assessment route. “Contact us” alone is not a boundary.
Let uncertainty determine the order
Readers rarely experience questions alphabetically. They move through a decision. Am I eligible? Does this fit? What is included? What will it cost? How long will it take? What must I prepare? What can go wrong? What happens next? Order the page around that movement. Use clear group headings and a compact contents route when the collection is long enough to need them. Keep question wording natural so readers recognise their concern without translating SEO phrasing.
Do not force every answer into an accordion because the WordPress component already exists. Accordions can help scanning, but they can also hide decisive conditions, frustrate comparison and introduce accessibility defects when implemented badly. Interface choices should serve the task. If several answers need to be compared, price inclusions, option differences or safety conditions, show them together. A table, visible list or dedicated comparison may do the job better.
This is where branding and user experience meet. The brand promises clarity through what it reveals at the moment of decision, not through another paragraph claiming to be transparent.
The search value survived the rich-result retirement
The disappearance of Google’s FAQ rich result removed a display feature. It did not remove the value of resolving real questions. Google’s people-first guidance asks whether content serves an intended audience, offers original value and leaves readers feeling they have learned enough to achieve their goal (Google Search Central). Its newer AI guidance similarly encourages unique, non-commodity material rather than pages manufactured for every query variation (Google Search Central).
A focused question-led page can support ordinary search, sales, support, social media replies and customer onboarding. It may also make public facts easier for AI systems to recover. None of that guarantees rankings, citations or revenue. The honest AI SEO and search case is smaller: answer genuine uncertainty in a structure people can understand and the business can maintain. Do not replace the retired rich-result pitch with an equally magical AI marketing promise.
Delete the page on paper before defending it
My preferred audit starts with a temporary decision: the FAQ page will be deleted. For every question, identify where the answer must go if the URL disappears. Some answers move beside service decisions. Some become policy or support content. One may deserve a full guide. Others have no evidence, no meaningful demand or no permission to remain public. What remains is the genuine collection.
Keep the page only if those remaining questions serve the same reader, progress the same task, work better together and have an owner who can maintain them. Give the collection a title that names the job. Remove questions that merely make the asset look comprehensive.
There is a cost to this method: the site may end up with fewer pages and less keyword-shaped inventory. I accept it. Digital growth does not require every answer to own a URL. It requires the right answer to appear where a buyer or customer needs it. An FAQ page helps SEO when it is good decision architecture. If the questions do not belong together, stop decorating the cupboard and return each answer to the decision it was supposed to support.
Good to know
FAQs
The rich result was a display feature; its retirement did not remove the value of resolving real questions. A focused, maintained question-led page can still support search, sales and support. A junk drawer of unrelated questions never helped much and now has no markup incentive to hide behind.
Usually not. Answers that change fit, price, risk or commitment belong beside the decision they limit, on the service, pricing or service-area page. Sending someone to a general FAQ to discover an exclusion is avoidable friction.
Seven boundaries a collection must pass before it earns one URL: same audience, one task, a sequence that follows uncertainty, ownership no stronger page already has, answerable questions, one accountable maintainer, and a next action. One failed boundary can stop publication.
Decide on paper that the page will be deleted. For every question, identify where the answer must go instead. Whatever genuinely belongs together, serves one reader and has an owner is the real collection. Give it a title that names its job.
Next step
Is your FAQ page hiding decisions that belong elsewhere?
We delete the page on paper with you, return each answer to the decision it supports and rebuild the collection that survives under a title that names its job.