They keys operate based on the handling and requirements of Google, and not specifically for the module itself. So you will need to register the url's with Google for those to operate in the site. I've not been able to reproduce the issue with the bump out of the interface from entering the keys, but I will narrow this down and correct in the next release version. As for the url in the API key - you don't need the full url in the module, and its build by design for handling the partial name of the url specifically. This is because in house here, as well as many organizations switching from staging to production of a site generally means changing a staging to production URL may mean only a slight modication of the URL itself, and only one key may be required for that adjustment, which from the API key perspective the same key works for both domains.