Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
SEO

Schema for Telehealth Landing Pages: SoftwareApplication and MedicalWebPage

A guide to marking up a telemedicine landing page: app, consultation service, pricing and reviews, plus the claims a health tech startup should keep out of structured data.

Schema for Telehealth Landing Pages: SoftwareApplication and MedicalWebPage

A telemedicine startup's landing page carries several jobs at once. It introduces a company, promotes an app, sells a consultation, and often explains a clinical service. Developers tend to cover all of that with one block of structured data, usually SoftwareApplication pasted from a template with a five-star rating that nobody can trace. That block is the most likely thing on the page to cause trouble.

This article is for founders, product marketers and SEO leads at health tech companies in India and the GCC who want their landing pages marked up accurately. It explains which schema.org types fit which part of the page, what Google actually reads for software apps, how to model consultation pricing separately from the app, and a list of claims that should stay out of structured data altogether. It is a markup guide; the regulatory reading of what a telemedicine platform may say belongs with your legal and clinical leads.

If the page layout itself is your problem, start with our piece on landing page design for healthcare ads. This one is about the machine-readable layer underneath it.

Decide what the page is before choosing a type

A common mistake is to type the whole page as a MedicalWebPage because the product is healthcare. Schema.org defines MedicalWebPage as "a web page that provides medical information", with properties like medicalAudience, lastReviewed and reviewedBy. A page that sells an app is a commercial page. A page that explains how a video consultation works, or what to prepare for one, may be a medical information page.

Use this split:

PagePrimary typeSupporting entities
Home or product landing pageWebPageOrganization, MobileApplication or WebApplication, Service
"How teleconsultation works" explainerMedicalWebPagereviewedBy, lastReviewed, Organization
Specialty page ("consult a dermatologist online")MedicalWebPage if it carries clinical information, otherwise WebPageService, MedicalSpecialty
Pricing pageWebPageOffer, UnitPriceSpecification

If a page has clinical content, the reviewer fields should name a real clinician who reviewed it, and the same name and date should appear in the visible byline. Markup that names a reviewer the page does not show is a mismatch that readers and quality raters can see. Our E-E-A-T content framework article covers how to run that review.

What Google reads for the app

Google's software app structured data documentation lists three requirements for the rich result: name, offers.price, and either aggregateRating or review. Recommended properties include applicationCategory and operatingSystem. The list of supported categories includes HealthApplication, which is the right value for a consultation app. Google also supports the subtypes MobileApplication and WebApplication.

Three implications:

  • A free app sets offers.price to 0. Per the documentation, if the app is available without payment, price is zero. This is about the app download, not the consultation fee. Do not put a consultation price on the app node.
  • Without a rating or review you are not eligible for the rich result. That is a legitimate outcome. Omit the rating rather than invent one. Rich results are not the only reason to mark up the app: the node also tells crawlers and AI systems what the product is.
  • Use MobileApplication for the iOS and Android app and WebApplication for the browser version. If both exist, declare both, with separate operatingSystem values and separate download links.

A reasonable set of additional properties from the schema.org MobileApplication and SoftwareApplication vocabularies includes installUrl or downloadUrl, featureList, screenshot, inLanguage, countriesSupported and softwareVersion. Populate only what the page itself shows. featureList is where overreach starts, so it gets its own section below.

Ratings and reviews: only what the page can prove

Google's review snippet guidelines require that ratings and reviews are about the item, are visible to users and follow the policies for the type. The self-serving review restriction applies to local business and organisation types; an app is an eligible type, but the other rules still bind.

For a telehealth startup the usable approach is:

  • Use aggregateRating only if a real, auditable rating source exists, such as store ratings collected from users, and the same figure and count appear on the page with a visible source.
  • Keep the count current. A static ratingCount of 10,000 that was true last year turns into a liability the day someone checks.
  • Never mark up testimonials from clinicians, advisors or staff as user reviews of the app.
  • Patient testimonials about care are a different matter. They raise consent, confidentiality and advertising-rule questions that markup does not solve. Keep them out of structured data unless your legal reviewer has cleared the underlying content for publication. Our guide to compliant testimonial video explains the issues.

Model the consultation as a Service, not as the app

The app and the consultation are different products. Model them separately.

  1. The consultation is a Service with serviceType (for example "Teleconsultation"), name, description, areaServed and availableChannel.
  2. The channel is a ServiceChannel with serviceUrl pointing at the booking flow and availableLanguage for the languages you really support.
  3. The price goes on an Offer attached to the service, with price, priceCurrency, and eligibleRegion where it varies by country.
  4. Plans (for example a monthly subscription) use UnitPriceSpecification with a billing period, or separate offers per plan. Mark up the plans that appear on the page, with the same names.
  5. The provider is the entity delivering care. If your platform connects patients to independent clinicians, the platform is a broker and the clinicians' organisation or practices are the provider. If the platform is the provider through employed or contracted doctors, say so. The answer depends on your licensing and contracts, so ask the legal team before choosing.

