Store search does not return app 9PL7ZJ6HBW9S for its new name "Visdap" (stale search index after rename)

This is now a Store search-indexing issue for Microsoft to investigate; submit a Dev Center support case requesting reindexing of product 9PL7ZJ6HBW9S, rather than changing or republishing the listing again.

Open the support case through an alternate route

Because the Engage Center link in Partner Center does not load:

1. Sign in to Partner Center with the account associated with the app.
2. Select the AI assistant icon in the upper-right.
3. Describe the search-index mismatch.
4. Select Contact Support → choose the Windows Apps/Store workspace and the closest publishing or discoverability problem type.
5. Select Review solutions → Create support request → submit.

If AI assistant is unavailable, use Help (?) → Contact Support and follow the same workflow. This is the documented Partner Center support process.^1^

If the Partner Center support interface itself remains inaccessible, use the account-specific Dev Center support route listed for Store publishers:

• Entra ID/work account: use the Entra ID Engage Center link.
• Microsoft account (MSA): use the separate MSA Engage Center link.

Both are provided in the Windows developer support documentation.^2^

Include this evidence in the case

A concise request would be:

Subject: Microsoft Store search index still uses former app name — product 9PL7ZJ6HBW9S

Product ID: 9PL7ZJ6HBW9S
Previous name: Time for Life
Current name: Visdap: Visual Day Planner
Publication time: 2026-10-18 15:46 UTC

The current name is visible on the public product listing in all five published languages, but Store search still appears to use the previous listing metadata:

• “visdap” does not return the product.
• “visual day planner” does not return it in the top 20.
• “time for life” still returns it at position 1, although that phrase is absent from the current listing.
• Reproduced in US, DE, and UA markets through 2026-10-26.

Please investigate the Store search document associated with this product and reindex its current localized listing metadata.

Attach:

• Screenshots of each search result, including market/region and date.
• The public listing showing the new title.
• The Partner Center submission ID and publication status.
• The five affected listing languages.
• Confirmation that the renamed submission shows In the Store.
• A HAR file or browser console output only if Support requests it.

Support cases can subsequently be found under Help (?) → View my support requests.^3^

No further rename submission is indicated

The documented rename procedure is to reserve the new name, create a new submission, select it from Store listing → Product name for every applicable language, and publish it.^4^

Your public listing already displays the new name in all five languages, so the facts given indicate that this publisher-side rename flow has completed. Do not delete and recreate the product, and do not republish unchanged metadata merely as a speculative indexing fix.

Also, deleting the old reserved name is optional cleanup after publication; the documentation does not identify it as a search-reindexing operation.^4^

Client-side Store repairs such as wsreset, re-registering Microsoft Store, or changing Windows region are not applicable here: the old-name behavior has been reproduced across several markets and concerns the catalog’s search association, not one device’s Store client.

References

1. Get help and contact support in Partner Center
2. Help and guidance for Windows developers
3. Support for Microsoft Marketplace program in Partner Center
4. Manage app name reservations for MSIX app - Windows apps