Published by Telehealth Ad Infra by AdsInfra

Google Ads healthcare certification for US telehealth providers

An operational preparation guide. Policy sources checked October 3, 2026.

For a US telehealth business that provides virtual care and facilitates prescribing, Google’s published healthcare policy identifies LegitScript Healthcare Merchant Certification as the relevant telemedicine accreditation. The advertiser must also obtain Google certification. Requirements depend on the service and target location; the word “telehealth” alone is not enough to choose an application category. Google Healthcare and medicines policy

LegitScript certification does not guarantee advertising approval. A useful preparation process therefore keeps certification, campaign review, audience settings and measurement decisions visible as separate workstreams. LegitScript Healthcare Certification FAQ

This guide helps growth and operations teams assemble a review file, assign owners and identify unresolved questions before submitting applications or launching campaigns. It focuses on Google advertising directed at the United States. It does not establish your legal eligibility, evaluate medical treatments, or provide legal or medical advice. Use qualified clinical, legal and privacy reviewers for those decisions. Other platforms and jurisdictions require their own current review.

Start with the service you actually offer

Write a short description of the customer journey before choosing a certification route. Who operates the advertised business? Who provides the consultation? Can it result in a prescription? Who dispenses medication? Which entity takes payment? Which organization owns each website the customer visits?

These questions are especially useful when a brand works with a separate clinical practice, provider network or pharmacy. A company label such as “technology platform” or “management services organization” does not explain the entire service. Describe each party’s role and ask the relevant reviewer to confirm the correct category where it is unclear.

Google considers the service offered and the content of the ad, website or app when applying its prescription-drug-services policy. Related links can matter too. An ad that mentions only a consultation does not, by itself, settle the classification of the destination. Google Prescription drug services policy

Create one working record for each proposed service and market:

• The advertised service in plain language
• The business responsible for it and the clinical and dispensing partners, where applicable
• The country and states you intend to target
• The public destination and any onward domains in the journey
• The proposed certification category and the person who confirmed it
• Questions still waiting for a clinical, legal, privacy or platform answer

Leave an unresolved item open rather than treating a previous campaign’s approval as evidence for a different service.

Prepare the evidence before opening an application

LegitScript’s official application checklist covers registration and licensing, telemedicine information, applicable compounding information, advertising claims, privacy, affiliates and partner pharmacies. It is a useful starting point, but use the current program standards and application instructions for the complete requirements. LegitScript application checklist

The worklist below is an operational aid, not an official certification checklist. For each item, record the owner, where the authoritative record is held, when it was checked and what remains unresolved.

Business and partner roles

Prepare a simple entity map covering the advertiser, clinical provider, dispensing partner and advertising agency, as applicable. Resolve differences between the public brand, the business named in application records and the party operating the website. Keep contracts and regulated records in the organization’s approved systems; the advertising worklist can reference their locations without copying their contents.

Service locations

Have the responsible professional confirm which services may be offered in each proposed jurisdiction. Record the resulting geographic limits for the media team. Do not turn a national growth target into an assumption that every partner can serve every state.

LegitScript’s standards address licensing in the jurisdictions a merchant serves. The practical task is to establish the actual permitted footprint for the proposed service. LegitScript Healthcare Certification standards

Websites and domains

Inventory root domains, subdomains, campaign pages and onward links so reviewers can understand the full journey. LegitScript’s FAQ says certification applies to the root domain, including its subdomains and subpages. Additional root domains require separate consideration. That does not remove the need to check Google’s account and destination requirements. LegitScript Healthcare Certification FAQ

For each destination, record its purpose, owner, associated service and current review status. Treat a new root domain, new service or changed partner as a question to resolve before launch.

Claims and supporting evidence

Create a claims list for the exact ads and pages being proposed. For every objective statement about a treatment, eligibility, price or expected outcome, identify the supporting evidence and the person authorized to approve its use. A general study, testimonial or supplier description should not be assumed to substantiate the exact wording on your page.

The advertising team should flag unresolved claims to the appropriate reviewer. It should not decide clinical appropriateness or draft a universal medical disclaimer to cover every offer.

Review ownership

Name one person responsible for assembling the file and separate owners for clinical claims, legal eligibility, privacy and campaign operations. Agree how questions move between them. A documented unresolved issue is more useful than several people assuming another team checked it.

Apply to Google for the correct account and domain

Google’s current instructions say healthcare applications must be made at the child account level, rather than the manager account or MCC level. Applicants must provide the Google Ads customer ID and certified domain. An agency applying for an advertiser must document its relationship with the advertiser or license holder. Google healthcare application instructions

In your working record, keep these fields together:

• Advertiser and service category
• Google Ads child account customer ID
• Certified domain
• Intended target locations
• Application owner and submission date
• Current status and the location of the official response
• Any stated conditions or unresolved questions

Use precise status labels such as “preparing,” “submitted,” “additional information requested,” “approved for recorded scope” or “declined.” An application receipt is not an approval notice. Avoid a broad label such as “healthcare approved” when the underlying record refers to a specific account, domain or scope.

Before moving an existing campaign to a different account, have the account owner confirm the applicable certification and verification requirements. A manager-account relationship is not evidence that an individual account has completed its required application.

Review the complete public journey

Assign someone outside the campaign build to follow the proposed ad through its destination and onward links. Use public pages and approved synthetic testing where needed. No real patient record is necessary for an advertising preparation review.

Check whether a reader can understand:

• Which organization is advertising and which organization provides care
• What the offer includes and what requires a separate decision or assessment
• Where the service is available
• The basis of any price or offer shown in the ad
• How to find relevant service terms and privacy information
• Whether the ad and destination describe the same offer

