How to Update a Microsoft Merchant Center Store Safely

Your rebrand may be ready across your website, product feed, packaging, and campaigns, yet one unresolved Merchant Center setting can leave shoppers seeing the old identity. The good news is that you can now change store names and domains directly in Microsoft Advertising Merchant Center without opening a support ticket.

That removes the support handoff, but it does not make either change instantaneous. A store name goes through editorial review, while a new domain must be verified. Your safest plan is to keep the existing setup operational until the relevant check is complete, then finish the migration in a controlled second step.

Key takeaways

• You can edit a Merchant Center store name or domain within the Microsoft Advertising platform instead of submitting a support ticket.
• Ads continue to use the old store name while a replacement name is under editorial review.
• Ads continue to use the old domain while Microsoft verifies the replacement domain.
• After the new domain is approved, update the product URLs that still point to the old domain.
• A previously used store name or domain can be reused, but it must still satisfy the relevant editorial or verification requirements.

Know which Merchant Center setting you are changing

A store name change and a domain change may belong to the same rebrand, but Microsoft treats them as separate updates. They have different approval gates and different follow-up work. Distinguishing them before you start prevents a common planning error: assuming that changing one field completes the entire transition.

If you are changing both, manage them as two tracked work items. The store name can be ready for review while the website team is still preparing the new domain, or the domain can be technically ready before the public brand rollout. Do not mark the rebrand complete merely because one of the two changes has been submitted.

The distinction also matters when assigning responsibility. A brand or advertising owner can confirm the exact store name, but domain verification and product URL migration may require access from an ecommerce, development, or feed-management owner. Identify those owners before touching the settings.

Change the store name without promising an instant switch

Submitting a new store name starts an editorial review. During that review, your campaigns do not have to stop: ads continue serving with the old store name. This protects campaign continuity, but it also creates a transition period in which your website or other channels may show the new brand while Microsoft ads still show the old one.

Plan for that temporary mismatch instead of trying to force every public surface to change at the same moment. Microsoft has not attached an approval duration to the documented workflow, so treat editorial approval as an external dependency rather than a minute-perfect launch step.

1. Confirm the final spelling, capitalization, spacing, and punctuation of the new store name with the people responsible for the rebrand.
2. Check that the proposed name accurately represents the storefront shoppers will reach. A convenient internal label is not necessarily the right customer-facing store name.
3. Submit the new name through Merchant Center.
4. Expect the old name to remain on ads during editorial review. Tell campaign and customer-support teams that this is a pending state, not evidence that the submission failed.
5. Wait for approval before declaring the advertising portion of the rename complete.
6. After approval, inspect live customer-facing placements and confirm that the new name is rendered as intended.

Do not repeatedly resubmit the name simply because the old one remains visible during review. The documented behavior is to keep serving the existing name until the replacement passes the check. A submission and an approved public change are two different milestones.

If you need to return to a former store name, Microsoft permits reuse as long as the name passes editorial checks. Treat that reuse as another controlled review event, not as an automatic restoration of a previously accepted value.

Move to a new domain in the correct order

A domain change carries more operational risk than a name edit because product ads must lead shoppers to working landing pages. Microsoft requires verification of the replacement domain, and ads continue serving on the old domain while that verification is underway. The old site therefore remains part of the live advertising path until the new domain is approved.

Do not disable the old domain merely because the new site is available. If ads are still being served against the old domain, taking it offline can send paid visitors to broken or unavailable pages. Keep the existing storefront and its product destinations functional throughout the pending period.

1. Finish the new storefront before requesting the switch. Test representative product pages, navigation, cart behavior, checkout, policies, and mobile rendering on the new hostname.
2. Keep the old domain active and keep its current product URLs working.
3. Enter the replacement domain in Merchant Center and complete the required domain verification.
4. While verification is pending, monitor the old-domain landing pages that current ads still use. Do not assume that requesting the new domain has already moved ad traffic.
5. Wait until the new domain has been approved.
6. After approval, update product URLs so they point to the corresponding pages on the new domain.
7. Test a representative set of ads and products after the URL update. Confirm that the landing pages load, the products match the ads, checkout works, and measurement parameters have not been lost.

Domain approval is a gate, not the final migration step. Your catalog can still contain old-domain product links after the replacement domain is verified, which is why the product URL update needs its own owner and completion check.

Redirects can protect shoppers who encounter an old link, but they should be a safety net rather than the operating plan. Update the product URLs themselves after approval. Also review any feed rules, tracking templates, campaign parameters, canonical URLs, and analytics settings that contain the old hostname. Those systems sit outside the Merchant Center domain field and may not change merely because the new domain was accepted.

A former domain can be reused if it passes verification. That flexibility can help when reversing a migration or reorganizing stores, but previous use does not remove the need to prove control of the domain again when Microsoft requires the check.

Use a preflight checklist before submitting either update

The editable settings make the administrative step easier. They do not coordinate your brand, website, catalog, analytics, and campaign teams for you. A short preflight prevents the platform change from getting ahead of the assets it depends on.

• Final value confirmed: Record the exact store name or domain that should replace the current value. Have the accountable brand or website owner approve it before submission.
• Current setup recorded: Save the existing store name, domain, and a sample of current product URLs so you can diagnose a mismatch during the transition.
• Old destination protected: Keep the old domain and its landing pages available while the new domain is being verified.
• Verification owner available: Make sure the person who can complete domain verification is ready when the change is submitted.
• Product URL work prepared: Prepare the new product URLs in advance, but schedule their deployment for after the domain has been approved.
• Dependent systems checked: Search feed rules, redirects, tracking templates, analytics configuration, and other campaign settings for the old hostname.
• Pending-state expectations shared: Tell stakeholders that the old name or domain can remain in active ads while the replacement is being checked.
• Post-approval test assigned: Name the person who will verify live ads, landing pages, checkout, and measurement after the switch.

For a store-name-only change, your operating pattern is simple: submit, allow the old name to remain during review, and confirm the replacement after approval. For a domain migration, use a two-stage deployment: verify the new domain while the old one stays live, then update and test product URLs after approval. Build your launch plan around those confirmed states, and the new self-service controls can save administrative effort without turning the rebrand into an avoidable campaign outage.

References

• Search Engine Land — Microsoft lets merchants update store names and domains in Merchant Center