Google restricted FAQ rich results to mostly large, well-known sites in 2023, a change a lot of local-business SEO advice still hasn’t caught up to. This prompt builds the schema correctly regardless, but sets the expectation up front instead of promising a visual snippet a local service page is unlikely to get.
SEO
Build an FAQ schema block for a service page
A prompt for drafting FAQPage schema that mirrors real visible questions on a service page, structured to survive Google's stricter FAQ rich result eligibility rules.
Works with Claude / GPT1,900 uses★ 4.5
The prompt
seo-faq-schema-service-page
A local HVAC company's service page for "[AC repair in Phoenix, AZ]" has a visible FAQ section with 6 questions answered in plain text on the page (paste below), and wants FAQPage schema added so the questions might show as an expandable rich result. PAGE URL: [yourdomain.com/services/ac-repair-phoenix/] VISIBLE FAQ CONTENT ON THE PAGE (paste the actual questions and answers as they appear): [paste here] Build this the way someone aware Google restricted FAQ rich results mostly to authoritative government/health sites in 2023 would, so expectations are set correctly: 1. Confirm the 6 questions and answers are word-for-word what's visible on the page, since FAQPage schema must mirror visible content exactly, don't paraphrase or expand the answers in the schema beyond what a visitor actually sees. 2. Note plainly, before writing any code, that Google narrowed FAQ rich result eligibility significantly and now shows it mainly for well-known, authoritative sites, so a local business page having valid FAQPage schema doesn't mean the visual snippet will actually appear, set that expectation instead of implying schema alone guarantees it. 3. Write the JSON-LD using the exact visible text for each mainEntity Question and acceptedAnswer. 4. If any of the 6 answers reference something not stated in the question itself (e.g. an answer says "yes, we offer that" without the question specifying what "that" is), flag it, since ambiguous answers read fine to a page visitor with context but can look broken in a decontextualized snippet. 5. Note that even without the visual rich result, this schema still has value for AI-driven search summaries and voice assistants pulling structured Q&A content, so it's not wasted effort even if the SERP snippet itself doesn't appear.