【唐诗】《輞川集 竹里館》 王維：獨坐幽篁裏，彈琴復長嘯。深林人不知，明月來相照。

永夜

没有不值得去解决的问题，也没有不值得去学习的技术！

GSC → Bing Webmaster Tools: Reduce Duplicate Verification for Multilingual Sites

Figure 3: Bing recognized the new it-IT site from Google Search Console and simultaneously discovered the existing 1 sitemap

作者：

永夜

在

Post Views: 4

Recently, while continuing to add new languages to the A Tour of Go multilingual project, I also took the opportunity to reorganize the post-live closeout process for search engines.

In the past, every time I added a new locale, I would separately handle:

Plaintext
Google Search Console
+
Bing Webmaster Tools

The Google Search Console side is usually straightforward:

Plaintext
Add site
→
Complete verification
→
Submit sitemap.xml

As for Bing Webmaster Tools, I had always treated it as another independent process.

But after launching the Italian site this time, I reused Bing’s connection with Google Search Console and found I could eliminate quite a bit of duplicate work.

My actual workflow now is:

Plaintext
Google Search Console
↓
Complete site verification and sitemap
↓
Bing has already kept the Google Search Console account connection
↓
Manually Import from Google Search Console
↓
Directly import the new locale site and existing sitemap

There is an important boundary here:

The fact that Bing and Google Search Console are already connected does not mean that all new sites added to Google will automatically sync to Bing in the future.

Every time a new locale is added, I still need to manually perform an Import in Bing.

But compared to redoing the site verification and sitemap configuration from scratch, this process is already much simpler.

1. First complete the standard closeout in Google Search Console

Every new production locale for A Tour of Go completes its Google Search Console closeout after officially going live.

This time, the Italian site is:

Plaintext
https://it-go-dev.shuijingwanwq.com/

Official sitemap:

Plaintext
https://it-go-dev.shuijingwanwq.com/sitemap.xml

After submitting it in Google Search Console, the status shows:

Plaintext
Status: Success
Submitted: September 6, 2026
Last read: September 6, 2026
Discovered pages: 105
Figure 1: it-IT's sitemap.xml has been successfully read in Google Search Console, discovering 105 pages
Figure 1: it-IT’s sitemap.xml has been successfully read in Google Search Console, discovering 105 pages

This count of 105 exactly matches the current production sitemap count.

For my multilingual project, reaching this point means the standard post-live closeout on the Google side is complete.

I should specifically note:

What is completed here is the submission of the site and sitemap, not waiting for Google to actually finish indexing all pages.

Whether pages are already indexed or when they will appear in search results is not a production launch gate.

Therefore, I will not wait here for days or even weeks until all pages are indexed by Google before considering this locale’s launch complete.

2. Bing can actually reuse Google Search Console’s authorization

Next is Bing Webmaster Tools.

I previously always thought of:

Plaintext
Google Search Console

and:

Plaintext
Bing Webmaster Tools

as essentially two parallel systems.

However, Bing natively supports connecting to Google Search Console.

After checking the settings, I found that my current Bing account has actually maintained the Google Search Console connection.

The settings page shows the corresponding Google account:

Plaintext
shuijingwanwq@gmail.com

The action displayed in the menu is already:

Plaintext
Disconnect

rather than:

Plaintext
Connect
Figure 2: Bing Webmaster Tools has maintained its connection to the Google Search Console account
Figure 2: Bing Webmaster Tools has maintained its connection to the Google Search Console account

This means Bing already has the corresponding Google Search Console authorization.

So when adding new locales later, I don’t need to do the following again:

Plaintext
Reconnect to Google
Re-authorize account

This part can be directly reused.

For a project like this that will continuously add languages, this detail is quite valuable.

For a single site, it might feel like it doesn’t save much time.

But if I continue adding:

Plaintext
pt-BR
ru-RU
tr-TR
...

redoing the same authorization for every language becomes increasingly repetitive.

3. But “already connected” does not mean “automatically synced later”

This was also the point I was most likely to misunderstand this time.

At first, I naturally thought:

Since Bing is already connected to Google Search Console, will Bing automatically sync a new site whenever I add one in Google Search Console?

That is actually not the case.

At least for my actual operations this time, I still needed to:

Plaintext
Import from Google Search Console

