A service-business website can answer dozens of questions without needing a dedicated FAQ page. Use a dedicated FAQ only when several recurring questions share a reader job and are clearer together than on their owning pages.

A question about a specific service should usually be answered beside that service. A question about what happens after contact should usually be answered on the contact path. The goal is not to own more questions. It is to let a buyer find the answer before they make the wrong next move.

Start with the question’s job

Before deciding whether a question belongs in an FAQ, write it as the buyer would ask it. “How does it work?” is not a useful category until you know what “it” refers to. “Do you serve my property type?” and “What happens after I request a quote?” are both common questions, but they belong near different decisions.

Use this placement tree:

  1. Does the answer decide fit, scope, preparation, or proof for one service? Put it on that service page. A buyer should not have to leave the service they are considering to learn whether it applies to them.

  2. Does the answer determine how someone should call, request a quote, book, or follow up? Put it on the contact or booking path. For example, a question about whether a calendar slot is a request or a confirmed appointment belongs where the action is offered. The contact-path guide helps make that distinction.

  3. Does the answer explain who the business is, how it operates at a company level, or what credentials it has? Put it on the About page. Identity and company proof are not miscellaneous FAQ material.

  4. Does the answer state a policy, contractual term, privacy practice, warranty condition, or eligibility rule that needs stable, complete wording? Put it on a policy page, terms page, or a clearly labeled service condition. Do not reduce something consequential to a one-sentence accordion answer.

  5. Do several related questions recur across more than one page, and does answering them together help a buyer compare or prepare? A dedicated FAQ page may be warranted. Group the questions by a real reader job, such as preparing for an estimate or understanding how service areas work.

  6. Is the answer unstable, private, dependent on an individual assessment, or not something the business is prepared to stand behind publicly? Do not publish it as an FAQ answer. Explain the appropriate next step instead.

That last branch saves a surprising amount of trouble. Pricing that varies materially by inspection, a customer-specific eligibility judgment, or a staffing decision for next Tuesday is not made clearer by a confident canned answer.

A page does not become an FAQ just because it has questions

Service pages, pricing pages, booking pages, and About pages can all use short question-and-answer sections. In many cases that is better than a separate FAQ URL because the reader receives the answer in context.

Keep an answer on its owning page when it:

  • needs the surrounding service description to make sense;
  • affects the next action on that page;
  • is short and stable;
  • uses evidence already present on the page; or
  • would become repetitive if copied into an FAQ archive.

Create a dedicated FAQ page when the questions are cross-cutting, recur often enough to justify maintenance, and benefit from being compared. The page needs a clear subject. “Everything you might ask” is not a subject. “How our service area, estimate process, and appointment requests work” might be — if those are genuinely recurring, stable public questions.

This article decides where cross-cutting questions should live. The published page-count article separately owns whether a topic merits its own page.

The matrix: useful question, useful location

Question pattern Best initial home Why it belongs there When a dedicated FAQ can also help
“Do you handle this kind of project?” Service page It decides fit and scope for a particular service. Only when the same qualification rule applies across multiple services and needs comparison.
“What should I include in a quote request?” Contact or quote path It changes what the buyer should do next. When several request paths have shared preparation rules.
“Who will perform the work?” About page or relevant service page It is company proof or service-specific staffing context. Rarely; do not hide accountability in a catch-all archive.
“What is your cancellation or privacy policy?” Policy page Stable terms need complete wording and a maintained owner. A short FAQ answer can point to the policy, not replace it.
“Which areas do you serve?” Service-area or service page It determines practical eligibility. When the answer needs a map or a comparison of several stable territories.
“Can you give an exact price before seeing the job?” Service or quote path It depends on scope and sets a real expectation. Only if a grouped estimate-preparation FAQ adds context without promising an answer the business cannot give.
“What time will someone arrive next week?” Nowhere public It is unstable and requires an individual operational answer. Never; give a contact method or current scheduling process instead.

The matrix is a routing tool, not a reason to add six new pages. Often the best cleanup is moving two answers onto the page that already owns them and deleting the rest.

Write answers people can act on

An FAQ answer should be specific enough to remove uncertainty and narrow enough that it remains true. “We provide exceptional service” is not an answer. “For a request-a-quote form, include the service, location, timing, and any details that change the next step” tells a buyer what to do.

Avoid these three shortcuts:

  • The evasive answer: “It depends” with no explanation of what it depends on.
  • The sales answer: a question used only to repeat a slogan or force a call.
  • The brittle answer: a precise claim about availability, price, time, or policy that no one has agreed to maintain.

Where a complete answer requires individual judgment, state the decision rule and explain who can confirm the result. That is more useful than publishing a fake certainty.

FAQ structured data is not the reason to create the page

FAQ content can be good for readers without producing any special Google result. Google discontinued FAQ rich results for all sites beginning May 7, 2026, and later removed the feature documentation. Useful visible FAQ answers still help readers; their value does not depend on a discontinued rich-result presentation. Google also says correctly implemented structured data does not guarantee a search appearance.

That means the order of operations matters:

  1. Publish the answer because a reader needs it.
  2. Keep the answer visible, accurate, and in the place that owns the decision.
  3. Do not treat FAQPage markup as a route to a discontinued rich result.
  4. Do not describe FAQ markup as a rankings, citation, or AI-visibility tactic.

An accordion is a presentation choice, not evidence that the question has a good home. Make sure the answer remains available and understandable to people before you decide how decorative or interactive the page needs to be.

Give the page a maintenance owner

Every FAQ carries an implied promise: this is what the business says now. Give one person or role responsibility for revisiting answers when services, territories, prices, policies, staff coverage, or contact paths change.

If nobody can name that owner, keep the page smaller. A short set of maintained answers beats an archive of once-true statements that customers now have to correct by phone.

A clean way to decide this week

List the twenty questions most likely to arrive before a request. Put each through the placement tree. If fewer than a handful genuinely belong together after that exercise, you probably need better sections on existing pages rather than a dedicated FAQ. If a coherent group remains, give it a clear reader job, assign an owner, and publish only the answers the business can keep current.

The result is less content, but more useful content. A buyer should not need to solve the site’s filing system before they can understand the business.

Sources