Non-translated pages in translated directories taking over search results

[bnb]

Looking for a reference to the New Buffer depreciation, I searched for "node js new buffer deprecated" on Google, and this was the first result:

Going to the page, however, I realized that this was a "translated" version of the page:

Unfortunately, it seems that this page itself is not actually translated and is taking over the search results. Whether you're looking for it in english or the translated version, this is a super not good user experience since the page is in the translated layout but the content itself isn't actually translated.

I feel like there needs to be some kind of solution here since this brings up a few different problems. Potential solutions:

• Don't publish pages that aren't translated
• Set canonical URL on all translated pages to the english version
• Detect browser language and have an overlay that recommends going to the browser language's version of the page.

[nschonni]

@alexandrtovmach I think you were going to enable the setting so that untranslated pages weren't pushed from Crowdin till they started to be translated

[nschonni]

Ping @alexandrtovmach do you have a way of fixing this on the Crowdin side before I manually nuke all these untranslated pages that were added?

[thomscoder]

was this bug solved?

[bnb]

probably not