Telehealth Visit Stack
Telehealth visit pages with MedicalClinic + Service + FAQ context and breadcrumb navigation.
When to use this stack
- Telehealth visit landing pages for clinics
- Virtual care pages that need provider + service clarity
- Pages with FAQs on eligibility, scheduling, and insurance
What is included
Anchors the clinic’s identity, NAP, and URL.
Describes the telehealth service, provider, and area served.
Answers eligibility, scheduling, and insurance questions.
Provides navigation context for the telehealth page.
Properties across the bundle
Nested properties keep their parent path, such as offers.priceCurrency. Only publish values that match visible page content.
Required properties
- address.addressCountry
- areaServed.name
- itemListElement[].name
- mainEntity[].@type=Question
- mainEntity[].acceptedAnswer.text
- name
- offers.price
- offers.priceCurrency
- provider.@id
- serviceType
- telephone
- url
Recommended properties
- address.addressLocality
- address.addressRegion
- address.postalCode
- address.streetAddress
- description
- itemListElement[].item
- logo
- mainEntity[].acceptedAnswer.text
- mainEntity[].author.name
- mainEntity[].name
- offers.availability
- offers.url
Combined JSON-LD
Paste this as one script tag, then replace every example value with data from the live page.
[
{
"@context": "https://schema.org",
"@type": "MedicalClinic",
"@id": "https://www.example.com/telehealth#clinic",
"name": "Evergreen Health Clinic",
"url": "https://www.example.com/telehealth",
"telephone": "+1-312-555-0100",
"address": {
"@type": "PostalAddress",
"addressCountry": "US",
"streetAddress": "123 Main St",
"addressLocality": "Chicago",
"addressRegion": "IL",
"postalCode": "60601"
},
"logo": "https://www.example.com/assets/logo.svg"
},
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://www.example.com/telehealth#service",
"name": "Telehealth Visit",
"serviceType": "Telemedicine",
"description": "Virtual primary care visits with licensed clinicians. Same-day appointments available.",
"provider": { "@id": "https://www.example.com/telehealth#clinic" },
"areaServed": { "@type": "AdministrativeArea", "name": "United States" },
"offers": {
"@type": "Offer",
"price": "79.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"url": "https://www.example.com/telehealth#book"
}
},
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do you accept insurance?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We accept major insurers and provide a cash option. Eligibility is confirmed during booking."
}
},
{
"@type": "Question",
"name": "Are visits same-day?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Most patients can book same-day appointments. Availability is shown in the scheduler."
}
},
{
"@type": "Question",
"name": "What conditions do you treat?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Primary care, urgent care, mental health consults, and prescription refills where appropriate."
}
}
]
},
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com" },
{ "@type": "ListItem", "position": 2, "name": "Telehealth", "item": "https://www.example.com/telehealth" },
{ "@type": "ListItem", "position": 3, "name": "Book a Visit", "item": "https://www.example.com/telehealth/book" }
]
}
]Implement and verify
- 01
Start with the live page
Confirm titles, prices, availability, policies, and visible FAQ content before generating markup.
- 02
Add one JSON-LD script
Use the combined example as a template in the document head or before the closing body tag.
- 03
Complete regional details
Fill shipping destinations and timing for every region the page actually serves.
- 04
Link the return policy
Use a stable MerchantReturnPolicy URL and keep its terms synchronized with the page.
- 05
Match visible answers
Add only FAQs that users can read on the same page, with identical answers.
- 06
Validate after changes
Run Rich Results Test after implementation and whenever price, availability, or policy data changes.
Common errors and fixes
- Missing currency or availability
Use ISO currency codes and complete schema.org availability URLs in Offer data.
- Incomplete shipping details
Include shippingDestination.addressCountry and deliveryTime.transitTime with units.
- Return policy is not connected
Reference MerchantReturnPolicy from the Offer and provide a stable public policy URL.
- FAQ answers differ from the page
Keep structured FAQ answers identical to visible answers.
Stack FAQs
Can I show multiple visit types?
Yes. If you list multiple visit types, include one Service per type with distinct @id values and tie them to the same MedicalClinic.
What if price varies by insurance?
If exact pricing isn’t displayed, omit price fields and keep offers.url/availability aligned to the CTA for the quoted flow.