# How to Write an FAQ Page That Ranks and Gets Picked Up by AI > An FAQ page is just the questions you already answer by phone and email, written down once. That question-and-answer shape is what Google's "People also ask" matches and what ChatGPT and AI Overviews quote. *Roald, Founder Fonzy · Jul 5, 2026 · 8 min read* Source: https://www.fonzy.ai/blog/faq-page-seo --- The easiest piece of content you will ever publish is an FAQ page, and it works because you already wrote it in your head. Every question a customer asks by email or phone is one FAQ entry: the real question as the heading, your normal two-sentence answer right underneath. Take Lena, who shoots weddings under the name Lena's Lens. She answers the same eight questions every week. "Do you travel?" "How many photos do I get?" "Do you shoot the rehearsal dinner?" She types those answers into messages all day. Put them on one page, and she has an FAQ page that Google can match to searches and that AI assistants can quote. No new ideas required. No SEO degree. She just stops retyping the answers and publishes them once. Here is the honest version of why this matters now, and exactly how to write the page so it gets used. ## Why is an FAQ page the easiest content win you have? Because you are not writing anything new. You are transcribing. Most content advice asks you to come up with topics, research them, and produce something you have never made before. An FAQ page is the opposite. The questions already exist, sitting in your sent folder and your DMs. The answers already exist too, because you have typed them a hundred times. The only work is moving them from private messages to a public page. Lena spent one afternoon on hers. She opened her email, scrolled her last two months of replies, and copied the questions couples actually asked. She did not invent a single one. By the end she had eleven real questions and eleven plain answers. That is a finished FAQ page, and it took less time than editing one wedding gallery. The standard advice from SEO publishers backs this up. Ahrefs and Semrush both tell you to source FAQs from actual customer questions, support emails, chat logs, and reviews, rather than inventing them, and to keep each answer short, a paragraph or two at most. The lowest-effort version is also the recommended version. That almost never happens in marketing. ## How do you find the real questions customers ask? Pull them from four places you already have, in this order. Start with your sent email and DMs. Scroll back two or three months and write down every question a customer actually asked. These are gold because they are phrased the way real people phrase things, not the way a marketer guesses they might. Next, read your reviews on Google and Yelp. Reviews quietly answer questions: "I was worried she would not catch the speeches but she got every one." That tells you couples worry about speech coverage. Turn the worry into a question: "Do you photograph the toasts and speeches?" Third, check Google's "People also ask" box. Search your service plus your city, like "wedding photographer Portland," and look at the questions Google shows. Those are queries real people typed. If your answer is on the page, you become a candidate to match them. Fourth, sit with your own booking calls for a week and note what gets asked. Lena did this and found one question she had never written down: "What happens if you get sick on the day?" Couples were too polite to ask by email but asked on the phone. That answer, about her backup shooter network, now reassures every visitor before they have to ask. ## How do you write an answer that gets quoted? Answer first. Put the direct answer in the first sentence, then add context. Never wind up. Here is the difference. A weak answer to "How many photos do I get?" reads: "Every wedding is unique and we believe in capturing your special day in a way that reflects your individual story, so the number of images varies depending on a range of factors." That says nothing. A reader bounces and an AI assistant has nothing clean to lift. The strong version: "You get 400 to 600 edited photos from a full wedding day, delivered in an online gallery within four weeks. Smaller elopements run closer to 200." Direct number first, context second. A person gets their answer in one second. So does ChatGPT. Keep one rule: one question, one self-contained answer. Do not make the reader stitch three entries together to understand one thing. Each Q&A should stand alone, because that is exactly how AI systems lift them, as standalone pairs. Lena writes every answer in two or three plain sentences and stops. The brevity is the feature. ## What is the honest truth about FAQ schema and rich results? The old FAQ "rich result," that expandable dropdown of questions under a Google listing, is gone. Do not write your FAQ page to chase it, because it no longer exists for ordinary businesses. Here is the timeline, told straight. Search Engine Land reported that Google deprecated FAQ rich results on 7 May 2026: it added a deprecation note to its structured-data documentation, the expandable Q&A dropdown stopped appearing in Search, and Search Console reporting plus Rich Results Test support are being removed, with API support ending in August 2026. This was not sudden. It finished a withdrawal that started in August 2023, when, as Search Engine Journal recapped, Google restricted FAQ rich results to "well-known, authoritative government and health websites" only. Most ordinary business sites lost the FAQ snippet back then. A wedding photographer was never getting that dropdown after 2023 anyway. So if someone sells you FAQ schema as a Google ranking trick, they are selling you 2022. The FAQPage markup itself stays valid, and you can leave it on the page. It just does nothing for that Google dropdown anymore, because the dropdown is retired. After the May 2026 change, the r/SEO community debated whether to rip the schema out entirely. The recurring practitioner take, summarized in coverage of those threads, was practical: leave the markup in place, do not count on it for anything on the Google Search side, and treat its remaining value as helping AI systems that crawl structured content on their own. In plain terms, the schema is a quiet helper for machines, not a snippet generator. Write for the reader and for AI, not for a dropdown that died. ## How does an FAQ page feed AI Overviews and ChatGPT? A question-and-answer pair is the cleanest thing an AI system can quote, because it matches how people ask. When someone types "how many photos do you get from a wedding photographer" into ChatGPT or sees a Google AI Overview, the assistant wants a short, direct answer it can lift. Your FAQ entry is already shaped that way. This matters more every month because of where attention is going. A Pew Research Center study, published in July 2025 and based on the browsing of around 900 U.S. adults, found that users clicked a result link only 8% of the time when an AI summary appeared, versus 15% when it did not. Only 1% of the time did they click a link inside the AI summary itself. Read that plainly: when AI answers the question, most people never click through. So your goal shifts. You want to be the source the AI quotes, named in the answer, even when the click never comes. And these answer boxes are everywhere now. A Semrush study of more than 10 million keywords, run across 2025, found that "People also ask" boxes appear on about 90% of search results that also show an AI Overview. Question-style searches almost always trigger a question box. An FAQ page built from real questions is built for exactly that surface. Lena's answer to "do you travel for destination weddings" is now a candidate every time a couple asks an assistant that question, whether or not they ever land on her site. ## How should you structure the page so AI can extract it? Plain and flat. Real question as the heading, short answer directly underneath, nothing between them. Use the actual question as the visible heading, worded the way a customer would say it. "Do you travel for destination weddings?" beats "Travel and logistics." Put the answer in the very next line. No introduction, no "great question," no marketing wind-up. AI systems and skim-readers both grab the heading, then the first sentence under it, so that first sentence has to carry the answer. Avoid these four mistakes, because each one breaks extraction: - Fluffy, marketing answers that circle the point. If the first sentence is about your "passion for storytelling," the answer is buried. - Fake questions no real customer asks, written to stuff in keywords. AI and readers both smell these, and they crowd out the real ones. - Burying the answer under context. Context comes second, always. - Walls of text. Two or three sentences per answer. If it runs longer, it is probably a blog post, not an FAQ entry. Lena's page reads like a clean list. Question, answer, question, answer. You can scan all eleven in under a minute, which is exactly what both a couple and a crawler want. ## One FAQ page, or FAQs on every page? Start with one central FAQ page, because it is the easy win. Then move your best two or three questions onto the matching service page, because that often works harder. The central page is your starting point: low effort, everything in one place, simple to keep updated. Build that first and publish it. But a general FAQ page is a generalist. A question about destination travel pricing does more on the destination weddings page, sitting right next to the thing it answers. So once your central page exists, take the two or three questions most relevant to each service and drop them onto that service's page too. Lena did both. Her main FAQ page holds all eleven questions. Her "destination weddings" page repeats the three about travel, passports, and extra-day pricing, placed under the pricing section where couples are already deciding. Search engines and AI assistants reward that relevance, because the answer sits inside the page about that exact topic. The central page is the easy start. The on-page Q&As are where it starts to pull. If you want the bigger picture on turning everyday answers into bookings, see how an FAQ page fits a wider plan in [how to get more customers](/blog/how-to-get-more-customers). ## Frequently asked questions ### Should I still add FAQ schema to my page after the 2026 deprecation? You can leave it on, but do not expect anything from it on the Google Search side. The expandable FAQ dropdown was deprecated on 7 May 2026 and restricted to government and health sites back in August 2023, so ordinary businesses get no snippet from it. The markup stays valid and may help AI systems that crawl structured content, so leaving it in place is low-risk and reasonable. ### How many questions should an FAQ page have? Enough to cover the questions real customers actually ask, which is usually somewhere between eight and fifteen for a small business. Pull them from your sent email, your reviews, and Google's "People also ask" box rather than inventing them. If you cannot remember a customer ever asking something, leave it off. ### How long should each FAQ answer be? Two or three plain sentences, with the direct answer in the first one. Ahrefs and Semrush both recommend keeping answers short, a paragraph or two at most, and leading with the answer before any context. If an answer needs more room, it is really a blog post, and you should link to that instead. ### Will an FAQ page help me rank on Google? It helps you match question-style searches and "People also ask," and it gives AI Overviews and ChatGPT clean answers to quote, which matters now that most searches with an AI summary end without a click. It will not earn you the old FAQ rich-result dropdown, because that is retired. Think of it as being a quotable source, not winning a snippet. Lena did not write anything new. She moved the answers she already gives onto one clean page, then copied a few onto the pages where they mattered most. That is the whole method: transcribe the questions you already answer, lead with the answer, and let Google and the AI assistants do the quoting. Fonzy handles that groundwork for you, finding the real questions and shaping the answers so they get picked up, while you keep doing the work customers actually pay for. --- Published by [Fonzy](https://www.fonzy.ai) — expert articles that get you found on Google and AI search.