---
url: "https://dfylegitscript.com/blog/rebranding-or-migrating-a-certified-telehealth-domain"
title: "Rebranding a certified brand without breaking the listing"
description: "Certification attaches to a domain, so a rebrand, a domain migration or a corporate restructure changes the thing that was certified, and a brand that redirects its traffic before telling anyone ends up advertising a domain that appears in no LegitScript listing."
published: "2026-07-29T11:03:13+00:00"
modified: "2026-07-29T11:03:13+00:00"
---

# Rebranding a certified brand without breaking the listing

Certification attaches to a domain, so a rebrand, a domain migration or a corporate restructure changes the thing that was certified, and a brand that redirects its traffic before telling anyone ends up advertising a domain that appears in no LegitScript listing.

## Key takeaways

- Because the credential attaches to a domain, a rebrand changes the certified thing itself rather than the branding sitting on top of it.
- Disclose the move before the traffic follows it, because a brand advertising a domain that appears in no listing is the failure mode that arrives after the redirect.
- Content migrations resurrect corrected copy, since what gets moved is often an archived version rather than the audited one.
- The card statement descriptor and the merchant account carry the old brand until somebody changes them, and that mismatch arrives as disputes.

Rebrands happen. A better domain becomes available, an investor wants a cleaner
name, two brands merge, a category pivot makes the old name wrong. None of that
is a compliance event in itself.

It becomes one because certification attaches to a website. Change the website
and you have changed the certified thing, and every downstream check reads a
listing that still describes the old one.

## What actually breaks

The failure is not dramatic and it is not immediate, which is why it catches
competent teams.

You migrate. The old domain redirects, traffic follows, and everything looks
fine. Then an advertising platform reviews the account, checks the listing for
the domain in the ad, finds nothing, and stops serving. Then an acquirer's
periodic check flags a merchant whose certified domain no longer resolves to a
site. Then a partner's annual diligence asks a question nobody can answer
quickly.

Each of those arrives weeks apart and gets attributed to something else, which
is the same pattern as
[the constraints that accumulate without certification](/blog/what-happens-to-a-telehealth-clinic-without-certification).

## Sequence it in this order

**Decide what the new estate actually is** before anything is bought. One
domain, or one per market, or a brand domain plus a shop. Every domain that
takes intake or transacts is its own application and its own annual renewal, so
this is
[a cost decision](/legitscript-certification-cost) made at the whiteboard stage.

**Tell the certifier before the migration, not after.** A change to the domain
being certified is a disclosure, and disclosing it in advance turns a surprise
into an administrative step.

**Keep the old domain resolving.** A redirect preserves the crawl path and, more
importantly, keeps the certified address answering rather than disappearing.
Retiring it entirely is a decision to make later, deliberately.

**Move the content, then move the traffic.** The new domain should carry the
substantive pages, in their compliant form, before anything points at it. A
migration is the most common moment for old copy to reappear, because a page is
recreated from a design file rather than migrated from the live version.

**Update everything that names the old brand.** The listing, the ad accounts,
the merchant descriptor, the affiliate creative, the pharmacy agreement, the
privacy documents and the packaging.

## The descriptor and the merchant account

Easy to forget and expensive to forget. Your card descriptor names the brand
customers bought from. Rebrand the front end without updating it and every
statement now shows a name the customer has never seen, which produces exactly
the disputes
[the subscription mechanics article](/blog/subscription-billing-and-cancellation-under-review)
is about.

The reverse is also true. Change the descriptor before customers know the brand
has changed, and you get the same result. Communicate the change to existing
subscribers before it appears on a statement.

## Corporate restructures are the quieter version

A new holding company, a change of operating entity, a professional corporation
reorganised, an acquisition. The website may not change at all, and the
certified merchant still has.

Ownership, principals and the operating entity are part of what was assessed.
Where they change, the file changes, and a structure that cannot be explained
plainly is a bigger problem than a structure that is merely complicated, as
[non-US operations and cross-border shipping](/blog/non-us-telehealth-operations-and-legitscript-certification)
sets out for the multi-entity case.

## The content migration is where old copy comes back

Worth its own warning, because it is the most common way a brand that fixed its
claims ends up publishing them again.

Migrations are rarely a straight copy. Pages get rebuilt in a new design system,
which means somebody works from a layout file, a content brief or a competitor's
page rather than from the live version that was corrected during the last
review. The corrected sentence was a compliance edit made months ago in a
content management system, and it is invisible in the design file.

Three habits prevent it. Export the live copy as text before the redesign starts
and treat that export as the source. Read every new page against the claims
allowlist before launch rather than after, as a launch gate rather than a
follow-up task. And check the pages nobody thinks of as pages: the checkout
copy, the confirmation email templates, the error states and the legal
documents, all of which get rewritten during a migration by whoever is nearest.

## What to do with the pages that do not survive

A rebrand usually retires pages, and retiring a page that a certification file
referenced, or that another site links to, has consequences beyond traffic.

Redirect rather than delete, to the closest equivalent rather than to the home
page, and keep a record of what moved where. Partners, affiliates and
counterparties hold links you do not control, and a link from a diligence
questionnaire that lands on a generic page reads as a business that has changed
in a way it has not explained.

## Merging two brands, both certified

The specific case worth naming, because the instinct is to consolidate quickly.

Two certified domains merging into one leaves questions: which listing survives,
what happens to the retiring domain, whether the surviving site now carries
product categories the other application covered, and whether the clinical model
and pharmacy relationships behind them were the same.

Answer those before the migration rather than during it. A merged site
describing a catalogue that no single application covered is a change to the
certified business, not a redesign.

## A migration checklist worth keeping

- The new domain estate, with a decision recorded against every domain.
- The disclosure to the certifier, dated, before the traffic moves.
- The content moved rather than recreated, and read against the allowlist.
- Redirects in place and the old domain still resolving.
- Advertising accounts, listings and descriptors updated in the same week.
- Partner, pharmacy and affiliate documentation updated.
- Packaging and post-purchase material scheduled, since printed stock lags.

## The underlying rule

A rebrand changes what the certification points at, and the listing is live
state that every counterparty reads. Businesses that treat the migration as a
marketing project with a compliance step attached discover the sequence in the
wrong order. Businesses that treat the listing as part of the launch plan
publish on a Tuesday and nothing downstream notices.

## Frequently asked questions

### Do I need a new application if I change domain?

Certification attaches to a website, so a new domain that takes intake or transacts is a new certified thing rather than a rename of the old one. Disclose the change before the migration rather than after, and keep the old domain resolving in the meantime.

### Can I just redirect the old domain and carry on?

A redirect keeps traffic flowing and does nothing about the listing that downstream checks read. Advertising reviews look for the advertised domain in the listing, so a redirect on its own produces a rejection nobody can explain.

### Does a change of corporate entity matter if the website stays the same?

Yes. Ownership, principals and the operating entity form part of what was assessed, so a restructure changes the file even when the site does not change at all. Explain the new structure plainly rather than leaving it to be reconstructed from filings.

## 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.