Welcome to the Q&A Forum

Sure, 10,000 people is enough to run a retargeting campaign.

You might try bringing up the bid to get some more impressions and see how it goes.  100 impressions isn't enough to tell much of anything.  Retargeting does tend to have the highest ROI of any display advertising if you target it properly.  Since the users in your retargeting list are more likely to convert on your site since they've been there before, you can tolerate a higher CPC with retargeting as compared to other display campaigns.

Are you segmenting your retargeting lists into many smaller lists?  You can split your lists into users that have made it further down your conversion funnel, and bid higher the further they've made it down the funnel already (e.g. visited a subscription page and left, or added items to a shopping cart and abandoned it).  If you're using Adwords and Google Analytics, you can do this easily with Google Analytics Remarketing, and retarget any visitors on your site based on things like time on site, pages they've visited, and custom events and goals they've accomplished (or not accomplished).

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.

Do any pages on Domain A link to this page?  Is it going to be off-putting or strange for users to get whisked off to Domain B when they follow these links?  If so, is this a place where a cross-domain canonical might make more sense?

If you go the redirect route, do make sure to update all your internal links from Domain A to go directly to the page on Domain B as to not bleed any link juice by going through the redirect, and to help mitigate the surprise of changing domains (some people look at link destinations before clicking links).

I've been migrating to using Google Analytics for our remarketing lists (see here) to keep all these Adwords pixels from hanging around on my site.  Unless you're using these for doing remarketing on the search network... the Google Analytics segments aren't supported for that yet, but I was told by my reps to expect that soon.

As Remus said, there's absolutely no problem with having multiple Adwords remarketing pixels on one page.

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.

(Using example.com instead of your domain in case you want anonymity later)

If you try to go to any of these m.example.com URLs on your desktop computer, you're redirected on the server to a www.example.com URL.  I'm guessing Googlebot and Googlebot-Mobile cannot access m. pages (unless you're sniffing out Googlebot-Mobile specifically to serve it m.example.com pages).  If you're looking at screen resolution for these redirects, you might not be catching Googlebot-Mobile, as I don't think Googlebot-Mobile gives a screen resolution in its user agent.  I believe you want Googlebot indexing your www. content, and Googlebot-Mobile indexing your m. content, so you'll need to sniff out Googlebot-Mobile's user agent (see here), and redirect it to m. content.

Also of note is that I think these should be 302 temporary redirects, and not 301 permanent redirects between your www. and m. versions, as they're not really permanent, just getting a given user to the right version of the site.  Also, you don't let me switch from the mobile version to the desktop version, which drives me bananas!  Let users choose after the initial redirect.  If you allow people to switch, but maintain 301 redirects, the browsers may cache some of the redirects which will lead to weird behavior if people hit a page that redirected before.

You don't have a robots.txt file at m.example.com/robots.txt, as that redirects to www.example.com/robots.txt even on my phone.  I don't think this is the root of the problem, but once you figure things out, you can set up a robots.txt file on your m. subdomain.

Adwords Editor doesn't download the negative keyword or placements lists from your shared library or allow you to edit these.  You have to use the web interface to edit the keywords in the list (including match type), and also to link the list to every campaign you want it to apply to.

If you need to make many bulk edits, you could download the list, delete the original list, and then copy/paste the new list of negative keywords.

To indicate match type when adding the keywords here, you need to put brackets around exact match keywords, for example: [keyword], quotes around phrase match keywords, for example: "keyword", and nothing for broad match keywords, for example: keyword.  You can easily wrap those around keywords in Excel using the concatenate command.

As far as I know, you can't do this in Google Webmaster tools.  It would have to be a parameter like shopby= instead of shopby/ as you suspect.

This sounds like a good place to use the rel=canonical tag.  You want those pages to exist, and if people link to them, you want them to pass their link juice back to the /tshirts/ page.  These shopby pages will have a subset of the info on the /tshirts/ page, so Google should respect the canonical tag.

Other search engines beyond Google should respect the canonical tag as well, so that's another benefit to doing it outside of Google Webmaster Tools.

Here's some reading:

rel=canonical: http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html

Using canonical to a view all page: http://googlewebmastercentral.blogspot.com/2011/09/view-all-in-search-results.html

If you want to do it yourself, I highly recommend Optimizely.  You can find a lot of resources around the web on tests to try, and with Optimizely, you can implement them yourself.  I use it everyday, and implementing and running tests is a breeze.

They also interviewed me and put me on their blog awhile back.

I don't believe that's possible.  You'd have to create a special ad group like you suggested just for those keywords to get the capitalization in that word to behave that way.  Google's capitalization guide is here for DKI.

As a user, I prefer the URLs without.  Looking at the SEOMoz 2011 Rankings, longer URLs correlate to worse rankings, so do yourself and your users a favor and save them 5 characters.

http://www.seomoz.org/article/search-ranking-factors#metrics-8

Google's guide for AJAX crawling is here.  This is a considerable amount of work though, and honestly I wouldn't recommend it.  Google is getting better everyday at crawling JavaScript content.  You can try to test whether it's indexing this content by doing some very specific Google searches for things only rendered by JavaScript, and seeing if your pages rank for those searches.  If they do, there's a good chance that Google is reading and rendering your JavaScript properly.  Even if they don't now, it's likely only a matter of time before they do.

I don't imagine that Rogerbot has an army of engineers at Moz trying to figure out how to render JavaScript outside of a browser, so I wouldn't expect this to come to Moz crawls anytime soon.  I also doubt that Rogerbot would understand what's going on in Google's guide either, as I wouldn't expect many sites to have actually gone through this process.

Why is most of your main content generated by JavaScript?  It sounds like you should be rendering some of this on the page in good ol fashioned HTML.  A lot of times this doesn't require an entire redo of a website. It could just be a matter of loading some default HTML with the page, and then updating it with JavaScript, instead of rendering all of it with JavaScript.  It would be easier to see if you share the site (if not, I understand).

Keri has it right, you can include or exclude users based on pages they've visited or actions they've taken on your site.  So you can target people who visited a certain page (or did something like added an item to their cart), and then exclude those who have checked out.

There's a bunch of remarketing features within Adwords, like Dynamic remarketing for retailers, remarketing lists for search ads, & Google Analytics remarketing.  Beyond Adwords, there's Facebook, Twitter, and partners to get remarketing ads on placements outside of the Google Display Network, like Adroll and Doubleclick.

Yeah, that's a problem.  That means if people put links to http://mydomain.co.uk, they won't be passing their link juice on to http://www.mydomain.co.uk if the redirect is a 302 (temporary) redirect.  You should configure this to be a 301 (permanent) redirect.

For geo-redirects, I do not recommend you use 301 redirects.  Browsers can cache these, so if you tell a browser in Canada that example.com should redirect to www.example.com/ca-fr, and later the user changes their language to English, and then tries to go www.example.com, the browser could use that redirect again to go back to the French version without hitting your server.  301 tells the browser that www.example.com ALWAYS (permanently) goes to www.example.com/ca-fr.  Page rank isn't really a consideration with these, since Googlebot always comes from the US, so it should never hit these redirects.  If example.com always goes to one of the versions via a redirect (i.e. you don't serve content under that root URL), then you do have a bit of problem with redirects.  You don't want to 302 Googlebot to another page for your home page, but at the same time, you want to avoid weird redirect behaviors for your customers.

