To update SaaS directory listings after a rebrand, first collect the public pages that still show the old identity. Prepare the exact replacement name, description and product link; then edit each page where your account permits it or send the publisher a specific correction request. Mark a listing complete only after you open its public page and follow its product link to the intended destination. A saved submission record helps you find a page, but it does not give you control over the publisher’s listing.
Find affected listings and prepare one replacement profile
Start with your submission records, then search for the old product name and domain to catch pages created by someone else or missed by your records. For submissions made through Ranks, its submission history shows where the product was submitted and which listings are awaiting approval or live; saved listing logins are accessible when available. Use those records as leads, then open each public listing to see what visitors actually see. A submission without a public page is not an existing listing you can correct yet.
Create a worksheet with one row per public listing URL. Record the publisher, old displayed name, old description, current product link, proposed name and description, replacement product link, intended destination, access owner and correction route. Capture the page as it appears now so a teammate or publisher can identify the mismatched fields. Keep your approved replacement copy in one place, but adapt its length or formatting to the fields each publisher actually offers.
- Name: write the exact new product name, including capitalization, rather than asking for a general “rebrand update.”
- Description: provide paste-ready replacement copy that describes the product as it works now; identify any old-name references that must be removed.
- Link and destination: distinguish the URL you want displayed or linked from the page a visitor should reach after following it. Prepare that destination before requesting a link change.
Edit the listing if you can; otherwise request a correction
For each page, check whether your authorized account exposes controls for the fields that need changing. If it does, enter the approved details and save them. If the account cannot edit the page or a required field is missing, find the publisher’s claim, access or change-request route. Do not create a second listing just because the existing one is hard to edit: that can leave visitors with two conflicting product identities.
Product Hunt shows why access and field availability are separate questions. Its claim guidance says an owner or member can edit Page content, but editing does not cover every field; for a field absent from settings, it directs users to “request changes to this page.” To claim a Page, it asks for a company email matching the product domain, with additional information available when that is not possible; a nonmatching-domain request goes to moderation. After a domain change, check which email and ownership route applies rather than assuming an old login can edit everything.
Here is a fictional worked decision: Acme Tasks becomes Acme Flow, and its intended product destination changes from https://old.example to https://new.example. Directory A’s fictional public listing URL is https://directory-a.example/listings/acme-tasks; Directory B’s is https://directory-b.example/listings/acme-tasks. Both pages show the name “Acme Tasks,” the description “Acme Tasks helps teams organize tasks,” and the product link https://old.example. The requested replacements are the name “Acme Flow,” the description “Acme Flow helps teams organize tasks,” and the product link https://new.example, which is also the intended destination. Directory A’s authorized account exposes editable fields for all three, so the owner enters those replacements, saves and then checks the public page. Directory B’s owner has no usable edit control, so they send its publisher the Directory B listing URL, those exact current and replacement values, the intended destination and a contact address. Directory B remains unresolved until its public page and link are checked—not merely until the request is sent.
A concise request is easier to act on than “please update our listing.” Use a subject such as “Correction request: Acme Tasks → Acme Flow,” identify the public listing URL, and list each current value beside its requested replacement. Explain that the product was renamed and state who can answer ownership questions. If the publisher requires a claim or verification first, complete that route rather than treating an email request as an approved edit.
Verify the public page and the link’s destination
After saving an edit or receiving a publisher response, open the public listing as a visitor. Read the displayed product name and description, inspect the product link, click it, and confirm that its final destination is the intended live page. In the fictional example, the owner’s public check of Directory A finds the name “Acme Flow,” the description “Acme Flow helps teams organize tasks,” and the product link https://new.example; clicking it reaches https://new.example. The owner marks Directory A verified. Directory B remains unresolved because its public page and link have not been checked after the request. An updated name beside a link to the old site is a partial correction. If a publisher leaves the old domain as the linked URL, record that separately even if the visitor eventually reaches the new site.
Do this check for each affected listing rather than relying on an account preview or a publisher’s confirmation. If one field is still wrong, send a focused follow-up naming that field and the public URL. This work concerns third-party product pages; if your rebrand also moves article URLs on your own site, use the separate SaaS blog URL migration guide for that task.
Hand off listings that are still unresolved
Keep a correction record for every page that has not passed the public check. Include the listing URL, incorrect and requested values, access owner, date edited or requested, publisher response, last public check, next follow-up owner and next action. Use clear outcomes such as “awaiting access,” “request sent,” “partially corrected” and “verified on public page.” That lets someone taking over distinguish a publisher delay from an edit that was never submitted.
Prioritize follow-up on pages visitors are likely to use or those still pointing to the wrong destination, while keeping publisher-dependent requests open until you can verify them. If you also need a broader system for submission dates and approval outcomes, use the directory submission-tracking guide; the rebrand record here is specifically about whether existing public details were corrected.
