Welcome to the Q&A Forum

I agree with david, this may have been a more effective approach when exact match keywords in domains were weighted heavily, but that is not the case anymore. You would risk, and probably lose more value than you would gain from this transition

_Definitely _don't create any duplicate content here. I think you're on the right track, though: create some navigation pages that are optimized for unbranded search, and use those as an alternative way to find product pages, beyond just the original branded way. Good luck! Kristina

Thanks everyone for you giving me your viewpoint. I was particularly interested with MorganNw answer, but I have not found any data to support this (as much as it would have been great if it was like that!)

While I do not know how Google treats HTTPS in regards to site speed, WebPageTest.org uses the following to score a site's Time To First Byte: "The target time is the time needed for the DNS, socket and SSL negotiations + 100ms. A single letter grade will be deducted for every 100ms beyond the target." Which means WebPageTest does not penalize a site for being secured. Edit: For redirections, 301 everything and change previously added redirects to point to the HTTPS so you don't end up with chained redirections. As far as GWT is concerned, I would add both sites (http://site.com and https://site.com) and use the Change of Address feature on the HTTP one to the HTTPS one. Hope this helps.

Hi, If you're worried about the Freshness factor for search, I don't believe it specifically applies to individual pages such as your product page.  It doesn't make sense to constantly update your images or product description to keep your product content fresh.  If you look around, you don't see a lot of eCommerce sites constantly update their product descriptions. I believe this factor applies to the website as a whole.  As long as there are new and fresh activities going on your website such as new reviews that Moosa mentioned below, it should be fine.  I believe you will also be adding more products and updating landing pages which already satisfy the "freshness factor." I would suggest spending more time on other factors if you're just thinking about Search Engine. My 2 cents

But beware some translation services based on automated systems that generate content 'almost duplicated', no matter the cost of the company that is hired, but the quality of the result and that these translations incorporating 'an extra' more human.

This is one of those things that just takes time. We moved our blog from /blog to a blog. subdomain about 2 months ago and have only recently seen SERPs reflect that. Also, the SERP results got better gradually rather than shifting overnight.

Agree with Justin, There is no right or wrong (www. vs none) pick one which suits you and go from there. You can learn setting preferred domain on webmasters here - https://support.google.com/webmasters/answer/44231 301 redirects depend on your CMS but don't forge to redirect to each relevant page. Best of luck BJS. (in short) 1) Hosted on the root domain instead of subdomain This is your preference 2) 301 all incoming requests on domain to point to www.domain (subdomain) Yes 301 so you're only using one site not both (e.g use www. or htttp:// but not both) but it doesn't have to be the www.

Thank you. Our server is fast, hosted in OVH France and we use MaxCDN. Using Magento we can achieve a very low TTFB and load time of around 180ms. We rank better for our kws in France than we do in other European countries although our site is not in French. Any ideas where I can find a map of european connectivity and hosting companies? Thanks for your help, I think that we are heading in the right direction!

I'd agree, it's hard work! But, that's why we get paid a nice salary, to figure out those difficult problems. If you have an idea of the Customer Lifetime Value, for that country, you can get some decent estimates from the expected increase in traffic when targeting that country specifically.

Thank you

This is an topic that Google is very familiar with. Matt Cutts did a video specifically about Ecommerce websites and multiple breadcrumb paths for the same product. That video is here: http://www.seroundtable.com/google-breadcrumbs-seo-18285.html

Oh, ok. If that's the case, pls don't worry about those in the index. You can get them removed using remove URL feature in webmaster tools account.

Thank you.

Hi, Generally if its good for the user in most cases, its good for the search engines, and SEO. However this is a technical issue as well, but there is great material on this, including: http://searchengineland.com/the-latest-greatest-on-seo-pagination-114284 http://moz.com/blog/pagination-best-practices-for-seo-user-experience http://moz.com/community/q/what-is-the-best-seo-solution-for-pagination Hope this helps!

Hey Ben, it has been quite a while, I would like to know if this has resolved and if so, how? I have a client who have millions of images and we have created sitemaps but they have not indexed any from the sitemap. I am guessing that it might be some information structure/link juice flow issue but any more info on the matter is gladly welcome.

That would do it! Try this in robots.txt: User-agent: Rogerbot Disallow: User-agent: * Disallow: / Keep in mind that this will only block crawlers that obey robots.txt. Once Roger crawls your site, it may be a good idea to lock the dev site down entirely.

Hi there No, the canonical will not pass the meta robots directive to the original page, so you're safe there. What you're effectively doing is using two ways to prevent duplication - the canonical will instruct web crawlers not to index versions of the URL with query strings, just as the noindex,nofollow tags will. Nothing wrong with using two methods simultaneously to do this - always a good idea to be safe - and so the end result will be that the URLs with query strings will be very, very unlikely to be indexed.

If you use the words Weber 522053 in the query, Google is likely to return the title with Weber 522053 in it, even if it doesn't return it that way for a different query, because Google sees that Weber 522053 is important to the querier. But this does show that Google knows what the intended title is and is shortening it for its own unfathomable Google-ish reasons. (I did notice that Weber 522053 is not visible on the page at all, so possibly that is what makes Google think that it is not important information to display in the serps.)