Google can visit the international versions directly without redirects, right?  They should have no problem indexing those pages then.

I agree with István, get some local links to your different local versions, register them each with Google Webmaster Tools (and Bing), put up sitemaps for each, and implement the hreflang tags in your sitemaps (or pages).  That way Google can easily index each version, and knows exactly what each version is for.

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.

First, the site structure you're proposing sounds fine.  The shorter URLs with just the country code look better to me, but I'd lowercase the country codes.

Second, there are a few things you can do to make sure the search engines are doing the right thing with respect to content for different countries.  You can set you location target for each directory within Google Webmaster Tools in Site configuration > Settings.  You can also set language metadata, or set HTTP headers to clue in Bing as to what language and country the page is targeting (see http://www.bing.com/community/site_blogs/b/webmaster/archive/2011/03/01/how-to-tell-bing-your-website-s-country-and-language.aspx).

Even though these are targeted to different countries, they show up to the search engines as duplicate content since the content is so similar, and until recently there wasn't much that could be done about it.  You could either rel=canonical to the page that caters to your main audience, or just accept that there would be some duplicate content.  Google recently announced support for a rel=alternate tag which should help to mitigate this.  You can read more about it here: http://googlewebmastercentral.blogspot.com/2011/12/new-markup-for-multilingual-content.html.  The tl;dr of this is you can set rel=alternate tags to signal which pages are alternates of each other, and rel=canonical to one preferred version.  When this page would come up in search, it'll use the title and description from the preferred page, but if the searcher is in a country where you have an alternate version, it'll use the URL for the alternate page.  It's not perfect, but at least it's a step in the right direction.

You should be able to can control the rate at which the bot accesses you pages by adding a crawl delay in your robots.txt file. Robots.txt and crawl delay is discussed here: http://en.wikipedia.org/wiki/Robots_exclusion_standard, and Slurp bot here: https://help.yahoo.com/kb/SLN22600.html.

Should look like this in your robots.txt file:

User-agent: Slurp

Crawl-delay: 30

The crawl delay is the number of seconds the bot should wait between pageview (ask your IT guys what's appropriate for you).  I stuck 30 in there, meaning the Slurp bot would only be able to access up to 2 pages a minute.

rel=canonical is more for when there are parameters on your URLs that you can't really do anything about.  When you know one URL is being served, but should be another, you should use a 301 redirect.  So in this case, you should pick which URL you like better, either with or without the trailing slash, and redirect one to the other.  Google treats both of these as two completely separate pages, which is why you're seeing views on one and not the other.  If you can't configure the redirect, then you could resort to rel=canonical.

If you have pages with similar content but not a lot of views, then 301 redirecting that page to another page with more views would be fine.  That'll pass it's pagerank along, and good for people who find that original URL later, because they'll go to an actual page instead of your 404 page.

Here's Matt Cutts take on it: http://www.youtube.com/watch?v=r1lVPrYoBkA.

He says Googlebot will follow 301 redirect chains.  Once you get to 4 or 5 in a row... he says Googlebot might bow out.  He recommends 1 or 2, or maybe 3 in a row.

So based on what he said, you should be completely safe doing 2 redirects.