Due to some questions over direct traffic and Googlebot behavior, I want to do some log file analysis.  The catch is this is a Mac shop, so all our systems are on OS X.  I have Windows 8 running in an emulator, but for the sake of simplicity I'd rather run all my software in OS X. This post by Tim Resnik recommended Web Log Explorer, but it's for Windows only.  I did discover Sawmill, which claims to run on any platform. Any other suggestions?  Bear in mind our site is load balanced over three servers, so please take that into consideration.

I successfully enabled rel=publisher on our WordPress blog, and as a test I also enabled rel=authorship for a set of blog posts.  (Tested both in Google's Rich Snippets Tester.)  However, on the individual blog posts the publisher credit disappears.  Is there a way to enable both to appear on blog posts?

So my company is upgrading its Internet bandwidth.  However, apparently the vendor has said that part of the upgrade will involve changing our IP address.  I've found two links that indicate some care needs to be taken to make sure our SEO isn't harmed: http://followmattcutts.com/2011/07/21/protect-your-seo-when-changing-ip-address-and-server/ http://www.v7n.com/forums/google-forum/275513-changing-ip-affect-seo.html Assuming we don't use an IP address that has been blacklisted by Google for spamming or other black hat tactics, how problematic is it? (Note: The site hasn't really been aggressively optimized yet - I started with the company less than two weeks ago, and just barely got FTP and CMS access yesterday - so honestly I'm not too worried about really messing up the site's optimization, since there isn't a lot to really break.)

Our main site, www.domain.com, is on an IIS 6 server.  When we started our blog, we wanted to put it in a subdirectory (domain.com/blog), but we couldn't because our IT people refused to support it.  Instead, we built it on a third-party Apache server and configured it to open under blog.domain.com.  However, I came across this SEOmoz post about the glories of reverse proxies, so I've persuaded our IT people to take a swing at it. We got it to work on a staging server, but the permalinks won't change (still appear as blog.domain.com/slug).  The IT guys say it's due to a configuration problem with WordPress.  Can somebody out there point me in the right direction as far as working out the URL issues with this?