how to update listings after a rebrand

Not specified by the original author.

TL;DR

Stale listings after a rebrand confuse searchers and split your brand across two names. The inventory is the hard part; the updates are mechanical. Applies to any tool with directory, marketplace, or registry listings.

The query

how to update listings after a rebrand

Use this when

• You renamed or rebranded the tool.
• Old-brand listings still exist across directories.
• You want consistent branding without breaking links.

Not for

• Only the logo changed (update the top listings, skip the full inventory).
• You are pre-launch with almost no listings (just update the few that exist).
• The old name still resolves and you are keeping it as an alias (update descriptions, not URLs).

Steps

1. Export your listing tracker and add any listings you find by searching the old name. Expected output: A complete inventory of every listing carrying the old brand.

2. Prioritize: top traffic drivers and registries first, long-tail directories second. Expected output: An ordered update queue, highest impact first.

3. Update name, logo, URL, and description on each; set up redirects from old URLs to new ones. Expected output: Consistent new branding across every listing, with old links still resolving.

4. Re-run the old-name search a month later to catch stragglers. Expected output: No public listing still showing the old brand.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_33KYLLXhcmO0Sf-cb0lIzg

Resolved from the public thread: https://vectle.com/posts/pst_33KYLLXhcmO0Sf-cb0lIzg

Thread query: how to update listings after a rebrand

TL;DR: Stale listings after a rebrand confuse searchers and split your brand across two names. The inventory is the hard part; the updates are mechanical. Applies to any tool with directory, marketplace, or registry listings.

Not specified by the original author.

TL;DR

Fix this in ZoomInfo by acting on the exact message first: update the domain mapping to the rebranded domain, merge the old domain record into the surviving account, and rematch intent signals against the new domain before assigning the lead. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

ZoomInfo intent enrichment matched a company on its old domain after a rebrand, wrong account

Use this when

• The operation in ZoomInfo fails with this exact message: ZoomInfo intent enrichment matched a company on its old domain after a rebrand, wrong account.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in ZoomInfo, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: update the domain mapping to the rebranded domain, merge the old domain record into the surviving account, and rematch intent signals against the new domain before assigning the lead. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in ZoomInfo so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in ZoomInfo on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The rebrand changed the public domain while enrichment keys still pointed at the old one, so signals landed on a shell record instead of the live account.

Variant phrasings

ZoomInfo intent enrichment matched a company on its old domain after a rebrand, wrong account

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in ZoomInfo

The how to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in ZoomInfo

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: ZoomInfo at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_8vYuJfCXgcUiTDEZZSIAgQ

Resolved from the public thread: https://vectle.com/posts/pst_8vYuJfCXgcUiTDEZZSIAgQ

Thread query: ZoomInfo intent enrichment error company match on old domain after rebrand wrong account

TL;DR: Fix this in ZoomInfo by acting on the exact message first: update the domain mapping to the rebranded domain, merge the old domain record into the surviving account, and rematch intent signals against the new domain before assigning the lead. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Help center search by acting on the exact symptom first: build the synonym pair in the help center search settings for old name to new name, add the reverse pair too, and verify with the three most common old name queries from the search log. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Old feature name search returns no results after rename

Use this when

• Work in Help center search shows this exact symptom: Old feature name search returns no results after rename.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help center search, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: build the synonym pair in the help center search settings for old name to new name, add the reverse pair too, and verify with the three most common old name queries from the search log. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help center search that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Old feature name search returns no results after rename

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - how to fix help center search synonyms missing users searching old feature name find nothing fails error

The how to phrasing for the same problem in Help center search. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help center search troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Search treats the old and new names as unrelated terms after a rename, so only an explicit synonym mapping reconnects reader language to current content.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help center search at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_b22G2a41iqXeqURA2GEuDw

Resolved from the public thread: https://vectle.com/posts/pst_b22G2a41iqXeqURA2GEuDw

Thread query: how to fix help center search synonyms missing users searching old feature name find nothing fails error

TL;DR: Fix this in Help center search by acting on the exact symptom first: build the synonym pair in the help center search settings for old name to new name, add the reverse pair too, and verify with the three most common old name queries from the search log. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.