Building an FAQ Schema That Gets Allied Health Clinics Cited in Google AI Overviews and ChatGPT

30 August 2026·5 min read

Quick answer: FAQPage schema is a small block of code (JSON-LD) that tells Google and AI tools exactly which text on your page is a question and which is the answer — it doesn't guarantee a citation, but it removes the guesswork for machines trying to extract a quotable answer. Pair it with Q&A content written the way AI tools actually quote (direct answer first, one clear claim per question) and you've done the two things actually inside your control. Copy-paste template and formula below. ✨

Every clinic owner has heard "get your FAQ schema sorted" from an SEO person and nodded along without knowing what that means or whether it's worth the afternoon. It is — but not for the reason most people think. Google quietly stopped showing FAQ rich snippets for most sites back in 2023, so the SEO click-through boost is mostly gone. What schema still does is make your content easier for AI Overviews, ChatGPT and Perplexity to lift and quote accurately. Here's how to set it up. 💖

What most allied health clinics get wrong with FAQ schema

Copy-pasting the same five generic questions — "what are your opening hours" and "do you bulk bill" on every single page, adding no real information for AI tools to differentiate one page from another.
Schema that doesn't match the visible page — writing different or more detailed answers into the code than what's actually shown to a human reader, which breaks Google's structured data guidelines.
Vague, hedge-everything answers — "it depends, book a consult" gives AI nothing extractable to quote, even though it's often true.
Questions written how a clinic thinks, not how a patient searches — "our treatment philosophy" instead of "do I need a referral to see a physio."
Never checking it's valid — a typo in the JSON breaks the whole block silently.

The copy-paste schema template and Q&A formula

Drop this JSON-LD into the page `<head>` (or via your theme's custom code section), matching each question and answer to text that's also visible on the page:

For the content, use this formula per Q&A pair: question in real patient language → direct answer, first sentence → one supporting detail (a number, timeframe, condition) → a clinic-specific detail (location, booking). The first-sentence answer is the bit an AI tool lifts, so it must stand alone.

Three real examples

Notice each question is phrased the way a patient would actually type it, and the answer front-loads the direct response. 📈

Physiotherapy clinic doing home visits: Q: "Do physios do home visits on the Gold Coast?" A: Yes — we offer home visit physiotherapy across the Gold Coast for clients recovering from surgery or unable to travel. Visits are typically available within 48 hours and claimable through most health funds. Book online or call our Southport clinic.

Podiatry clinic treating diabetic foot care: Q: "How often should a diabetic have a podiatry check-up?" A: Most people with diabetes benefit from a podiatry check every 6 to 12 months, or more often with existing nerve or circulation issues. Regular checks catch problems early. We bulk bill eligible assessments under a GP care plan.

Speech pathology clinic for kids: Q: "At what age should I get my child's speech assessed?" A: If your child isn't combining words by age two, or is hard to understand by age three, it's worth booking an assessment — earlier support makes a bigger difference. We see children from 18 months, with NDIS and Care Plan appointments available.

The mechanics: getting it live and checked

Add one FAQPage block per page, matching only the Q&As visible on that page — don't reuse one giant sitewide block. Most Shopify and website themes have a custom code or "additional scripts" section for this; if you're not comfortable editing code, it's a five-minute job for a developer. Once live, run the page through Google's Rich Results Test or Schema Markup Validator to confirm it parses — a single missing comma breaks the block.

💡 Heads up: Google's structured data guidelines require the schema content to match what's visibly on the page — don't write a punchier answer into the code than what a patient actually reads. Mismatched schema can get ignored or, in worse cases, flagged as spam.

Mistakes to avoid

One schema block copied across every page — dilutes relevance and gives AI tools nothing page-specific to cite.
Answers over 2-3 sentences — AI tools extract the concise, direct part; long paragraphs get skipped.
Forgetting to update it — if a service or referral requirement changes, the schema needs updating too.
Treating schema as a silver bullet — it helps machines parse content; it doesn't replace useful answers.

Frequently asked questions

Does FAQ schema still help my Google ranking directly?

Its direct ranking impact is limited, and Google retired the visual FAQ rich snippet for most sites in 2023, so don't expect the old blue accordion in results. Its value now is mainly making your Q&A content machine-readable for AI Overviews and chatbots.

Will FAQ schema guarantee I get cited by ChatGPT or AI Overviews?

No — there's no guarantee with any AI visibility tactic. Schema removes ambiguity for tools that use it, but citation also depends on clarity, authority, and whether a competitor answered the question better.

How many FAQs should I add per page?

Three to six well-written, page-specific questions beats twelve generic ones. Specificity matters more than volume.

Can I use the same FAQ schema on every page?

Technically yes, but it defeats the purpose — each page's schema should reflect questions genuinely relevant to that page's service, not a blanket set repeated everywhere.

Please note: general information, not medical advice — check current official guidance before relying on it.