Web Site Optimization vs Bandwidth

I up-loaded the xml sitemap for interfacebus up to my site on Google Pages. The xml site map is used by search engines to determine the page addresses of all pages located on a web site. Search engines find your site map via a command within your robots.txt file. Up until now the robots.txt file indicated the site map was out on my server. The sitemap started on my server because Google Sitemaps does not give you the option of having the map in another location.

However, all other search engines find the sitemap via the robots text file. So Google will still check the site map, and hit my bandwidth, but now all the other search engines will go out to Google pages to access the sitemap.

The xml site map is 284k bytes in size and was viewed [down-loaded] 43 times last month. That's over 12 MBytes of server bandwidth. Yes I'm still trying to reduce bandwidth; currently running at 58.35kB/visit.

The html version of the sitemap [used by people] has been viewed 631 times this year. At the bottom of the sitemap is a list of the html pages located on 'Google Pages'; however the xml file will not be listed. The html viewable sitemap is also out on the Google server, saving server bandwidth..

The attached graphic shows the search trend for the term "miniPCI". I checked after my Analytics report indicated only three hits to the miniPCI page on the site [that's 3 hits for the year]. However it looks like I viewed data for a 404 page. The active MiniPCI pages has seen 3,377 page views. The page covering the MiniPCI 100-pin Signal Assignments page has received 333 page views, while the page covering the 124-pin MiniPCI card has received 3,497 page views.