Why this signal matters for Google
A FAQ page only proves expertise when the answers are precise. FAQ stands for frequently asked questions: the page where you answer in advance what people ask you all the time. Most sites have one, and most are decorative: "Do you ship nationwide? Yes." "Are your products guaranteed? Yes, satisfaction guaranteed." Those answers take no skill to write, and readers feel it. An expert FAQ answers the way a professional does on the phone: with the timeline, the price, the condition and the exception. "How long does a carpenter ant treatment take?" becomes "One visit, then a check at 30 days; if the nest is inside a wall, plan on a second application, and damaged wood still has to be repaired." Every short answer counts double, because nobody will read you in full: according to the Nielsen Norman Group (2008), a visitor has time to read at most 28% of the words on a page, and 20% is more realistic. When I review the FAQ of a criminal defence firm, "Will I go to jail?" almost always gets "every case is different": true, and exactly the sentence a lawyer with no experience would write too.
Google's raters look for expertise in the content itself. Google has its results graded by people who follow a public manual, the Quality Rater Guidelines. Section 3.4 defines expertise as the knowledge or skill needed for the topic, with this example: whom would you trust for home rewiring advice, a skilled electrician or an antique homes enthusiast who knows nothing about wiring? The same section adds that for some types of pages, the level of expertise is clear from the main content itself. A FAQ page is the textbook case: ten questions, ten answers, and each answer shows whether you know your subject. The rater does not need to know your trade to tell "it depends on several factors" from "it depends on the pitch: asphalt shingles are not made for a nearly flat roof, you need a membrane". The first sentence could come from anyone. The second can only come from someone who has installed a roof.
Good questions come from your customers, not from a keyword tool. Before writing a single answer, pull out the real questions: the emails, the calls to the front desk, the objections heard in meetings, the questions that keep coming back on your Google business profile. That is where the exact wording people later type into Google hides, and it is what the Needs Met signal measures: does the page answer what the person came for? A question invented to fit a keyword is spotted at once, because nobody asks it that way. On topics that touch health, money or the law, what Google calls YMYL, precision becomes a safety matter. "Can I stop my treatment if I feel better?" calls for an answer that says no, why, and when to call the clinic back; not a generic "ask your doctor" that sends the person back to square one. A good answer on a sensitive topic gives the rule, the limit of the rule, and the way out to a human.
Answer engines lift your question and answer pairs as they are. ChatGPT, Claude or Perplexity build their answers from short passages that stand on their own. A question followed by a complete three-sentence answer is the easiest format to quote there is; an answer that says "see our services page" gives them nothing. FAQ schema (a block of JSON-LD code that declares your questions to Google) is no longer a visibility shortcut: Google first limited FAQ rich results to authoritative government and health websites in August 2023, then removed them from its results as of May 7, 2026, according to the Google Search Central changelog. It still helps describe the page to machines, as long as you only declare questions visible on screen. Finally, an expert FAQ knows where it stops: the last question leads to visible customer service, a phone number or a form for everything the page did not foresee.
The NeuroEEAT scoring grid (0-10)
Rate your FAQ as a reader in a hurry who wants a real answer, not as the person who wrote it.
| Score | Description | Concrete indicators |
|---|---|---|
| 0-2 | Decorative | No FAQ, or five generic questions ("Do you ship everywhere?") with one-word answers. Nothing a competitor could not write in your place. |
| 3-4 | Copied | Questions lifted from competitors or pulled from a tool, and vague "it depends" answers. No date, no number, no exception. |
| 5-6 | Real | The questions come from your customers and every answer gives at least one concrete element. The page is reachable from the menu and signed. |
| 7-8 | Expert | Every answer carries the condition and the exception, trade vocabulary is explained, sensitive questions say when to call. The page is dated and revised. |
| 9-10 | Reference | The FAQ grows from the new questions you receive, each answer links to the detailed page, answer engines pick up your wording, and the markup matches exactly what is on screen. |
How to audit it on your site
What your FAQ page really gives people to read, checked in five points.
- 01
Check that the questions come from your customers
Take the last ten questions you received by email or phone. How many are on the page, in the customer's words? If the FAQ asks questions nobody has ever asked you, it was written for a tool, not for a reader.
- 02
Read each answer as a competitor would
For every answer, ask: could a competitor with no experience write it word for word? If so, it proves nothing. Add the number, the timeline, the condition or the exception that cannot be made up.
- 03
Hunt for the "it depends" left on its own
An "it depends" is not a mistake, as long as you say on what. "The price depends on the surface: expect this much for an apartment, that much for a house" answers; "contact us for a quote" does not.
- 04
Test the sensitive questions
On a health, money or legal question, the answer must hold the rule, its limit and the moment to call a professional. An answer that only redirects elsewhere leaves the reader exactly where they were.
- 05
Compare the code with the screen
If the page carries FAQ schema, open the code and check that every declared question is visible, with the same answer. Questions hidden in the code for Google are what the rater guidelines call deceptive, and it takes a minute to spot.
How to activate or improve it
Where to start depending on the time you have, from the first real question to a FAQ that keeps itself current.
Swap the decorative questions for the real ones
- Pull the ten questions you get asked most often, in the customers' exact words, and keep them as is for the headings.
- Answer each in three sentences: the direct answer first, then the condition, then the exception.
- Delete any question whose answer is a bare "yes" or "no".
- Put the FAQ in the menu or at the bottom of service pages, not only in the footer.
Make every answer checkable
- Add a number, a timeline or a price to every answer where you can, with the year when the figure changes.
- Explain the technical term inside the answer, in half a sentence, instead of leaving it to the reader.
- End the longer answers with a link to the page on your site that covers the topic in depth.
- Sign the page: name and role of the person who wrote or validated the answers, with the date of the last revision.
- Add a final question, "Did not find it?", that leads to a phone number or a form.
Turn it into a living page
- Keep a log of new questions from email, phone and your business profile; add any that comes up three times.
- Every quarter, compare your questions with the "People also ask" boxes Google shows on your queries, and fill the gaps.
- Declare in JSON-LD only the pairs visible on screen, and remove the markup from pages where the FAQ is gone.
- Link each sensitive question to the external reference page when one exists (professional body, public agency), with its date.
- Ask your own questions to ChatGPT or Perplexity and see whether your wording gets picked up or ignored.
5 common mistakes to avoid
Sector specifics
Dental or physiotherapy clinic
The questions arrive before the first appointment: "Does it hurt?", "How many sessions?", "Is it covered?". The expert answer gives the range, the factor that moves it and what will be confirmed at the exam. It is validated and signed by a professional of the clinic, with the date, because the rater guidelines expect more accuracy as soon as health is involved.
Criminal defence firm
The FAQ is read at night, on a phone, by someone who was just arrested or by a relative. "Will my name be in the news?" deserves a real answer: what is public, what is not, and when. A page that answers "every case is different" to every question loses the reader at the moment they were about to call.
Exterminator, roofer, plumber
Your questions are very concrete: timeline, preparation, price, warranty, what happens if it rains. Answers with a timeline and an indicative price set you apart from the competitor who answers "contact us", and they feed straight into your Google business profile, where the same questions come back.
SaaS and agencies
Here the FAQ replaces the qualification call: integrations, data security, contract length, what happens on cancellation. Buyers compare three vendors at once; the answer that gives the precise limit ("exports up to 50,000 rows, beyond that through the API") wins against "contact your representative".
Signals to activate in parallel
A precise FAQ rests on other signals. These decide whether your answers are believed:
FAQ
What is a FAQ page on a website?
A FAQ page (frequently asked questions) gathers the questions your customers ask most often, with a short answer under each one. Its useful job: answering in advance, at any hour, what your front desk repeats every day. For Google and for the raters who read the page, it is also proof of expertise, because the quality of the answers shows at once. A FAQ of ten generic questions does neither job.
How to create a FAQ page on Shopify or WordPress?
The platform does not matter; the questions do. Shopify, WordPress, Wix or plain HTML all let you build a page with headings and short paragraphs, which is all a FAQ needs. Start from the questions you received, not from a template: emails, calls, objections in meetings, questions on your business profile. Keep the customer's wording as the heading, answer in three sentences, sign and date the page, and end with a question that leads to a human. Add an accordion or a search bar only once the page passes about fifteen questions.
How to structure a FAQ page?
Most asked questions first, grouped by topic once you pass ten or so (before the job, during, after, price, warranty). One question per heading, in the customer's words. Under it, the direct answer, then the condition, then the exception, then a link to the detailed page when there is one. Sensitive questions carry the rule, its limit and when to call. The last block is always the way to reach a person for whatever the page did not cover.
How to make a good FAQ page?
Write every answer as if the customer had asked on the phone and you had thirty seconds. Answer first, context after. A number, a timeline or a price whenever possible, with the year if it changes. Explain the technical word inside the sentence. Then reread each answer asking whether a competitor with no experience could have written the same thing; if yes, make it more specific. Sign the page, date it, and revise it from the new questions you keep receiving.
Is FAQ schema still worth adding?
For a special display in Google, no: Google removed FAQ rich results from Search on May 7, 2026, after limiting them to authoritative government and health websites since 2023. For describing your page cleanly to machines, yes, on one condition: declare only the questions and answers visible on screen. Markup never replaces the quality of the answers; it describes it. If in doubt, work on the answers first and the code second.
Case study
Before · four sites tracked by Marie Haynes, with no FAQ and no proof of expertise
After · product FAQ added, among several proofs of expertise
Source: Search Engine Journal (Marie Haynes), 2026, https://www.searchenginejournal.com/4-sites-that-recovered-from-googles-december-2025-core-update/567960/ · The product FAQ is one action among several carried out at the same time: the result cannot be attributed to it alone. The case shows where a FAQ sits in a set of expertise proofs.