Know what the import is for

Bing offers an import route for websites already verified in Google Search Console. Treat it as a convenient ownership and setup workflow. It does not make the two search engines a single reporting system. Before connecting an account, list the production sites you intend to manage, along with the teammate who can authorize access. This small inventory matters when an account contains personal experiments, client properties, old subdomains, and multiple variants of one business website. Import the scope you need rather than turning an unfamiliar account list into your reporting structure.

Select the right account and properties

Open Bing Webmaster Tools and choose the Search Console import option. Read the authorization request and check the Google account shown before accepting it. Then select the intended properties from the import list. Bing's guide explains that imported permissions are checked periodically and that sitemap information can also be imported. If a site is absent, first check whether you are using the correct Google account and whether an equivalent property already exists in Bing. Do not create duplicate site entries as your first troubleshooting step; that can make ownership and reporting harder to understand.

Audit the imported result

After import, examine the property URL, current access, and sitemap locations. An old sitemap may still load successfully while pointing to content the business no longer publishes. Open a few listed URLs and verify that they resolve to the live production site. Record which Google identity supports the connection and how an administrator can disconnect it. This makes future offboarding manageable. If your team relies on an external consultant's account, arrange durable organization access now. Convenience at onboarding should not create an invisible dependency that surfaces only when the consultant leaves.

A hypothetical multi-site import

Imagine an agency with a client's marketing domain, staging host, and retired blog in Search Console. Importing all three would create unnecessary work and potentially confuse a report shared with the client. A better sequence is to identify the production canonical host, import it, review its sitemaps, and confirm sample pages. The staging property remains outside the production dashboard. If the client later moves the blog, the agency updates the inventory before adding anything new. This example is a proposed workflow, not a claim about results obtained from a real agency account.

Keep performance interpretation independent

Once both tools are connected, label every chart with its source. Google clicks belong in a Google series; Bing clicks belong in a Bing series. A connection event should be marked in the reporting timeline so missing early data is not mistaken for a launch failure. Build a simple acceptance record containing the imported site, administrator, relevant sitemap, and first successful page inspection. When access changes, test the connection deliberately rather than waiting for a monthly report to reveal it. The import saves setup effort; thoughtful account ownership keeps that saved effort from becoming maintenance debt.

PUT IT TO WORK

Use the import for setup and ownership, then manage Bing reporting as a separate measurement system.

Sources & further reading

Official documentation informs this guide. Examples are illustrative, and product interfaces or limits can change.

THE WORKSPACE WE'RE BUILDING

From search signals to a useful first draft.

SERP.so is in development. Join the waitlist for a workspace that connects research, content review, and publishing.

Join early access ↗