IWeb Root Directory solution

Question

I had a question and saw some other discussions regarding publishing your iWeb '09 created site via FTP to a non-MobileMe webhost.  After some experimentation, I think I found one possible answer.
You have to change your Site Name in iWeb to whatever the folder is that your web-host needs.  Some are public_html, some are web, some could be another thing entirely.
For example, my webhost used to require that all uploaded content be placed in a folder called public_html.  So, in iWeb I had to change the site name to public_html.  Then, when I uploaded through iWeb's FTP, it went straight to a public_html folder and would appear as my webdomain without all of those extra /names that people were complaining about. 
     My webhost seemed to have changed recently so when I uploaded to public_html, my site would come up www.mydomain.org/public_html/welcome.html
Not the worst thing in the world, but I didn't like having that extra /public_html/ added to my URL.  After some experimenting, I found that the new folder my webhost seemed to want was web (don't ask me why), so I changed my Site Name in iWeb to web, uploaded, and now I am back to good old www.mydomain.org/welcome.html  without that extra /web or /public_html in my URL.
I hope that this helps anyone searching like I was for an answer.  It can be a little confusing, so if you have any more questions, post to this thread and I will try to explain further.  It may not work for every webhost, but it worked for mine.

Answer 1

Read this :
     The concept of iWeb Sites
A Site, which is just a folder, is a convenient way to organize your pages based on topic, subject or whatever you choose to keep relevant pages together. I’ve been doing that for the past 17 years, and I find it rather natural.
But since iWeb is doing it, it seems to confuse & frustrate people. iWeb shouldn’t do it, they say. As if there is a law that demands it.
To avoid the Sitename in the URL, read my solution. It's very technical but in the end it saves time. And best of all, iWeb is not involved :
     Avoiding the iWeb Sitename in the URL
An easier, time-wasting, solution is to publish to a folder on your desktop.
Open that Site folder and move the content of that folder to the root of the webserver with a FTP application.
(The root of a webserver is where the file or folder, shown immediately to the righthand side of the domainname, is stored.)
Everytime you make changes to a page, you have to repeat these steps.
But the result is what you want.
And here's a re-post with some additional info about using an index.php file to avoid overwriting the index.html file iWeb creates :
    Avoiding the iWeb Sitename in the URL
Works on all servers. With or without a subdomain I may add. Like this one :
     http://wyodor.byethost8.com/htdocs/index.html
Not as easy as publishing to a folder, but in the end it saves time. Again.
See this post that explained the link above :
Re: iWeb keeps populating a site name at the end of my url.  Causing error.