A few months ago I posted an article about FamilySearch's "standardized place names" introducing errors (see FamilySearch Introducing Errors) but not only does nothing seem to have been done to fix the errors, but they seem to be getting worse.
I am not talking here about errors in indexing. There are many indexing errors, some of which give rise to place name errors, especially when the original document is not available to correct it.
The errors I am talking about here are not indexing errors but algorithmic errors, when the place name in the index is correct, or almost correct, and FamilySearch's algorithm changes it to something wrong.
Also, FamilySearch flags many correct place names as wrong, with warnings like !Missing Standardized Death Place, which encourage users to change a correct place name to a wrong one.
These errors can destroy the hard work of indexers, and that of family historians who have contributed to FamilySearch Family Tree. These algorithms should never have been let loose on the database before being tested to avoid such errors.
Here is another example:
People in Trans-Caucasia, on the other hand, seemed to prefer to die in Cleveland, UK in the town of Guisborough: