“health export ai” Is Still the Term With the Backlinks: Running Two Brand Names Without Splitting the SERP
Renaming a product is easy. Renaming a product that already has search history is not. Every link, every post and every past mention still points at the old string, and the new string starts with nothing. This is what happened to us, and here is how we are running both names without splitting the results.
Quick answer
Keep both names alive and consolidate the entity rather than the string. The legacy term still holds the backlinks, the new name holds the queries, and one canonical domain carries both. On 2026-10-18, a brand query for “metricbridge apple health mcp server” returned four healthexport.dev URLs at positions one to four on Exa, and the older term “health export ai” still carries the inbound links. Pointing both at the same canonical pages is what stops the SERP from splitting into two weak halves.
What a rename actually breaks
Three things, and only the first is obvious:
- The string. Your old name is indexed; your new name is not. Queries for the new name return nothing until pages exist that use it.
- The links. Nobody rewrites a backlink. Every historical mention keeps your old name, so the old term accumulates authority you are not using.
- The entity. Search engines and answer engines resolve a brand as an entity, not a string. If the two names are never linked to each other on your own pages, they look like two weak entities instead of one strong one.
The evidence we are working from
Two datapoints from our own 2026-10-18 checks shaped this approach:
- A brand query for “metricbridge apple health mcp server” returned four healthexport.dev URLs at positions one to four. The new name plus a qualifier is already a brand echo: the results are our own pages, which is what you want.
- The older term “health export ai” still holds the inbound links, and an answer-engine probe quoted our repo and our config block verbatim. The citation is structural, coming from our own pages rather than a third-party mention.
So the old name is the link magnet and the new name is the query magnet. Killing either would throw away half the asset.
How to run two names without splitting the SERP
Five rules that we apply, and that any renamed product can copy:
- One canonical domain. Both names resolve to the same site, and one page is canonical per topic. Never publish the same post under two names.
- Mention both names on the key pages. A single sentence linking the old term to the new brand is what merges two weak entities into one strong one. Do it on the home page and on the main product page, not in a buried footer.
- Keep the old name in the places it already earns links. Blog slugs, developer docs and historical posts can keep the old term where it is doing work. Rewriting them resets the value for no gain.
- Use one organisation name in structured data. One publisher name in your Article and FAQ markup, matching the name on the site, is what an answer engine reads as the entity.
- Do not chase the old name in new copy. New posts lead with the new brand and its qualifier, because that is the query you are trying to own next.
What this is not
It is not link buying, and it is not spinning up pages to target every permutation of a name. Thin doorway pages for name variants are exactly what search guidelines punish, and they would split the entity further rather than merge it. Keep the pages real, keep the domain singular, and let the two names point at the same substance.
How we sourced this. Both SERP datapoints above are from our own checks on 2026-10-18 (brand query on Exa, and the answer-engine probe recorded in our weekly sweep). Search results and citation patterns move week to week, so we re-probe rather than treat a single check as settled.
The takeaway for anyone mid-rename
Do not delete the old name, and do not let it become a second brand. Let it be the term that keeps the links, put the new name on every new page, and write the one sentence that ties them together. That is the whole strategy, and it costs a paragraph, not a campaign.
If you are here because of the old name: this is the same product, now called MetricBridge. It exports 190 Apple Health metrics as local JSON and ships a zero-dependency stdio MCP server with 16 read-only tools that your agent can call.
{
"mcpServers": {
"health-export": {
"command": "node",
"args": ["/Users/you/.health-export-mcp/server.mjs"],
"env": {
"HEALTH_DATA_DIR": "/Users/you/Library/Mobile Documents/iCloud~ai~healthexport~app/Documents"
}
}
}
}FAQ
Did Health Export AI change its name?
Yes. The product is now called MetricBridge. The site stays at healthexport.dev, and the older name still appears where it already earns links, so existing readers and citations keep working.
Should I rename a product that already has backlinks?
Yes, if the new name matters, but do not delete the old one. Keep both alive, consolidate them under one canonical domain, and link the names to each other on your main pages so search engines treat them as one entity rather than two.
Does having two brand names split organic traffic?
It can, if you publish duplicate pages for each name. It does not if every page has one canonical URL and you mention both names on the key pages. The risk is duplicate pages and thin name-variant pages, not the second name itself.
How do I make search engines connect two brand names?
Use one publisher name in your structured data, keep a single canonical domain, and write at least one sentence that links the old term to the new name on your home page and product page. That tie is what merges the two into one entity.
Doing this yourself? MetricBridge handles the export step: all 190 metrics as local JSON, with the open-source MCP server (GitHub).
Same product, one purchase
MetricBridge is a $24.99 one-time unlock: 190 metrics as local JSON, the open-source MCP server with 16 read-only tools, and the on-device Ask and Weekly Brief.