This "guess" seems wrong to me. As one that has gone through the trouble to generate such and entry for Google
, it is easy to do for a given location or two. But for hundreds or even thousands of locations it would be daunting to set up let alone maintain with the current process required by Google.
You misunderstand my post, or I was not clear enough. My "guess" was about the programming required on the church end to generate one web page with a unique URL per meetinghouse from the maps.lds.com database. The availablity of the database infrastructure is obvious to anyone who uses maps.lds.org and understands how dynamic web sites are built. I still see that piece as no big deal, just generating URLs with a slightly different database logic.
But you are right about the process to update Google's own listings being a non-trivial task. That is why I am calling that the hard part.
jbh001 wrote:This Google requires a verification process before you can update the listing. This required getting a PIN from Google, and then being at the phone number listed when Google initiates and automated call for you to enter the PIN to verify your identity to Google.
Someone in Salt Lake is not going to be able to remotely answer the phone in my meetinghouse in Oklahoma to enter Google's PIN.
Even at that, it then took 3 to 8 months for Google update their listing with the information I provided.
Google does provide a bulk upload process for multiple entries. The generation of that bulk upload file, and subsequent verification, need to happen at CHQ. Your experience is evidence of that. It really is not feasible to authenticate and verify onesie-twosie at the local unit level, where there is no postal delivery or regular phone service.
I have no hands-on experience with this. I'm just going by what I have seen in Google's documentation and user forums.