That is:

The account connection can be reused, but the new site itself still must be imported manually.

These two concepts need to be separated.

What is already connected is:

Plaintext
Bing
↔
Google Search Console account

This does not mean it automatically establishes:

Plaintext
Google new site
↓
Bing new site

So my standard understanding now is:

Plaintext
Account authorization: long-term reuse
New locale site: manually Import once each time

This is more accurate.

4. Import the new it-IT site from Google Search Console

In Bing, I select:

Plaintext
Import from Google Search Console

Afterwards, it directly recognized the newly launched Italian site.

The page shows:

Plaintext
Total sites found: 1
Importable sites: 1
Total sitemaps found: 1

And I can see the corresponding site already has:

Plaintext
Sitemap count: 1
Figure 3: Bing recognized the new it-IT site from Google Search Console and simultaneously discovered the existing 1 sitemap
Figure 3: Bing recognized the new it-IT site from Google Search Console and simultaneously discovered the existing 1 sitemap

This is the most convenient part of the whole process.

If I had handled Bing completely independently, I might originally have needed to redo:

Plaintext
Add site
→
Prove site ownership
→
Find or enter sitemap URL
→
Submit sitemap

But now it actually becomes:

Plaintext
Google has completed verification
+
Google already has the sitemap
↓
Bing Import

and I can reuse this existing information.

5. After importing, Bing directly brings in the official sitemap

After completing the Import, I went to the “Sitemaps” section in Bing Webmaster Tools.

I can see the official sitemap already exists:

Plaintext
https://it-go-dev.shuijingwanwq.com/sitemap.xml

Status:

Plaintext
Success

It also shows:

Plaintext
Known sitemaps: 1
Sitemaps with errors: 0
Sitemaps with warnings: 0
Total discovered URLs: 105
Figure 4: After Bing import is complete, the official sitemap has been successfully read, all 105 URLs are recognized, with 0 errors and 0 warnings
Figure 4: After Bing import is complete, the official sitemap has been successfully read, all 105 URLs are recognized, with 0 errors and 0 warnings

This result is more valuable than a simple:

Plaintext
Import successful

Because it ultimately proves:

Plaintext
Site has entered Bing
+
Sitemap already exists
+
Sitemap status is normal
+
Discovered URL count is correct
+
No errors
+
No warnings

At this point, Bing’s standard closeout is complete.

6. For future new locales, the process can be compressed like this

After this actual operation for it-IT, my standard closeout path for Google and Bing is now quite clear.

Google Search Console:

Plaintext
Production is live
↓
Add/confirm new locale site
↓
Submit official sitemap.xml
↓
Confirm sitemap status is successful

Bing Webmaster Tools:

Plaintext
Keep existing Google Search Console account connection
↓
Import from Google Search Console
↓
Select the newly added locale this time
↓
Complete import
↓
Confirm sitemap is successful

Compared to treating Google and Bing as two completely independent webmaster platforms before, many duplicate steps can now be eliminated.

Especially:

Plaintext
Bing ownership verification
Bing manual sitemap reconfiguration

Since existing Google Search Console information can be imported, there is no need to redo them.

7. What can be reused, and what still cannot be skipped

This time I also clarified the boundaries.

What can be reused long-term is mainly:

Plaintext
Google Search Console account connection
Bing's authorization for Google

While each new locale still needs to individually complete:

Plaintext
Google Search Console new site
Google sitemap
Bing Import new site
Confirm Bing sitemap

In other words:

Reducing duplicate operations does not mean fully automating search engine closeout.

I think this point is quite important.

If one mistakenly assumes:

Plaintext
Bing is connected to GSC
=
All future new sites will automatically enter Bing

it is very likely to miss the Bing closeout for subsequent locales.

Therefore, in my official new language workflow, both Google and Bing will still be retained.

It’s just that the Bing part goes from:

Plaintext
Re-establishing the entire site

shortened to:

Plaintext
Import + check results

8. Why I don’t wait until “truly indexed” before finalizing Production

When doing SEO, it’s easy to fall into another misconception:

The sitemap has been submitted, but the pages haven’t been truly indexed by the search engine yet—does that mean the launch isn’t complete?

I have now clearly separated these two things.

Production launch completion depends on:

Plaintext
Production acceptance
↓
HUMAN visual gate
↓
first-production finalize
↓
production_state=live

Search engine post-live closeout depends on:

Plaintext
Google sitemap submitted
+
Bing sitemap submitted/imported

While the actual:

Plaintext
indexing
coverage
ranking
organic traffic

are all subsequent asynchronous processes handled by the search engines themselves.

These results might take:

Plaintext
a few days
a few weeks
or even longer

So there is no need to make the Production lifecycle wait for the search engines.

The same applies to this Italian site.

Both Google and Bing sitemaps have been successful, and 105 URLs have been recognized.

At this point, the search engine closeout is already complete.

Next, I just need to maintain it normally and wait for the search engines to crawl and index on their own.

9. Google and Bing are standard items; other search engines are decided by locale

Currently, in my multilingual Production workflow:

Plaintext
Google Search Console
+
Bing Webmaster Tools

are already the standard post-live closeout for all new locales.

But this doesn’t mean that every language must be integrated with all regional search engines in the future.

For example, for the Korean site:

Plaintext
ko-KR

I also additionally handled South Korea’s:

Plaintext
Naver Search Advisor

because it has value for the Korean market itself.

But for Italian:

Plaintext
it-IT

there is no need to mechanically copy Naver.

So my rule now is:

Plaintext
Google: all Production locales
Bing: all Production locales
Regional search engines: decided by target locale / market

This ensures basic search coverage without adding meaningless operations just for the sake of process completeness.

10. For long-term multilingual projects, eliminating one duplicate operation is also valuable

If there was only one website, this optimization might not seem like anything special.

After all, manually adding a Bing site doesn’t take too long.

But the goal of the A Tour of Go project is not to stop at:

Plaintext
zh-CN
ja-JP
de-DE
fr-FR
ko-KR
es-ES
it-IT

More locales will continue to be added later.

When the same process has to be repeated dozens of times, many originally inconspicuous duplicate steps will start to incur noticeable costs.

So I am increasingly inclined to handle it like this:

Processes that have already been verified and can be safely reused will not be redesigned for the next language.

For example:

Plaintext
Production verifier
Ad implementation
Locale Surface Review
TranslationUnit workflow
Google / Bing closeout

should all be turned into a stable baseline as much as possible.

Adding a new locale should only handle:

Plaintext
what is genuinely new for this language

rather than reinventing the entire workflow.

11. Summary

The search engine closeout for the Italian site this time didn’t encounter any complex technical issues, but it allowed me to streamline a small workflow that will be repeatedly executed over the long term.

The actual path has now become:

Plaintext
it-IT Production live
↓
Google Search Console
↓
sitemap.xml successful
↓
105 pages
↓
Bing has kept Google Search Console account connection
↓
Import from Google Search Console
↓
Recognize new site + sitemap
↓
Bing sitemap successful
↓
105 URLs
↓
0 error / 0 warning

The most important conclusion is not:

Bing can automatically sync with Google Search Console.

Because that statement is not accurate.

A more accurate statement would be:

Bing can long-term reuse the Google Search Console account authorization, and quickly import the site and sitemap for each new locale via manual Import.

So when adding new languages in the future, I will still perform the Bing closeout.

But I will no longer redo a duplicate site verification process.

For a long-term project that will continuously add locales, this slight process convergence is quite valuable when accumulated.

系列导航

需要长期技术维护或远程问题排查？

我是拥有 15+ 年经验的 PHP / Go 后端工程师，长期关注已有系统维护、Bug 修复、性能优化、服务器排查、WordPress 网站维护和小功能迭代。

如果你的项目遇到以下情况，可以先从一次小问题排查开始合作：

  • ✅ PHP / Laravel / Yii2 老项目无人维护
  • ✅ Go / Gin 后端接口需要排查或优化
  • ✅ WordPress 网站访问慢、报错或插件冲突
  • ✅ Nginx / MySQL / Redis / Linux 服务器异常
  • ✅ CDN / Cloudflare / DNS / HTTPS 配置问题
  • ✅ 需要长期远程技术支持或兼职维护

更多介绍请查看：关于我 & 合作

微信：13980074657
邮箱：shuijingwanwq@gmail.com
Telegram：@shuijingwan
GitHub：https://github.com/shuijingwan

更多文章