---
url: "https://dfylegitscript.com/blog/google-ads-healthcare-certification-for-telehealth"
title: "Google Ads healthcare certification is a second application, not a consequence of the first"
description: "Google Ads Healthcare Certification is filed per advertising account and references your public LegitScript listing, which means holding certification does not switch your ads on and telehealth advertisers routinely lose weeks discovering that in the wrong order."
published: "2025-11-01T13:23:45+00:00"
modified: "2025-12-29T13:10:56+00:00"
---

# Google Ads healthcare certification is a second application, not a consequence of the first

Google Ads Healthcare Certification is filed per advertising account and references your public LegitScript listing, which means holding certification does not switch your ads on and telehealth advertisers routinely lose weeks discovering that in the wrong order.

## Key takeaways

- Platform healthcare certification is a second application filed per advertising account, so holding the credential does not switch anybody's ads on.
- The domain your ads point at has to be the domain that appears in the listing, and that mismatch causes more platform rejections than anything else.
- Platform advertising policy is stricter than the certification standard, so a page that survived review can still be the reason an account will not serve.
- Plan the domain estate before the campaigns, because a funnel domain built for a quick test becomes an advertised domain nobody certified.

This is the single most common sequencing error in telehealth marketing. The
certification comes through, the team assumes the ad account is now unblocked,
and the campaigns still do not serve. Nothing has gone wrong. There was always a
second application.

## Two credentials, two reviewers, two timelines

The first credential certifies your website. It is issued by LegitScript, it
attaches to a domain, and it appears in a public listing.

The second is Google Ads Healthcare Certification. It is a Google process, it is
filed at the advertising account level, and it references your public
certification listing as evidence. Google reviews it on its own timetable and
applies its own policies, which are broader than the certification standard and
which change.

Neither one produces the other. A certified website with no platform approval
cannot advertise. A platform approval cannot be obtained without the underlying
certification for the relevant categories.

## The mismatches that cause rejections

Almost every platform rejection after a successful certification traces to one
of four mismatches, and all four are avoidable if you know to look.

**The advertised domain is not the certified domain.** Your ads point at a
funnel domain, your certification covers your clinical domain. The reviewer
checks the listing for the domain in the ad, finds nothing, and declines. This
is the big one.

**The account structure does not match the certification.** Certification is
filed per account, and agencies running client campaigns from a manager account
frequently apply at the wrong level. Get this straight before you file rather
than after.

**The entity names do not match.** The business name on the ad account, the legal
entity in the certification, and the entity on the website should be the same
name spelled the same way. Where they legitimately differ, expect to explain it.

**The landing page says something the ad policy prohibits.** Platform policy is
not the certification standard. It is stricter in places, particularly around
prescription medicines, before-and-after imagery and implied outcomes, and it is
enforced by a different reviewer reading the same page.

## Plan the domains before you plan the campaigns

The practical consequence of all this is that your advertising architecture is
a certification decision, and it is made much earlier than most teams make it.

If you intend to run paid traffic to a dedicated landing domain, that domain
needs its own certification. If you intend to test three offers on three
domains, that is three certifications and three annual renewals, and it is worth
asking whether the same tests can run as paths on one certified domain instead.

Consolidating funnels onto a certified domain before you apply is usually the
cheaper answer, and it is a decision that becomes expensive once the
applications are already filed.

## What survives a policy change

Platform policy in the medicines categories moves. It moved for compounded
products, it moves for weight management periodically, and it will move again.
Some of that is outside your control.

What is inside your control is how much of your account depends on the
interpretation being generous. Accounts built on defensible claims, accurate
provider disclosure and an honest description of what the product is survive
policy tightening. Accounts built on comparisons to brand-name drugs and implied
outcomes are the ones that stop serving overnight.

Our
[index of FDA warning letters](/research/glp-1-compounding-warning-letters) over
compounded GLP-1 marketing is a useful proxy for where the enforcement attention
sits: it counts the letters and codes each one by the violation it cites, and
misbranding and comparisons to the brand-name product are what the series turns
on. Ad platforms read the same landscape and tighten accordingly.

## A working sequence

1. Decide the domain architecture, including every domain that will receive paid
   traffic.
2. Fix the claims and disclosures on those domains, to the standard the stricter
   of the two reviewers would apply.
3. File certification for each domain that needs it.
4. File the platform healthcare certification per advertising account, once the
   listing is live.
5. Build campaigns against the approved landing pages, and route new landing
   pages through the same claims review before they ship.

Step five is the one that lapses. The account gets approved, the marketing team
resumes shipping pages at speed, and six months later a landing page nobody
reviewed reintroduces exactly the claim that would have failed the original
review.

## Who owns this internally

Nominate somebody. The most common structural failure is that certification is
owned by operations or legal, advertising is owned by marketing, and no single
person is accountable for the fact that a landing page is a compliance artefact.

If you are weighing whether to run the whole thing in house, the ongoing
ownership matters more than the filing does, and that is covered in
[what a complete application file looks like](/blog/what-a-complete-legitscript-application-file-looks-like).

## What to check before you file the platform application

Half an hour here saves a rejection cycle.

- The exact domain in your ads appears in your public certification listing, and
  the listing is live rather than pending.
- The advertising account you are applying from is the one that will actually
  run the campaigns, at the right level in the manager structure.
- The business name on the ad account, the legal entity in the certification and
  the entity named on the website are the same name, spelled the same way.
- The landing pages the campaigns point at have been read against platform
  policy rather than only against the certification standard, because the
  platform is stricter in places.
- The destination pages load without a consent wall or a geographic redirect
  that a reviewer in another location will hit instead of your page.

That last one causes rejections nobody can explain, because the reviewer never
saw the page you meant them to see.

## If the application is declined

Read the stated reason literally rather than interpreting it. Platform decline
notices are terse but they are usually accurate about which policy was applied,
and the common causes are the mismatches above rather than anything subtle.

Fix the mismatch, then reapply rather than appealing, unless the notice
explicitly invites an appeal. And resist the temptation to soften the landing
page just enough to pass while leaving the underlying claim intact somewhere
else on the site, because the next policy sweep reads the whole domain rather
than the page you edited.

## Frequently asked questions

### Does certification automatically enable Google Ads?

No. Google Ads Healthcare Certification is a separate application filed at the advertising account level. It references your public certification listing as evidence, and Google reviews it against its own policies on its own timetable.

### My ads point at a landing domain, not my main site. Which one needs certifying?

The domain in the ad. The platform reviewer checks the listing for the advertised domain, so certifying the clinical site while advertising a separate funnel domain is the most common cause of rejection after a successful certification.

### Can my agency file the platform certification for me?

Yes, and it is usually filed from the account that runs the campaigns. Confirm the account level before filing, because applying at the wrong level in a manager account structure is a common and time-consuming error.

## Disclaimer

LegitScript is a trademark of LegitScript LLC. VeriScripts is an independent application-preparation service. It is not affiliated with, endorsed by, or certified by LegitScript LLC, and claims no sponsorship or partnership with it. We prepare, submit, and manage the application; LegitScript alone decides whether certification is granted. "LegitScript" is used here only to name the certification these applications are for.