Operator Intelligence from Evolette Locin: Agentic SEO and Technical Dominance, Singapore
1. The Operational Flaw: Writing FAQs for a Search Feature Instead of a Buyer
For several years, the FAQ block was the most over-produced section on Singapore SME websites. Agencies added eight to fifteen questions to the bottom of every service page, wrapped them in FAQPage structured data, and sold the result as a way to take up more space in Google’s results with expandable question-and-answer dropdowns. Many of those questions were never asked by a customer. They were keyword variants dressed as questions: “What is the best business consultant in Singapore?”, “Why choose us?”, “How much does a tennis lesson cost in Singapore?” answered with a sentence that avoided giving a price.
That justification has now expired. In August 2023 Google restricted FAQ rich results to well-known, authoritative government and health websites, which removed them for almost every commercial site. In May 2026 it went further. Google’s FAQ structured data documentation now states that FAQ rich results are no longer appearing in Google Search, and that the search appearance, the rich result report and Rich Results Test support are being dropped. Google published no blog post and gave no reason.
The costly mistake is not that a founder paid for FAQ markup in 2021. It is what happens next. One group of founders will tell an agency to strip every FAQ section because “FAQ is dead”, and lose the content that was answering real buyer objections. Another group will keep paying for keyword-stuffed question lists on the strength of a new promise: that FAQ schema is now the secret to being cited by AI Overviews and chat assistants. Neither decision starts from the right question, which is whether the answers on the page reduce the work a buyer has to do before they commit.
On the AI claim, be precise. Google has not said that FAQPage markup earns a place in AI Overviews or AI Mode. Its position on AI features, which we covered in AI Overviews and the fact record, is that there is no special markup required; the same fundamentals of crawlable, helpful, consistent content apply. Anyone selling FAQ schema as an AI citation lever is selling a hypothesis as a guarantee.
2. The Live Proof-of-Concept: FAQs Built From the Enquiry Log, Not the Keyword Tool
Every business in our portfolio takes its enquiries through WhatsApp, which gives us something most websites never look at: a written record of every question a buyer asked before booking. That record, not a keyword tool, is where our FAQ content comes from.
At TAG International Tennis Academy, the questions parents ask before a first lesson are concrete: which venue, what level the group is pitched at, whether a missed session can be made up, what happens when it rains, and what the package costs after the trial. Those are the questions worth answering on the programme page, with the actual policy, because every one that is answered in writing is one fewer message for a coach to handle between sessions and one fewer reason for a parent to hesitate. At PickleChoo, the pre-booking questions are about court access, paddle rental and how block bookings work. At Miyu Omakase, they are about dietary restrictions, seating times, deposits and cancellation. At Winchester Tennis Arena, they are about court hire versus coached sessions.
Notice what these questions have in common. None of them is a keyword variant. Each one is a point of friction that, left unanswered, either costs a staff member time or costs the business a booking. The FAQ section is a written policy layer that sits between the marketing copy and the WhatsApp conversation. Whether Google shows it as a dropdown has no bearing on that job.
As with the rest of this series, we do not publish enquiry volumes, conversion rates or ranking positions for these properties in a public essay. What we can describe is the method, which connects directly to thread ownership in a shared WhatsApp inbox and the one-intent-per-page rule in our keyword cannibalisation build.
3. The Execution Architecture: A Five-Step FAQ and Schema Reset
Step 1: Inventory what is live. Have an agent crawl the site and list every page carrying an FAQ section, every page carrying FAQPage markup, and every place where the two disagree: markup with no visible questions, visible questions with stale markup, or the same question answered differently on two pages. Duplicate FAQ blocks copied across ten service pages are common, and they are a quieter version of the cannibalisation problem.
Step 2: Mine the enquiry log. Export three to six months of WhatsApp and email enquiries. Use an agent to cluster the questions by theme and count how often each appears, removing names and contact details before the data goes anywhere. The output is a ranked list of real buyer questions per service. This list replaces the keyword-derived questions, not the other way round.
Step 3: Answer with the policy, not a deflection. Every answer should state the actual rule: the price or price range, the cancellation window, the make-up policy, the deposit amount and when it is forfeited. If the honest answer is “it depends”, say on what. A vague answer to a commercial question tells the buyer you are hiding something. A precise answer is also a representation to the public, so it must match your terms and conditions and the way your staff actually apply them. Where the answer has contractual weight, the FAQ should link to the governing terms rather than restate them loosely.
Step 4: Decide the markup on maintenance cost, not on hope. FAQPage markup that accurately mirrors visible content is not reported to cause problems, so there is no need for an emergency removal project. There is also no Google search appearance left to earn from it. The practical rule: keep accurate markup where it already exists and costs nothing to maintain; do not pay for new FAQ markup as a rankings or AI-citation tactic; and remove any markup that no longer matches the page, because a machine-readable claim that contradicts the visible page is a trust problem. Put the effort into the structured data that still describes your business as an entity, such as Organization, LocalBusiness, Person and Article, kept consistent with your Google Business Profile.
Step 5: Close the loop every quarter. Once a quarter, compare the new enquiry log against the FAQ sections. A question that keeps arriving on WhatsApp despite being answered on the page means the answer is buried, unclear or wrong. A question that has disappeared from the log means the page is doing its job. This is the only FAQ metric that matters to a business that sells through conversation.
The same discipline applies to the other search feature SMEs chase: star ratings. Google’s review snippet guidelines state that where the entity being reviewed controls the reviews about itself, those reviews are ineligible for the star review feature, including reviews embedded through a third-party widget on your own site. Marking up your own testimonials to win stars was never a durable plan. Real reviews belong on your Google Business Profile, where buyers and Google can see them on neutral ground.
4. The Asymmetric Advantage: Why Agencies Cannot Write These Answers
An hours-billing agency writes FAQs from a keyword tool because that is the only data it has. It does not see your WhatsApp threads, it does not know which question makes a parent go quiet for three days, and it cannot commit your business to a cancellation policy. So it writes answers that sound helpful and say nothing, then marks them up for a search feature that no longer exists. When the feature disappears, the agency’s next deliverable is usually to remove the work it sold you, or to rename it as AI optimisation.
The academic consultant has the reverse limitation. They can explain structured data vocabularies precisely and recommend best-practice FAQ formats. They cannot tell you whether your make-up lesson policy is costing you retention, or whether the deposit wording on your omakase booking page is creating disputes at the counter. Those are operating decisions, and the FAQ is where they become public.
Our advantage is that we answer the questions from the same seat that receives them. We run the enquiry lines, we set the policies, and we carry the consequences when a published answer and a staff member’s reply do not match. Agentic tooling lets us cluster thousands of enquiry messages and audit FAQ markup across a multi-site portfolio quickly. The decision about what the business is willing to commit to in writing stays with the operators who have to honour it, and we read each published answer the way we read a contract clause.
5. The WhatsApp Conversion Bridge: Request a Private Portfolio Audit
A quick test for your own site: take the last fifty enquiries your business received and mark each question that is already answered, clearly and with the actual policy, on the page the buyer came from. Then open your FAQ sections and mark each question that no buyer has asked in the last six months. The gap between those two lists is the work. In a Private Portfolio Audit we map every FAQ section and every piece of structured data across your properties, clean out markup that contradicts the page, rebuild FAQ content from your real enquiry log, and check each published answer against the terms you actually enforce.
Request a Private Portfolio Audit via WhatsApp.
How this article was produced: researched and drafted with AI-assisted tools under Evolette Locin’s operator methodology, with Google’s published FAQ and review snippet structured data documentation, and industry reporting on the May 2026 change, checked at the time of writing. This article is general commercial commentary, not legal or financial advice. Search engine policies change; confirm current platform documentation before restructuring structured data on live pages.