Record the page version and the date reviewed. If the page changes after sign-off, identify whether the change affects a reviewed claim, partner, service or data flow.

Prescription-drug terminology needs its own check. In the United States, Google distinguishes using drug terms in ad or landing-page content from keyword-targeting those terms. Its policy also retains certification requirements for specified business types, including telemedicine providers. Read both rules before concluding that a particular word is either universally prohibited or automatically permitted for your campaign. Google Restricted drug terms policy

This is a review of the real offer. Do not hide relevant prescribing or dispensing information from reviewers to change how the business appears.

Check audience settings independently

Google treats personal health content as a sensitive interest category. For promotions in sensitive categories, its health policy disallows advertiser-curated audiences such as Customer Match, your data segments, audience expansion and lookalike segments. Certain predefined Google audiences are permitted, subject to the stated conditions and exceptions. Google Health in personalized advertising

Make an audience inventory for the proposed campaigns. Record each audience feature, the source of its signals and the policy review outcome. Check inherited settings and templates as well as the settings the buyer intentionally added.

Avoid assuming that certification permits a retargeting plan. If an audience choice is unresolved, leave it out of the launch plan until the responsible reviewer confirms the permitted approach. Keep the public description of the service accurate while resolving targeting issues.

Give measurement a separate approval step

Google’s customer-data policy prohibits using conversions related to sensitive categories for measurement in enhanced conversions or store-sales uploads. Its examples include health or medical information, such as purchases of medical services, prescription drugs or medical devices. This is a separate requirement from the audience rules above. Google Customer data policies

Before enabling or changing measurement, prepare an event inventory for the privacy and technical reviewers:

• Where each event originates
• What it represents in the customer journey
• Every field and value it could contain
• Which systems would receive it
• Who approved that use and on what basis
• How the configuration will be tested and disabled if it behaves unexpectedly

Use synthetic values for testing. Check URLs, page titles, event names and free-text fields as well as the obvious identifiers. The review should examine what a recipient could learn from the event in context.

Do not treat hashing, server-side routing or a conversion API as a compliance conclusion. A technical transformation does not answer whether the proposed collection and sharing are permitted. Have qualified reviewers assess the actual configuration, applicable law and recipient policies.

Keep patient names, contact details, intake answers, diagnoses, prescription information and account credentials out of the advertising support packet. If a certification provider requires controlled test access or other restricted material, the authorized business owner should handle that through the provider’s approved secure process. A sales chat or general agency inbox is not the place for it.

Use a clear launch decision

A useful launch check ends with a named decision owner and a record of remaining limits. “The documents are in the folder” is not a decision about the campaign.

Use this final operational checklist:

• The service description and business roles are accurate
• The intended geographic scope has been reviewed
• Required certification and account records have been checked against the proposed campaign
• The exact ad and destination versions have completed the assigned review
• Audience settings have a recorded policy review
• Measurement has a separate privacy and technical review
• Unresolved issues have owners and are excluded from launch where necessary
• The team knows who can pause a campaign and who will handle a policy notice

This checklist supports a controlled internal decision. It cannot guarantee certification, approval, delivery or continued eligibility.

If an ad is disapproved

First identify what happened. An ad disapproval, a limited serving status, a certification problem, a billing issue and an account suspension are different situations. Record the exact notice before proposing a remedy.

For an ad-level issue, Google explains how to inspect the policy reason, correct the relevant ad or destination, and request review or appeal when appropriate. Track the response in Policy Manager and follow the current appeal instructions. Google disapproved-ad and appeal guidance

A useful internal incident record contains:

• Date and time observed
• Affected account, campaign, ad and public destination
• The policy label and the official case reference
• Recent changes that may be relevant
• What was checked or corrected, with evidence
• The owner, next action and current platform response

Keep the record factual. If the cause is unknown, say so. Separate the time the team submitted a response from the time a platform made a decision, and avoid promising a recovery date the platform has not provided.

Do not respond to enforcement by opening replacement accounts or disguising the same restricted offer. Google prohibits attempts to circumvent its review and enforcement systems, including creating new accounts to re-enter after suspension. Use the applicable official resolution process. Google Circumventing systems policy

Keep the record current after launch

Treat the review file as part of change management. Before altering a service, destination, partner, target market, audience or measurement configuration, identify which earlier decisions need to be revisited.

LegitScript asks certified businesses to report significant changes, including relevant business, website, licensing and regulatory changes. Use its current instructions to determine the appropriate notification. LegitScript Healthcare Certification FAQ

An internal change record can stay short: proposed change, affected campaigns, review owners, decision, implementation date and any follow-up. Keep a link to the live policy source beside time-sensitive requirements, so an old checklist is less likely to become the team’s only reference.

Where managed advertising infrastructure can help

When evaluating a managed provider, ask for a written scope covering account ownership and access, billing responsibilities, campaign change controls, documentation and support-case ownership. These are practical operations questions. Request evidence for any claimed platform relationship or special support entitlement.

The provider should be able to explain who does what, which records the advertiser controls, how work is handed back and what happens when a case is unresolved. Clinical and legal decisions need the appropriate qualified owners. Platform certification and advertising decisions remain with the relevant reviewers.

Treat promises of guaranteed approvals, healthcare-review immunity or automatic enforcement failover as reasons to ask more questions. An operations service should be assessed on documented responsibilities and supported capabilities.

Discuss your operating requirements

Discuss whether managed advertising infrastructure fits your operation. Start with your public website, target market, advertising platform and a non-sensitive description of the operational problem. Confirm the available scope in writing. Do not send patient information, clinical intake records, passwords or access tokens.

Source check: October 3, 2026. Policies can change. Recheck the linked official requirements before applying, changing a campaign or relying on an earlier approval.