Welcome to the Q&A Forum

I think it's worth it as it should only take a few minutes to set up, and it's good to have a robots.txt, even if it's allowing everything.  Put a text file named "robots.txt" in your root directory with:

<code>User-agent: *
Disallow: 

Sitemap: http://www.yourdomain.com/none-standard-location/sitemap.xml</code> 

Read more about robots.txt here: http://www.seomoz.org/learn-seo/robotstxt.

Somehow Google is finding these pages, but you're disallowing the Googlebot from reading the page, so it doesn't know anything about the meta noindex tag on the page.  If you have meta noindex tags on all of these pages, you can remove that line in your robots.txt preventing bots from reading these pages, and as Google crawls these pages, they should remove them from their SERPs.

Here's a good SEOMoz post about this: http://www.seomoz.org/blog/robot-access-indexation-restriction-techniques-avoiding-conflicts.  What's most likely happening is that the disallow in robots.txt is preventing the bots from indexing the page, so they're not going to find the meta noindex tag.  If people link to one of these pages externally, the disallow in robots.txt does not prevent the page from appearing in search results.

The robots.txt syntax you're using now looks correct to me for what you're trying to do.

This is what rel canonical tags are for!  Read more about them here: http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html

It sounds like the aspx pages are still being served?  If so, you should 301 redirect them to the new friendly URLs with the htm extensions.  Google doesn't care about which page extension you use.

I'm not sure about the answer to the first question, but there was an SEOMoz post awhile back about scraping Facebook comments, so that you could get search engines to be able to read them.  If you can scrape them, then you should be able to set something up to detect with some frequency when new comments are added.  If you use them, you'll probably want to set this up so the comments can be indexed.

I've never used Facebook comments, so there might already be a way for Facebook to notify you when comments are added.

Add canonical tags to all the https pages that have a http counterpart pointing to the http version.  Here's the original Google Webmaster Blog post about canonical tags: http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html

Your meta descriptions aren't very long at 60 characters.  You could write longer meta descriptions that include more info specific to that watch.  Like, for http://www.traxnyc.com/Mens-Diamond-Watches-G-Shock-Watches-Casio-G-shock-Atomic-Solar-Watch-GWM5600-1V-item25463.html, the meta description is "Mens G-Shock Watches White Stainless Steel Item Price : $120", but the product is "Casio G-shock Atomic Solar Watch GWM5600-1V".  When this page appears in the SERPs (when I search for the page title at least), the meta description is short so Google fills in a lot:

Mens G-Shock Watches White Stainless Steel Item Price : $120. ... TraxNYC is a leading retailer of Diamond Jewelry in the heart of New York's famous Diamond District .... Full Size Picture for Casio G-shock Atomic Solar Watch GWM5600-1V ...

Each subdomain may have its own robots.txt file.  So for that subdomain, you can put:

User-agent: *
Disallow: /

In the robots.txt, and that should do it.

Please note that disallowing pages in robots.txt will not necessarily mean they won't appear on search result pages.... if people link to pages that are disallowed on that subdomain, they can still appear in SERPs.  I had this happen with a few pages, which leads to funny listings in the SERPs because Google has to guess what the page title and description of the page should be, since it's not allowed to read the page.  The meta noindex tag is the way to go if you want to be really sure the page doesn't appear in the SERPs.  If you use that, don't disallow the page.  Here's a recent SEOMoz post about it: http://www.seomoz.org/blog/robot-access-indexation-restriction-techniques-avoiding-conflicts

If you just want the directory page removed from SERPs, but not the images, you can put a meta noindex tag in the of the page (see here).  It'll look like .  Provided you link to the images from other pages, you should be in business.

I don't think it would hurt your rankings at all.  I would exclude it as you don't want people wandering in to your site on a directory page.

For Google, you can go into your Webmaster Tools, and go to the Site configuration > URL parameters page.  You can set the parameters in your URLs to things like "Sorts", "Paginates", or "Narrows", so that Google will know how the parameter changes the info on the page.  Once Google knows how the parameter effects the page, presumably they'll give the right links and display URLs in their search results.

Last year was a pre-panda world.  A lot has changed over the last year in Google's search algorithm.  SEOMoz keeps a complete list here: http://www.seomoz.org/google-algorithm-change.

Using social bookmarking sites and article submissions aren't pulling the same weight as they used to.  Content is king now... you'll have to write high-quality posts that people want to read, link to, tweet about, share on Facebook, etc.

One thing you can do is install Google Webmaster Tools on your site, log in and go to Site configuration > Settings, and set your Geographic target to the United States.

For Bing and other search engines, you can set the content-language in a meta tag or in your HTTP headers (see here).

If my detective skills aren't lacking, his site is http://www.njtraininggrounds.com/.

Using display:none is fine.  There's JavaScript on the page that will make those items display when the users takes some action on the menu.  Google has some way of reading the JavaScript to see what may be displayed, and at this point, I'm sure they're very good at detecting these types of menus.  I don't think you can't make a menu like that without using it, and tons of sites use them.

Obviously, you shouldn't use display:none to cloak text on the page, when no user action can get that text to be displayed.

This is why the canonical tag was invented, to solve duplicate content issues when URL parameters are involved.  Set a canonical tag on all these pages to point towards the version of the page you want to appear in search results.  As long as the pages are identical, or close to it, the search engines (most likely) will respect the canonical tag, and pass along the duplicate versions link juice to the page you're pointing to.

Here's some info: http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html.  If you Google "canonical tag", you'll find lots more!

I like lowercase because when I type URLs by hand, I don't think to capitalize things.  If you capitalize things, you have to get the casing right to make the URL valid (unless you're setting up all sorts of fancy redirects), otherwise you a 404 and are left scratching your head.  Also, I agree with Dan that it looks better.

Hyphens vs. underscores is a classic question; Matt Cutts says to go with hyphens: http://www.youtube.com/watch?v=Q3SFVfDIS5k.  I like that better too.

For images at least, they say alt >> title.