A 75-location HVAC group imports its Google listings into Bing Places on Friday. On Monday, operations finds a former branch, two crossed phone routes, and one acquired company still using its old website.
The import worked. The rollout did not.
Microsoft relaunched Bing Places for Business in October 2025 at bing.com/forbusiness. The company says the new experience includes an improved Google import, bulk editing, real-time status updates, and a Recommendation Tool. Those changes make portfolio work easier, but they do not turn another platform's data into verified branch truth.
For a multi-location service brand, Bing Places belongs in the same operating system as Google Business Profile, Apple Business, location pages, call routing, and the citation cleanup queue. If leadership cannot see which public sources disagree with the approved branch record, check the brand's location-level visibility before expanding the import. Start with a controlled pilot, approve the location facts, inspect warnings and duplicates, and read the result back in Bing Search and Bing Maps.
Important
Microsoft described deeper Bing Maps and Copilot integrations as future investment in its 2025 relaunch announcement. Do not promise that a listing controls Copilot recommendations. Manage Bing Places for accurate Bing Search and Maps facts, then measure AI answers separately.
Know what the new Bing Places can do
Microsoft's relaunch announcement says existing listings were automatically migrated into the new experience. It also describes faster Google import, bulk editing tools, a centralized dashboard, and real-time status updates.
The current Bing for Business page says operators can add multiple locations through bulk upload. It also lists photos, hours, services, and contact methods among the information a business can manage. Microsoft Support directs owners to Bing Places when they need to add or change a business listing that appears in Bing Maps.
That is the documented scope: a business-listing management surface for Bing Search and Maps. It is useful even if an AI recommendation never changes. Customers get a better chance of reaching the right branch, local teams inherit fewer routing errors, and the central office has another public source it can verify.
The portal does not replace a location database. It also does not resolve whether a franchise, acquisition, service-area business, or closed branch should exist. Those are operating decisions the brand has to settle before import.
Freeze one canonical record per location
Do not start with every listing Google happens to contain. Start with the branches the company is prepared to operate publicly.
Create one approved record for each location, tied to an internal store code that will survive a rebrand or platform change. At minimum, capture:
- Identity: operating status, approved public name, parent brand, legitimate former name, and the person accountable for the branch
- Customer route: current address or service-area configuration, working phone path, dedicated location URL, regular hours, and temporary exceptions
- Service truth: services actually sold in that market, business type, customer-facing categories, and any eligibility constraint that changes how the address should appear
- Publishing control: current Bing state, verification owner, duplicate or suppression note, last edit, last public readback, and the next review date
An HVAC rollup should not import a warehouse just because the location exists in a spreadsheet. A med-spa group should not attach a shared call-center number if it cannot route the caller to the selected clinic. A restoration platform should not keep an acquired company's old domain after the customer journey has moved.
This is the same identity problem covered in How to Fix Conflicting Records Across 50 Locations. The canonical record lets the team distinguish a harmless formatting difference from a former address, disconnected number, duplicate branch, or wrong market.
Pilot the Google import before the portfolio
Choose five to ten locations that represent the hard cases in the portfolio. Include a normal storefront, a service-area branch, an acquisition or rebrand, a location with a recent move, and one market with a known duplicate. The sample should expose the process, not flatter it.
Use the new Google import only for the approved pilot locations. Record which account supplied the data, which locations were selected, when the import ran, and which fields Bing accepted or flagged. Do not assume the portal copied every Google field or preserved the intended branch relationship.
Then compare every imported listing with the canonical record. The useful questions are concrete. Did the phone reach the promised team? Did the URL land on the right location page? Were normal and holiday hours still current? Did a former brand or former address reappear? Was a location that should hide its address published differently?
Microsoft says some business types may hide their address, but a valid address is still required in the management flow. Do not copy Google eligibility assumptions into Bing without checking the current portal behavior for the actual business type.
Pro Tip
Import is a transfer mechanism, not an approval. A branch is complete only after the team verifies the managed record and the public customer experience.
Resolve warnings, duplicates, and lifecycle exceptions
Real portfolios rarely arrive clean. Acquisitions create former names. Moves leave old addresses. Franchise transfers divide access. Closures remain visible after the phone and location page disappear.
Give each exception one owner and one resolution state. A suspected duplicate should show both public URLs, the canonical branch it may represent, and the action requested. A moved branch should preserve the continuing identity while the old address is removed from customer routes. A closed branch should move through a documented closure process rather than vanish from the central record.
For a 120-location plumbing platform, this prevents corporate marketing from editing the current branch while a regional manager tries to reclaim the former listing. The work may happen in Bing Places, but the decision belongs in the shared operating ledger.
Use the closed-location cleanup workflow for branches that no longer serve customers. For acquisitions and moved locations, preserve the internal store code, public transition notes, and approved destination so the wrong record does not return during the next import.
Read the listing back like a customer
A green status inside a management portal is not the public result.
After Bing accepts or verifies a pilot listing, search the brand and service in the location it serves. Open the Bing Maps result. Check the displayed name, address or service-area treatment, phone, hours, website, services, and photos. Follow the phone and website routes instead of stopping at the listing card.
Microsoft explains that Bing can use location information to provide local search results. That makes the test location material. A result observed from headquarters may not represent what a customer sees near the branch.
Run the same readback on mobile and desktop when the customer path differs. Call the number during both staffed and after-hours windows. Test any redirected location URL. Save the public URL, observed result, market, device, and timestamp in the branch record.
For a med-spa group, the decisive failure may be a phone route that sends a prospective patient to the wrong clinic. For a garage-door franchise, it may be a regional landing page that cannot confirm the customer's ZIP code. Those failures are more important than whether two platforms abbreviate the street in the same way.
Put Bing Places inside normal change control
The portfolio will drift again unless Bing has an owner after launch. Location operations should trigger updates for openings, moves, closures, rebrands, phone changes, holiday hours, service changes, and agency transitions. The listings team should publish only the approved facts and record the public readback.
Set the cadence by operational risk. A fast-growing rollup may review change events weekly and sample stable locations monthly. A mature franchise may use a monthly exception queue and a quarterly portfolio audit. Microsoft does not prescribe those cadences; they are operating controls.
The platform owner also needs durable access. Avoid making a departing employee or agency the only person who understands the portfolio. Record the Microsoft account or approved access path, backup owner, import source, verification dependencies, and escalation history.
Keep Google, Apple, Bing, and owned location pages in one change manifest, but verify them independently. The Apple Business guide for multi-location brands uses the same principle: shared brand control does not remove the need to validate each physical location and customer handoff.
Use a 30-day rollout with explicit gates
The following sequence is a Cheers operating recommendation, not a Microsoft processing timeline:
- Days 1 through 5: approve the canonical location inventory, choose the pilot, confirm access, preserve before-state URLs, and record lifecycle exceptions
- Days 6 through 12: import only the pilot, compare every field, resolve warnings and duplicates, and verify the phone and website destinations
- Days 13 through 20: read the pilot publicly in Bing Search and Maps, document failures, fix the process, then approve the remaining location groups
- Days 21 through 30: roll out in controlled batches, verify each batch, assign recurring ownership, and schedule the first exception audit
The rollout is complete when leadership can answer six questions for every branch: should it exist, who owns it, which source supplied it, what exceptions remain, what a customer sees now, and when it will be checked again.
Sources
- Microsoft Bing Blog: Introducing the New Bing Places for Business. Supports the October 2025 relaunch, migration, improved Google import, bulk editing, status updates, Recommendation Tool, and Microsoft's future-integration wording.
- Microsoft Bing for Business. Supports the current management surface, multiple-location bulk upload, and the types of business information operators can manage.
- Microsoft Support: Add and manage your business listing. Directs businesses to Bing Places to add or change listings that appear in Bing Maps.
- Microsoft Support: How Bing uses your location. Supports location-aware local search behavior and the need to record the market used for public readback.
Amadeus Peterson is the CTO & Co-Founder of Cheers, the local search platform for multi-location service businesses.