A migration affects Bing the same way it affects Google, so the same discipline protects both: preserve your URLs, 301-redirect any that change, and let Bing recrawl the new site. Bing is a separate search engine with its own crawler, bingbot, its own index, and its own Bing Webmaster Tools, so it has to rediscover and reprocess your migration independently of Google, but the fundamentals are identical. The Bing-specific steps are to re-verify your site in Bing Webmaster Tools, submit your new sitemap there, and use Bing’s Site Move tool to signal the change, which is Bing’s equivalent of Google’s change-of-address process. Do that and your Bing rankings carry over as your Google ones do. Bing also feeds some AI search experiences, so its visibility is worth protecting deliberately. WPBuildAI preserves your URLs and maps every change to a verified 301, and the same redirect map and sitemap that satisfy Google satisfy Bing, so both engines keep your rankings.

Bing is separate, but the fundamentals are the same

The useful mental model is that Bing is another search engine reading the same web, with its own machinery. It runs its own crawler, keeps its own index, and offers its own Bing Webmaster Guidelines and tools, which means it discovers and reprocesses your migration on its own schedule, not Google’s. But it responds to the same underlying signals: it follows 301 redirects, it rewards preserved URLs, and it needs to recrawl to see the new site. So you do not learn a different playbook for Bing; you apply the same one and add a few Bing-specific tools. That is reassuring, because it means the work that protects your rankings in a migration protects them across engines, not just in Google.

One redirect map serves every engine

The core protection, your redirect map, is engine-agnostic. A 301 redirect is a standard signal that every major crawler honors to move a URL’s identity and value to a new address, as Google’s own guidance on redirects describes and Bing follows in kind. So you do not build a separate set of redirects for Bing; the same verified map that carries your pages for Google carries them for Bing. This is why URL preservation is the single highest-leverage task in any migration: it pays off in every search engine at once. The platform you move to is not itself a ranking factor in either engine, as the Backlinko analysis shows, so a faithful rebuild at preserved URLs holds rankings broadly.

The Bing-specific tools to use

What Bing adds are its own webmaster tools, and using them speeds and smooths the transition. Re-verify your site in Bing Webmaster Tools so you keep visibility into how Bing sees the new site, submit your new sitemap there so Bing discovers your URLs quickly, and use Bing’s Site Move tool to signal the change of address directly, which is Bing’s counterpart to Google’s change-of-address in a site move. These do not replace the redirect work; they complement it by telling Bing explicitly that a migration happened, which helps it reprocess your URLs rather than inferring the move purely from crawling. Doing this in Bing as well as Google is simply finishing the job in both places.

Keep verification and monitoring in both engines

A practical point that is easy to forget is verification. Just as Google Search Console access can lapse in a migration if verification breaks, your Bing Webmaster Tools access can too, and losing it removes your window into Bing exactly when you need to watch the transition. So make keeping site verification through the migration a step for Bing as well, ideally via a domain-level method that survives platform changes. Then monitor both engines after launch: watch for crawl errors, index coverage, and any URLs that failed to redirect. Catching a Bing-side problem, such as a page dropping out of the index, depends on having that visibility, which depends on verification you did not let lapse.

Do not neglect Bing because it is smaller

There is a temptation to treat Bing as negligible next to Google, but that undersells it in two ways. First, Bing still carries real search share in many markets and on many devices, so the traffic is worth protecting on its own terms. Second, Bing’s index and search have fed AI search and assistant experiences, so your Bing crawlability and standing can influence visibility beyond Bing itself. Given that protecting Bing costs almost nothing extra, the same redirects and sitemap plus a few Bing tools, there is no reason to skip it. Treating both engines as first-class in the migration is cheap insurance against losing traffic and AI-adjacent visibility you did not have to lose.

Steps to protect Bing rankings in a migration

  1. Preserve your URLs and 301-redirect any that must change, using one map for all engines.
  2. Re-verify your site in Bing Webmaster Tools, ideally with a domain-level method.
  3. Submit your new sitemap in Bing Webmaster Tools.
  4. Use Bing’s Site Move tool to signal the change of address.
  5. Monitor Bing for crawl errors and index coverage after launch.
  6. Do the same in Google, since one redirect map satisfies both.

Worked example: both engines held together

Consider a B2B site that drew a meaningful minority of its organic traffic from Bing alongside Google. Migrating off WordPress, the team built a single verified 301 redirect map for every changed URL and preserved the rest. On the Google side they used Search Console’s change-of-address and submitted the sitemap; on the Bing side they re-verified in Bing Webmaster Tools, submitted the same sitemap, and used the Site Move tool. Because the redirects were engine-agnostic, both crawlers followed them, and because they signaled the move in both toolsets and kept verification active, they could watch each engine reprocess the site. Rankings held in Google and Bing alike, with no extra redirect work, just the Bing tools layered onto the same foundation.

Limitation: each engine recrawls on its own timeline

It is honest to bound this. Bing and Google reprocess a migration independently, so they will not recover in lockstep; one may settle faster than the other, and Bing’s crawl frequency for your site may differ from Google’s, which affects how quickly its rankings restabilize. Using the Site Move tool and submitting the sitemap help, but they do not force instant reprocessing, so expect a settling period in each engine. The reassurance is that the same correct fundamentals drive recovery in both, so a clean migration recovers in Bing as it does in Google, just on Bing’s own schedule rather than exactly alongside Google’s.

Key points

A migration affects Bing much as it affects Google, because Bing responds to the same fundamentals: preserved URLs, proper 301 redirects, a current sitemap, and a clean recrawl. You build one verified redirect map that serves every engine, then add the Bing-specific tools: re-verify in Bing Webmaster Tools, submit your sitemap there, and use the Site Move tool to signal the change. Keep Bing verification active so you can monitor the transition, and do not neglect Bing, since it carries real traffic and can feed AI search experiences. Each engine recrawls on its own timeline, so expect independent settling periods, but the same correct work recovers both. WPBuildAI preserves your URLs and maps every change to a verified 301, and the same redirect map and sitemap that satisfy Google satisfy Bing, so both engines keep your rankings. Send your web address for a free analysis.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.