Attach .html to domain name

Question

If anyone can help. I have contacted Apple phone support and they say this is impossible but I believe different.
I am trying to verify my site(web space/domain) with GOOGLE. All they want is for me to attach a .html file to my domain. I created a site using iWeb and have attached(linked) it to my domain space I have(www.domain.com) all GOOGLE want to verify is
Once you verify that you're the site owner, we can provide you with comprehensive statistics and error information about the pages in your site. If you're unable to verify, you can still use the webmaster tools, submit Sitemaps, and see detailed information about those Sitemaps as well as basic information about your site. [?]
We offer two methods of verification. You can either upload an HTML file with a name we specify, or you can add a meta tag to your site's index file. Choose your preferred method below. [?]
Create the HTML verification file specified below and upload it to http://www.thekakeman.com/. [?]
googleffd2dd2cfdbdadb0.html
1. I've created a file named googleffd2dd2cfdbdadb0.html.
2. I've uploaded the file to http://www.thekakeman.com/ and can view http://www.thekakeman.com/googleffd2dd2cfdbdadb0.html in my browser.
This domain has been launched onto the internet with my .mac account. According to google AND my .com provider I have to do this through my .mac since it is launched through there.
I have tried to drag this file to the iDisk folder on my .mac account but no joy. Also created a page in iWeb and attached the file...no joy.
Any takers?

Answer 1

HI Varkgirl
iWeb and my problem persists. I have followed all experst instructions with adding HTML files to my site so that GOOGLE can verify it but I am still unable to do so and now get the following message which APPLE are refusing to help me with this matter as they say it is my Domain companies responsibility..I feel it iWEB!
Here is the Lead.......
We've detected that your server returns a status of 200 (found successfully) for pages that don't exist.
We've detected that your server returns a status of 200 (found successfully) for pages that don't exist. We can't verify sites with this configuration because it would enable anyone to verify ownership of your site. You can try our meta tag verification method or change your server's configuration.
This configuration presents a security risk for site verification and therefore, we can't verify your site. If your web server is configured to return a status of 200 (found) in the header of 404 (not found) pages, and we enabled you to verify your site with this configuration, others would be able to take advantage of this and verify your site as well. To ensure that no one can take advantage of this configuration to view statistics to sites they don't own, we only verify sites that return a status of 404 in the header of 404 pages.
If your server is configured to return something other than a 404 for non-existent pages, try our meta tag verification method or change your server's configuration.
You can change your web server configuration to return a status of 404 in the header of 404 pages and still provide a custom error page (see Apache information and IIS information). Note that we do a HEAD request (and not a GET request) when we check for this. Once your web server is configured correctly, try to verify the site again and we'll recheck your configuration.
Can you make any sense of this?
Thank you for your help
Gavin