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:
| Page | Primary type | Supporting entities |
|---|---|---|
| Home or product landing page | WebPage | Organization, MobileApplication or WebApplication, Service |
| "How teleconsultation works" explainer | MedicalWebPage | reviewedBy, lastReviewed, Organization |
| Specialty page ("consult a dermatologist online") | MedicalWebPage if it carries clinical information, otherwise WebPage | Service, MedicalSpecialty |
| Pricing page | WebPage | Offer, 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.priceto0. 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
MobileApplicationfor the iOS and Android app andWebApplicationfor the browser version. If both exist, declare both, with separateoperatingSystemvalues 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
aggregateRatingonly 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
ratingCountof 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.
- The consultation is a
ServicewithserviceType(for example "Teleconsultation"),name,description,areaServedandavailableChannel. - The channel is a ServiceChannel with
serviceUrlpointing at the booking flow andavailableLanguagefor the languages you really support. - The price goes on an
Offerattached to the service, withprice,priceCurrency, andeligibleRegionwhere it varies by country. - Plans (for example a monthly subscription) use
UnitPriceSpecificationwith a billing period, or separate offers per plan. Mark up the plans that appear on the page, with the same names. - The provider is the entity delivering care. If your platform connects patients to independent clinicians, the platform is a
brokerand the clinicians' organisation or practices are theprovider. 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.




