What Makes a Telehealth Landing Page Pass Meta and Google Review?

What this means for you

• Both platforms review the destination as part of the ad. A compliant ad pointing at a non-compliant page is rejected because of the page.
• The page decides the account's category. A medication menu with prices reads as an online pharmacy and restricts conversion events across the account.
• Every page an ad can land on carries a prescription-required statement, provider credentials, a results-vary line and a real privacy policy.
• Compounded products are described as compounded, not FDA-approved, and never compared to the branded drug.
• Speed and intake length are conversion problems and review problems at once: Google scores landing page experience, and a nine-field form before the calendar loses half the people who clicked.

MedScale Health, a patient-acquisition agency for telehealth and clinics, builds and rebuilds telehealth landing pages because most healthcare sites were built by someone who did neither the policy read nor the intake math, and the ad budget pays for it every month. The rules below are what a page is read against. This page is marketing guidance for healthcare operators. It is not medical or legal advice, and platform policies change: check the sources listed at the end before acting on any specific rule.

The reviewer reads the page, and so does the classifier

Google's destination requirements cover what a final URL may and may not be: it has to work, match the ad, not cloak, not redirect through chains, and provide the contact and privacy information a user needs. Its landing page experience factors, which affect Quality Score and therefore cost, reward relevance, transparency and ease of navigation. Meta's drugs and pharmaceuticals standard applies to the ad and to where it leads: a page that promotes prescription drugs is prescription-drug advertising whether or not the ad named the drug, and requires LegitScript certification and Meta's authorization.

Separately from the human reviewer, Meta's systems classify the data source by what the site is about and restrict what a health-associated source may send. That classification is made from the pages, which is why a clinic that added a medication menu sees cost per consult climb without a single ad being rejected.

Pharmacy signals to remove

• Drug-name headlines and per-drug pricing tables without certification.
• Buy, order and add-to-cart language for a prescription product.
• "FDA-approved" on a compounded product, or any claim that it is the same as the branded drug. The FDA's 2026 warning letters to telehealth companies cited exactly those claims.
• Transformation imagery, numbers on a scale, and second-person copy about the visitor's body or condition.
• URLs and page paths that name a drug or a condition where a tracking event might carry them.

Elements every page needs

• The program and the prescriber first: what the visit is, who conducts it, what happens after.
• Medication detail second, framed as options a licensed prescriber may consider, with compounded status stated wherever a compounded product is named.
• A prescription-required statement and the candidacy conditions in plain language.
• Provider credentials, licensing, and the states served.
• A results-vary line and, where a testimonial appears, a statement of what is typical, in line with FTC guidance on health product claims.
• A real privacy policy, contact details and terms, which Google's destination requirements expect and Meta's review looks for.
• Once certified, the certification seal in the footer of every page an ad can land on.

Claims: what the FTC and the FDA read

The FTC's health products guidance requires that health claims be truthful, not misleading and substantiated by competent and reliable scientific evidence, with testimonials reflecting typical results or accompanied by a clear statement of what is typical. The FDA's letters to telehealth companies over compounded GLP-1 marketing cited unapproved-drug claims, sameness claims and missing safety information. A landing page that would draw either agency's attention also fails LegitScript, so the claim discipline is the same discipline that unlocks certification.

The intake path

The fewest fields sit before the booking and the qualification questions after it, with the calendar embedded rather than linked out wherever the booking tool allows. Where the patient must click out to an intake platform, the ad click travels with them so the booked visit, not the form fill, is what the campaign gets credit for. Consent language for texting sits on the form, because the speed-to-lead sequence that follows depends on it.

Speed

Google's Core Web Vitals set the thresholds a page is measured against: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, Cumulative Layout Shift under 0.1. A telehealth page loads under two seconds on a phone or it loses the click it paid for, and the hero image is usually the element that decides it.

Tracking on the page

Server-side events fire on every step with generic names. No form field or URL that contains a condition reaches an ad platform, no third-party pixel touches a health field, and identifiers are hashed to each platform's specification. Hosting keeps intake data where a business associate agreement covers it. The data path is documented so a compliance officer can review it.

One page per offer, not one per ad

A GLP-1 program and a TRT program need separate pages because the policy rules, the candidacy questions and the intake path differ. Two ads for the same program share a page. A med spa that adds a prescription weight-loss add-on separates it onto its own page so that the cosmetic pages never fall under the prescription-drug rules.

How to audit the page you already have

Read the page the way a reviewer does, top to bottom on a phone, and ask one question per screen: does this screen describe a clinic and a program, or does it describe a product for sale? A headline that names a molecule, a pricing table with one row per drug, a button that says order, a compounded product described as FDA-approved or as equivalent to a brand, an image that invites comparison of bodies, and a second-person sentence about the visitor's condition are each a pharmacy or a personal-attribute signal. Then open the network tab and read what the page sends when the form is submitted: any field, URL or event name that carries a condition or a drug to an ad platform is a tracking finding, and it is the finding that classifies the account.

Rebuilding without stopping the campaigns

Most pages can be fixed in the CMS they already live in: headlines rewritten around the program, the medication section moved below the prescriber and reframed as options, the required statements added, the images swapped for process imagery, the event names changed. Those changes go live behind the running campaigns and are followed by a policy read of the ads pointing at the page, because a page that now reads as a clinic exposes any ad that still reads as a pharmacy. A rebuild is scoped only when the structure itself is the problem, when the platform cannot host compliant tracking, or when the site is one page for every program and needs to become one page per offer. In either case the client owns the result: the code, the domain and the hosting account sit in the client's name from the first day.

What MedScale does

MedScale Health's websites and landing pages service (medscale.health/services/websites-and-landing-pages) starts with a policy read of the current site and a written list of what would trigger a restriction, then builds one landing page per campaign to the structure above, integrates intake and calendar, installs and verifies server-side tracking on every step, and tests one variable at a time on the page that gets the traffic, read against booked consults rather than click-through. Where the whole structure reads as a pharmacy or the platform cannot host compliant tracking, it scopes a rebuild and says so first. The client owns the code, domain and hosting from day one.