This keeps "the app is free to download" and "a consultation costs a stated amount" both true in the markup and on the page, which is also what users expect to read.

Want this applied to your practice? Get a free seo audit.

Book my free audit

India and the GCC: language, currency and region

For a company serving India and the Gulf, the page set is rarely identical across markets. Practical rules:

  • Separate pages per market where price, licence or clinician pool differ. One page with an Offer in rupees and another in dirhams is clearer than one page with both and an ambiguous eligibleRegion.
  • Declare language per page. Use inLanguage on the WebPage and availableLanguage on the channel to match what is genuinely supported. Do not claim Arabic support in the channel if only the marketing site is in Arabic.
  • Declare supported countries on the app. countriesSupported should list where the product can lawfully be used, not where the marketing team hopes to launch.
  • Do not borrow credentials across jurisdictions. A licence in one country does not describe your operation in another. Where a UAE or wider GCC page mentions regulatory status, align it with what the relevant authority actually granted, and check our UAE and GCC notes before publishing.

Claims that should not be marked up

Structured data is a statement of fact in a format that copies easily into other systems: snippets, aggregators, AI answers. Anything you would hesitate to print in a regulator's inbox should not be in it. The following are common offenders in telehealth featureList, description and Service text:

  • Outcome language such as "cures", "reverses", "reduces risk" or "accurate diagnosis". Even where the product has clinical evidence, a feature list is the wrong place for it.
  • Availability promises such as "doctors available 24x7" or "consult in 5 minutes" unless the operations team has a service level they can meet at peak load.
  • Credentials and approvals that cannot be verified on request. If a product is described as meeting a standard, name the standard and link to the document on the page.
  • AI capability claims. If symptom checking or triage uses AI, describe what it does in neutral terms and state that a clinician makes the decision, if that is true.
  • Doctor counts and ratings without a dated source on the page.
  • Prescription language. Whether and how prescriptions are issued during a teleconsultation depends on the jurisdiction and the clinician; leave it to the visible, reviewed text.

A good test is whether the same sentence appears on the page, was approved by someone who would defend it, and can be dated. If not, drop it from the markup.

A sample graph, described rather than pasted

For a single landing page, a clean graph has these nodes, linked by @id:

  • Organization for the company, with sameAs links to profiles you control.
  • MobileApplication named exactly as in the app stores, applicationCategory HealthApplication, operatingSystem Android, iOS, offers with price 0.
  • Service for the teleconsultation, provider or broker referencing the right party, offers with the consultation price, availableChannel with the booking URL.
  • WebPage for the landing page, about referencing the Service, publisher referencing the Organization.

Resist adding MedicalCondition nodes for every condition the app addresses. They invite claims the page cannot support, and the page should link to reviewed condition content instead. The wider entity patterns are in our healthcare schema guide; the schema markup service page describes how we implement them.

Test and monitor

  1. Validate with Google's Rich Results Test and the Schema Markup Validator. The first tells you about Google features; the second checks vocabulary correctness.
  2. Compare each marked-up fact to visible text, using a crawl that extracts JSON-LD and page copy side by side.
  3. In Search Console, watch the pages in the Performance report for brand and non-brand queries after each change, and annotate the date so you can tell later what moved. Treat any shift as a hypothesis to examine, not proof of effect.
  4. Re-run after every release. Single-page apps and tag managers often change the rendered output without anyone editing the markup.

Checklist for the telehealth team

  • Each page typed for its purpose; MedicalWebPage only where there is reviewed clinical content with a visible reviewer.
  • App marked up as MobileApplication or WebApplication, HealthApplication category, price 0 if the download is free.
  • Consultation modelled as a separate Service with a channel and a price in the right currency.
  • No aggregateRating without an auditable source shown on the page.
  • No outcome, speed, approval or AI-capability claims in featureList or description that the page does not carry and the compliance reviewer has not cleared.
  • Market pages separated, with language and region declared accurately.
  • Markup re-tested after each release.
Filed underhealthcare app schema markuptelemedicine schema markupSoftwareApplication schema health appMedicalWebPage schematelehealth landing page SEOhealth app structured data

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free seo audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to schema for telehealth landing pages softwareapplication and.

Explore client work →