A FAQ earns its place when it resolves a doubt that the rest of the page leaves open. “Do you offer SEO?” and “Do you build eCommerce websites?” may confirm a service, but give little guidance to someone choosing a provider. Questions about required data, costs, constraints, coverage and responsibilities help them assess the project.
This applies to a company looking for a partner in Jesi, a seasonal business in Rimini and an online shop connecting its warehouse. The context and the need change; replacing the city name in a standard answer is not enough. This guide explains how to choose questions, where to put them and how to check the content and implementation.
The work connects with technical SEO consultancy and AI content automation, but starts with an editorial question: what does the reader still need to make a decision?
The value of FAQs after FAQ rich results
Google announced that FAQ rich results stopped appearing on 7 May 2026 and later removed the documentation for the feature. The change is recorded in the official Google Search Central changelog. Writing FAQs to obtain that additional search feature is therefore no longer a current strategy.
The section can still help the page explain the offer, address objections and lead to more specific information. Those are goals to check, not guaranteed increases in traffic or conversions. A detailed answer matters because it supports a better decision, rather than because it meets a word count.
Look for questions where the customer gets stuck
Start with business sources: quote requests, support conversations, pre-sales messages and internal searches. Search Console adds the available queries, which do not represent every conversation or every search. A question proposed by AI remains a draft, rather than evidence of real demand.
A lightweight register can record the question, source, candidate page, verified answer and owner. Personal messages and customer details should not be copied into public content. A useful clarification can still be proposed without a source, but its frequency should remain marked internally as unvalidated.
- Recurring doubt: several customers ask how order history will move during a migration.
- Technical gap: the page describes an integration but does not explain what happens when the ERP is unreachable.
- Decision criterion: a customer wants to know when a standard platform is enough and when custom development deserves consideration.
The same sources help with questions on product pages. The answer must refer to the correct item or variant, without turning opinions or reviews into technical specifications.
Put the answer on the page that owns the need
On a service page, FAQs can follow the method and scope of work and precede the contact action. On a product page, they belong near the information that supports the purchase decision. A section anchor helps readers go straight to the questions.
The distribution follows a straightforward hierarchy:
- Local page: real coverage, working arrangements, territorial needs and operational conditions.
- Service page: decision criteria, required data, integrations, costs and limits that apply beyond the location.
- Article: explanations and comparisons needing more examples or steps.
- Help centre: shared procedures that customers also use after purchase.
A return policy or common procedure does not need a fresh version everywhere. Maintain an authoritative source and link from the relevant points. A FAQ should add a clarification rather than become a second service catalogue.
Three local examples that change the content
The following examples are editorial scenarios, not results attributed to clients. They use the Italian markets covered by BitHub, but the decision process can be applied to other real service areas.
Jesi: a B2B manufacturer looking for national buyers
“Should a company in Jesi that sells outside its region invest in local SEO?” distinguishes location from market. The answer can explain the role of a local page alongside pages about processes, materials and services searched for across Italy. The city name should not constrain every technical page.
The practical task is to define which enquiries matter, then connect territorial context with the main service pages. A business can have local and national needs, with different content and conversion paths.
Rimini: bookings completed on an external system
For a seasonal business, “how do we measure a booking completed on an external system?” introduces a concrete constraint. A useful answer separates a click on the booking button from a completed reservation, identifies the connections to check and explains the limits when the final data is unavailable.
Seasonality also needs consistent comparisons: summer growth and improvement caused by the project are not interchangeable. That issue deserves its own context rather than an identical answer on every city page.
Osimo: a technical catalogue with variants
A question about migrating variants and units of measurement needs identifiers, mapping rules and a trial import. It is more informative than “do you build eCommerce websites in Osimo?” The location provides context; the need is to preserve accurate technical data through the transition.
Near-identical location pages created mainly to target similar searches and lead to the same destination can fall within the issues described in Google's doorway abuse policy. A FAQ section alone does not fix a page without value of its own.
A useful answer explains conditions and the next step
A practical structure has three parts: direct answer, conditions that change the case, and the next check or action. It does not require formal language. It needs clear subjects and information the business can maintain.
Question: can an eCommerce website connect to an ERP without modern APIs?
Generic answer: yes, we integrate any ERP.
Useful answer: first we check the available exports, files, connectors and permissions. If the ERP cannot expose stock or orders in the required format, that limitation needs to be addressed with its supplier. A sample of products and orders allows the flow to be tested before it is extended to the catalogue.
The second answer helps the customer understand the work without inventing universal compatibility. The same applies to costs and timelines: explaining the inputs needed for a quote is more useful than an arbitrary number. Published prices should include consistent scope and conditions.
For eCommerce ERP integration, FAQs can explain synchronisation, duplicate orders, price lists and error recovery. The specialist explanation stays on the page that deals with that flow.
Making FAQs useful for AI answers
Google says its ordinary SEO practices apply to AI Overviews and AI Mode: accessible text, links and consistent structured data. It requires no special markup and does not guarantee inclusion. The source is its official AI features documentation.
An editorial implication is to make each answer understandable when read on its own. Name the process or product, explain conditions and sources, and avoid “it depends” without an explanation. That can make the content more useful as a reference; it does not establish that an assistant will cite it.
An AI chatbot connected to the catalogue also needs current sources and appropriate permissions. Publishing an order-related FAQ must not expose a customer's data. Collected questions can improve public content after review, while restricted actions remain in authorised systems.
Check the HTML, answers and outcomes after publication
An accordion can make a long page easier to scan. Start by inspecting the generated document: the answer should be present and accessible to the reader. A native element such as details can work without scripts; a custom component also needs keyboard and expanded/collapsed state checks.
- Test one question at a time on mobile and with a keyboard.
- Check that visible text and JSON-LD contain the same answer.
- Keep stable anchors for links to individual questions.
- Verify links and operational information are current.
- Assign ownership for reviewing locations, prices, compatibility and conditions.
In the BitHub FAQ revision, we used a shared source for HTML and structured data. The check detects differences between the two versions and unresolved links. That establishes implementation consistency, rather than an SEO outcome already achieved.
After publication, record the change date and observe relevant queries, qualified enquiries and questions that still reach support. Seasonal businesses need comparable periods. A search phrased as a question is not, on its own, evidence of a visit generated by an AI system.
Frequently asked questions about local SEO and AI content
Can FAQs still help SEO after FAQ rich results were removed?
They can help a page answer a search more usefully even without producing a FAQ rich result. Their value depends on relevance, accuracy and usefulness. There is no automatic improvement from the number of questions or the markup. Start with customer doubts and gaps in the page, then check relevant visibility and commercial outcomes after the update.
Should FAQs live on a general page or on each service page?
Questions that help someone choose usually belong on the relevant service or product page. A general page works for shared rules and support, such as contact methods or common procedures. The same block does not need to appear on every URL: keep a central source for shared answers and link to it from the pages where it matters.
Where can a business find real questions for local FAQs?
Collect pre-sales enquiries, support questions, internal searches and available Search Console queries. Group them by need and check them with the people delivering the service. A new question can clarify an important constraint, but it remains an editorial hypothesis until there is evidence that it is frequent. Adding a city name does not make the content local on its own.
How long should a FAQ answer be?
Long enough to resolve the doubt, without a universal threshold. A simple operational question may need a short answer; costs, integrations and migrations require conditions and limits. A useful structure answers directly, explains what changes the case and identifies the next check or step. If the topic needs several sections, create a separate guide and link to it.
Does an accordion hide answers from search engines?
An accordion can keep all the text in the HTML while letting the reader expand it. Check that the answer is already in the document, works with a keyboard and is readable on mobile. A component that downloads the text only after an interaction needs further checks. JSON-LD must describe an answer that a reader can actually access on the page.
Can AI write and publish all the FAQs on a website?
It can group questions and propose drafts, but publication needs reliable data and an editorial owner. Prices, locations, compatibility, timelines and conditions must be checked against business sources. If an answer is uncertain, state the limit or refer the reader to support. Generating many similar texts does not establish usefulness for customers or AI systems.
Bring customer questions into the right pages
A useful first step is to choose an important page, collect the doubts it leaves unresolved and verify the answers with the people who know the service. That creates a repeatable process with sources, owners and checks. FAQs become part of the offer and documentation, rather than a block added to make the page longer.