Treat a rebrand as a listing-maintenance project, not a one-time announcement. Start with every known directory profile, update public brand evidence first where a directory requires it, then record what changed and independently check the live result. A submitted edit is not the same as a verified public update.
Create one approved source record
Before opening a directory portal, create one approved rebrand record. Include the exact product name, canonical website URL, approved description and positioning, current pricing wording, logo, screenshots, support email, and the date each item became public. This gives every directory the same source material.
Keep both the former and new product name in that record. A publisher may need the previous name to locate the existing profile. For name changes, publish the new name on your own public website before making a request where the directory requires public evidence. Gartner Peer Insights requires supporting public documentation and says the proposed name must already appear on public sites before approval.
- Use one canonical destination URL for each update.
- Label screenshots with a version or capture date.
- Keep approved pricing language separate from internal pricing notes.
The approved rebrand record is ready, but no directory action has occurred.
An edit was sent through a portal or to publisher support.
A reviewer viewed the public profile and recorded the observed fields and time.
Audit every existing directory profile
Build the audit from known submission records, previous launch work, and team inboxes. For each directory, capture the public profile URL, visible name, destination URL, account owner or access route, and the fields that require change. A public listing and account access are separate conditions, so do not assume that a missing login means the profile no longer exists.
Use one row per directory, not one row per individual edit. That lets you see whether a rename is complete while pricing, screenshots, or a website URL still need attention. It also reduces the risk of creating a second listing when the existing one should be amended.
Backdrip shows submission history, status visibility, and saved listing credentials when available. Use these records to seed the audit, then inspect the public profile yourself. Whether a listing can be edited depends on the individual directory.
- Record the directory name and exact public profile URL.
- Capture the current name, URL, description, logo, pricing, and screenshots.
- Note access as credential available, managed email link, or publisher contact required.
- Log the requested change, owner, ticket or request reference, and last observation date.
| Field | What to record | Completion evidence |
|---|---|---|
| Directory and profile URL | Exact public listing page | Page opened and URL recorded |
| Change requested | Name, URL, logo, pricing, copy, or screenshots | Portal confirmation or support reference |
| Publication state | Prepared, submitted, or live update verified | Dated portal or public-page observation |
| Live checks | Visible name and destination-link correctness | Public profile viewed and link tested |
| Next review | Risk-based recheck date and owner | Future date recorded |
Choose direct editing or publisher support
Use a direct portal edit when you control the authorized account and the needed field is available. Complete the portal’s publication step rather than assuming that saving an edit makes it public. Software Finder instructs vendors to click Publish Changes after updating a logo or product name.
Contact the publisher when the change is a formal rename, the relevant field is unavailable, access cannot be recovered, or the directory requires review. Do not submit a duplicate profile simply to show the new brand. G2 tells companies that rebrand an existing profile to contact support rather than create another listing.
Some directories restrict who can make a rename request. Gartner Peer Insights says only Vendor Portal administrators can request a product-name change, using the current and proposed names, a description, and public supporting documentation. G2 also requires profile names to match the actual product name without marketing language or symbols.
- For a direct edit, save the confirmation and note whether a separate publish action was completed.
- For a publisher request, provide the old name, new name, listing URL, public evidence, and exact fields to update.
- For an access issue, use the directory’s recovery or support route and retain its reference.
- Ask the publisher to amend or merge an existing profile instead of creating a duplicate.
| Situation | Recommended route | Documented example |
|---|---|---|
| You can edit the required field | Use the authorized portal and complete its publishing step | Software Finder separates edits from Publish Changes |
| An existing profile has rebranded | Contact publisher support instead of creating another profile | G2 gives this instruction |
| A formal product-name change is needed | Have a portal administrator submit the required evidence | Gartner Peer Insights describes this process |
Verify the public profile after the update
After an update is processed, open the public listing in a separate browser session. Check the visible name, logo, description, pricing wording, screenshots, and destination link against your approved rebrand record. Record the observation time and the fields you actually saw. Only then mark the listing as live update verified.
Keep separate observations for public availability, destination-link correctness, indexability, and confirmed search indexing. A page loading proves public availability. Clicking the outbound link tests whether it reaches the intended current URL. Neither observation proves that the listing is indexed or that every requested field has changed.
Publisher timing remains outside your control. Backdrip notes that directory approvals can take days or weeks and that some submissions are not accepted. Keep an item at update submitted until you observe the public result or receive a definitive publisher response.
- Open and record the public listing URL.
- Click the destination link and confirm it reaches the intended current site.
- Compare all visible fields with the approved rebrand record.
- Save the reviewer, observation date, evidence URL, and any mismatch.
Match the visible profile against the approved rebrand record.
Open the destination link and confirm it reaches the intended current URL.
Log the observed fields, evidence URL, status, and observation time.
Review after known changes and on a risk-based schedule.
Maintain the change log and find silent changes
The change log is the operational record of your rebrand. Record when a request was sent, who sent it, the portal confirmation or support reference, the publisher response, the public-page observation, and the next review date. Preserve old observations instead of overwriting them so your team can see when a mismatch appeared and when it was resolved.
Recheck listings after known events such as a publisher approval email, a pricing-page revision, or a product release. Also schedule independent periodic checks for important profiles. Those checks can uncover silent external changes, such as a reverted URL or old screenshot, even when no one sends a notification. Choose a cadence based on each listing’s importance and the capacity your team can sustain.
Backdrip can centralize starting records through submission tracking and saved credentials where available. Its plan includes one vetted backlink submission per day, submission tracking with saved logins, Google rankings and traffic tracking, and Vercel live-traffic tracking. Use any available listing access to reach the appropriate portal, while retaining publisher-specific requirements and public verification in your own workflow.
- Assign one owner to every unresolved publisher request.
- Recheck higher-priority listings more often than lower-impact profiles.
- Record the observation time with each live-page check.
- Reuse the approved source record whenever positioning, pricing, or visual assets change again.
Make rebrand maintenance repeatable
A reliable rebrand update follows a controlled sequence: publish approved brand evidence, audit known listings, select the appropriate update route, verify the public profile, and keep a dated record. This prevents duplicate listings and gives the team a clear next action while publisher review is pending.
For future listing work, keep the same audit structure from the start. The SaaS directory submission checklist helps standardize recurring product details and assets. If you also need to inspect a published directory link, see checking whether a backlink is dofollow, while keeping link attributes separate from listing accuracy.
