Posted by graper on October 12, 2009 at 2:11pm
Jump to:
| Project: | XML sitemap |
| Version: | 5.x-1.7 |
| Component: | xmlsitemap_engines.module |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I recent upgraded by xmlsitemap module for Drupal 5 to the new 1.7 version. WHen attempting to verify my site with the page verify method I kept getting an error. It seems that Google is not verifying the contents of the HTML file that they want you to download and put into your site.
The current response from the drupal module is an some code that says Hello Google. Seems that they changed up the game and didn't tell anyone. They now want in the file "google-site-verification: [nameoffile].html"
Granville
Comments
#1
Google changed its verification methods and now requires meta data in the file. I suggest you upload a static file of the name given you by Google with the contents it also gives you as a work around for 5.x. Will the static file option work for you?
Version 6.x requires you to have http://drupal.org/project/site_verify module for programmatic creation of the verification file.
#2
yes this will work.
Just to keep you informed, when I attempt to verify the site, I get this message
Your verification file does not have the right content. Download the verification file below and upload it to your server.it links to http://www.google.com/support/webmasters/bin/answer.py?answer=35638&hl=en which has a section that states the following as part of the html file validation
* Your verification file does not have the right content.
We accessed your verification file, but it didn't contain the expected content. To avoid this issue, download the verification file and upload it to your server without making any changes to it.
#3
I can confirm this. Isn't working with google anymore due to the change in the file.
#4
I committed a fix to CVS that will temporarily fix this. Your best solution until Site verificaiton is ported to Drupal 5 is to upload the file yourself.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.